> Assume you have money, where would you spend it first to have the maximum > impact?
Definitely tooling and some marketing. To some degree, they overlap as good tooling helps marketing. On my team at Status there's a lot of non-Nim folks coming from Java, Python, etc and they pretty much all dislike the tooling. None of them really seem to care so much about syntax, exceptions vs results, ranges or map performance, etc. It's that the most common tooling (VSCode) only works part of the time, and that's after I helped show people how to set it up. It was broken for months due to `nimsuggest` crashing on some bit of syntax that compiled fine but crashed `nimsuggest`. Many of them can't compare it to the joy of things like C++ and are comparing it to Java IDEs or PyCharm. For small projects `nimsuggest` & VSCode works well. Even for the compiler it works well. On larger projects however, it becomes more of a pain. Even setting up VSCode to only run `nimsuggest` once on top level still is a pain. The VSCode plugin doesn't appear use `nimsuggest` to do compile checks even when configured to do that. I'm planning to spend some time seeing if we can switch to nim LSP and/or improve the VSCode plugin if needed. The important pieces people seem to want: dependency lookup / goto, and quick error checking.
