I'm more and more convinced that a language is only as good as its ecosystem. Yes, language features and ergonomics do matter and are what initially draw people, but in the long term without a robust set of supporting tooling, well designed libraries, and a significant standard library, the language will eventually decline.<p>Neither Java nor Python are incredible languages as far as baseline features and semantics are concerned, but they continue to thrive because their ecosystems are fantastic and they both have really rich standard libraries to start from. Contrarily, quite a few languages I love from a language design perspective fail to gain as much traction for lack of well-developed ecosystems.
If are a data scientist and come from python take a look at nimpy, a great way to just import python libraries and use them! <a href="https://github.com/yglukhov/nimpy">https://github.com/yglukhov/nimpy</a> Numpy, pandas, pytorch all usable in Nim.<p>Nim is the ultimate glue language, use libraries from anything: python, c, js, objc.
One unusual hurdle for Nim right now is that on Windows, many of the anti-virus vendors out there are overly aggressive in flagging as bad any executable that was written in nim [1].<p>Don't know if they've made much headway lately, but for awhile even the main installer was getting flagged, as well as tools like choosenim.<p>See e.g. <a href="https://github.com/nim-lang/Nim/issues/17820">https://github.com/nim-lang/Nim/issues/17820</a>
The guy needs better debugging facilities in Nim, so why don't guys discuss a way of organizing funding for better debugging facilities and stop going off on a tangent?<p>The inability of HN posts to stay on topic is pretty annoying.
The one thing that's really holding me back from Nim: the lack of an integrated debugger in Jetbrains' IDEs.<p>Yes, I can hold lots of state in my head; and yes, I can make do without a debugger, if I have to.<p>But I <i>don't</i> want to. Especially since I've been so spoiled with PyCharm and Clion's way of doing it. My debugging time is limited and valuable, and a debugger that quickens my inspection of a program is nowadays so essential to my workflow that I'd rather hold back from committing to Nim at all until its debugger tooling (at least to the level of that in Jetbrains' IDEs) is available.
I found Nim to be the best in compile-to-C class of language/tools from the 2010s.<p>The problem was that, it wasn't [possibly still isn't] available in default Fedora repo while other less popular languages were available. No idea why. Might be due to low adaptation.
The authors praised Rust debugging capabilities (also) in VScode, can somebody point to some references on this? From what I’ve seen around and what I’m able to debug in my VScode environment I might be missing something…