Nim core developer wanted
forum.nim-lang.org
forum.nim-lang.org
The main takeaway is specific to my use-case: writing a dynamic library that can be called from within Python code. The main positive and negative are two sides of the same coin: since Nim compiles to C, you get to use all the existing tools designed for doing C FFI in Python, and don't have to write any C wrappers. And since Nim isn't C, there's still a little bit of detective work involved in replicating all the argument types, GC behavior, etc, that is involved in Nim and the specifics of its realization in C.
Generally most bugs are related to newer features. I never experienced any bugs with the core features/library.
What kind of stuff is particularly popular among Nim users compared to communities for other languages?
What kind of stuff do the people working on Nim want to use it / see it used for?
Thanks to its approach to GC, you can impose a limit on the time to spend on GC between ticks, so no unpredictable performance stuttering.
I see it as having nice "functional-ish" syntax like Python, but with static types.
"As friendly as python or ruby, but compiles to binary for ease of deployment and speed" is currently an under-served market niche.
Rust, Go and Swift are all candidates for the space (with the current defacto standard of friendliness in compiled languages being c++), but I find none is quite a match for me.
Yet, Nim has a tiny memory and storage footprint and runs on microcontrollers thanks to GCC, which makes it ideal for IoT stuff.
Yeah, I don't have any sound technical reasons for not using Go, I just find it to be somewhat claustrophobic to use. To paraphrase someone else, when I code in Go I feel like Rob Pike is standing over my shoulder muttering "why would you want to do that?" every 10 minutes or so.