3 ms·
IT really depends on what you're doing. I'm inferring from the list of languages you described above that you're doing a lot of line-of-business applications w
by bunderbunder 8y ago
IT really depends on what you're doing.
I'm inferring from the list of languages you described above that you're doing a lot of line-of-business applications where, yeah, it's almost essential to have that huge, Java or Python sized ecosystem.
Nim doesn't have that. But Nim isn't really aimed at that kind of work, either. What it does have is very good C/C++ interop, which means that it's easy to interface with existing low-level libraries. That makes it a pretty decent option for writing low-level bits, or looking to incrementally migrate from C/C++ to something a bit more modern.
For the mostly-Java stuff I'm working on, I rather wish the native components were written in something like Nim. They'd be easier to maintain if they were.