When I started reading the feature list above, Nim was the first thing that came to my mind, until I saw the thing you mention:

> except the ecosystem/commercial backing

If this is not the most important feature on that list, here is one more vote for Nim. Give it a try, it might (pleasantly) surprise you!

Cheers to Nim. I'm learning it in my spare time for fun. However, I will not consider using it for anything more than toy projects until it hits 1.0. Hopefully soon.

> I will not consider using it for anything more than toy projects until it hits 1.0. Hopefully soon.

It should happen soon (TM), but from what I understand it will be just another version, just this time renamed to 1.0 - this basically means you could start using it more seriously even now.

Yeah. I understand that it will be just another version with not that many changes. Nim as it currently already feels stable and solid. But, I believe v1.0 release will carry a commitment to not introduce breaking changes at least for reasonable period of time after.

I wish there was a Go->Nim compiler or a way to simply import stuff from Go :) I'm just half-joking to be honest.

Go can generate .so/.dll usable from C; Nim can use them.

What's the IDE support like for Nim?

va code extension, vin plugin, enacts mode all very functional. There’s aporia, written in Nim, but it is not as advanced.

Nim itself does not come with an IDE, but does include nimgrep and nimsuggest which underlie intelligence and other features in every IDE setup.

Does Nim have a good story for borrowing c/c++ ecosystems?

Yes. The most common compilation path is through C or C++, which together with the source-based FFI makes the integration mostly seamless.

There’s also c2nim which will generate the bindings for you (though it might need some hand holding if the header files make extreme use of macros)