It may sound like a bit of a rant and I can't hide the fact that it is, because i am fed up. The newest "release" of the nim vscode plugin and nimlangserver throws me back to the last release of these to utils. It was a hell of a nightmare to get them working. and now the same as before, it fell completely apart.
starting with endless loading of "checking file://" to dozen of errors in the output of vscode. i am coming to the edge where i have no more desire to work on nim projects, because everything is falling apart. i have to debug more nim and its ecosystem as my own projects because where i look it is stitched together with ducktape that has its expire date overdue.
i am sad to say this but this brittle experience is currently only at nim if i look at similiar languages, their ecosystem is mostly working out of the box (in vs-code nim plugin you need a damn settings file, because the sh* plugin is to stupid to find a f* nim file, oh boy...)
opening issues is useless due to the gtfo mentality in a lots of projects / libraries.
i use nim sind 0.13. it was always a joy. but in the last couple month or maybe a year or so it feels more and more annoying to be permanently confronted with falling apart ecosystem.
one day it may matured, but not today.
I have to say nimlangserver is getting better with every release and is much more stable now compared to a couple of months ago.
No idea about the vscode extension though; I use helix with nimlangserver and nph, and it's a pretty solid nim development environment imho.
opening issues is useless due to the gtfo mentality in a lots of projects / libraries.
so you gave up without doing the only required part?
Complaint like this are always the same.
"I tried nothing and I am out of idea, someone needs to come holds my hands while I pee and solve all my problems for me. No, I am not a contributor of this community-built language, why do you ask ?"
As Araq mentioned, these won't help anyone.
We need to be kinder and more considerate to each other to foster a better community and help Nim become mainstream. That way, we all benefit.
I will be refactoring some Nim code in a few days and will report the issues (if any) that I face.
I agree. While the Nim programming language is getting better every release, lots of tools still drive me crazy. Things I try to avoid include nimble, DocGen and nimscript. I have managed to get at least syntax highlighting work with VS Codium, but getting things work is not easy.
What about giving Zed a chance? It seems to have built-in Nim support.
While Nim itself is a joy to work with, it is sad that the tooling does not yet live up to it. But understandable, given that this is essentially a community effort.
Trust me you’re not the only one frustrated with the tooling. Personally I’ve been contributing to nimble lately because it annoys me and I want it working.
What I’ve seen is that despite lots of improvements in the tools recently in some ways it’s been feeling worse for a while.
Most of that is due to things being changed and it taking time to fix some fundamental issues in the tools and ecosystem.
Hopefully folks can understand this process will be annoying while issues are being worked out.
It can be really helpful to file issues and even contribute PRs. @jmgomez has been doing awesome work on the tooling and has been very open.
starting with endless loading of "checking file://" to dozen of errors in the output of vscode.
Yeah that’s happening in my projects a lot as well in the last few releases of nimlangserver. I haven't figured out why yet though.
Note this stuff used to happen before but now it’s actually visible. Still it can get annoying seeing them spinning forever. But now they can be fixed.
Nimlangserver relies on nimble to find packages and libraries. Long term that’s good but short term it’s a pain because Nimble still struggles.