We're pleased to share some updates regarding the Nim tooling ecosystem.
As part of ongoing efforts to enhance the Nim programming experience, Status has brought on board part time @nickysn and myself specifically to focus on Nim tooling development. Our task is to streamline and improve the tools available to Nim developers.
Here is a mid term roadmap: https://github.com/nim-lang/RFCs/issues/544
We believe that these developments will significantly benefit the Nim community, and we're excited to see the impact of our work. Feel free to give us feedback here and/or the roadmap.
The official Nim extension for VSCode is available at https://marketplace.visualstudio.com/items?itemName=NimLang.nimlang
This is such great news to have you work on this and getting paid for it :)
I have no meaninful feedback to give, but I'm looking forward to see the impact of it !
Will the VSCode points be actually specific to the extension or is the plan to improve ‘nim-lang/langserver’ for this?
Really hoping for the latter as that would make these improvements available to everyone instead of just vscode users
I begrudgingly use vscodium and the official nim extension doesn't show up for me. I would prefer an up-to-date, fairly basic gtk editor written in nim and will eventually try to write one if nobody else beats me to it.
Being expected to get official nim tooling from the Microsoft Store is unfortunate (to me), to say the least, and i won't use the telemetry-laden, proprietary vscode to do it.
I hope Nim's policy will be that being subjugated by "Big Tech" or proprietary software is not mandatory for the eventual full, official tooling experience.
Note that this is not a nim action, this is status doing those actions which benefits the wider nim ecosystem.
Personally I'm happy for any improvements they shell out, anything to make my life easier while I write my threads-as-a-backend-server-for-applications library ^^
I don't think you're correct here:
Note that this is not a nim action, this is status doing those actions which benefits the wider nim ecosystem.
The first post clearly says "The official Nim extension for VSCode", and it's also sitting under the nim-lang org, which (I think) makes it an official Nim project either way.
Super!
from the changelog of the vscode extension, I read that nimlangserver is used by default, and direct access to nimsuggests is deprecated.
This is good, but this also opens the possibility to use other LSP like nimlsp instead of nimlangserver.
What about providing the user the possibility to pick the binary to use as LSP, defaulting it to nimlangserver?
`importjs` pragma requires the JavaScript target
dom.nim(1780, 1): template/generic instantiation of `since` from here
In VSCode I get this error for all {importjs} pragmas in eg. dom.nim in my project from the nimlangserver. What can I do?
How can I config the project as js target? Does it work with nim.cfg or config.nims?
I would prefer an up-to-date, fairly basic gtk editor written in nim and will eventually try to write one if nobody else beats me to it.
Like the old Aporia? https://github.com/dom96/Aporia
You can use every "official Microsoft store" extension/plugin in VsCodium too, but you need to download the .vsix file and the import it manually in the menu of VsCodium
But there is a serious problem on discoverability. Why would a VSCodium user do that if when he searches for nim extensions there is just a single clear option, that presumably is the official Nim VSCode extension everyone talks about. He will use that extension by nimsaem and complain everywhere on the state of the Nim tooling, where even the "official" extension hasn't been updated since 2022 and is lacking in many places.
Why can't the real official extension be visible in the VSCodium marketplace?