As for the nightly compilers, I keep most of public-oriented crates on stable but I have a few of them that requires several nightly compilers. As features get stabilized, they’ll eventually end up in stable. :)
Conversation
Tooling, ecosystem, stability. Also some people prefer the more ML-style type system (over Nim). In comparison to FP langs, it provides a smooth transition to low level performance tuning.
1
I think there's lots to do with where you want to spend your 'annoyance points' too. I do feel sad about losing lots of abstraction, but have tried and failed with OPAM, stack, cabal, nix many times before.
1
Good to hear! Yeah, I've used D before (in a similar space to Nim), but personally value a safe ML-style type system with no null more than what those langs provide in general purpose programming. Would prefer OCaml/Reason or Haskell here.
2
1
Nim also looks a whole ton prettier than Rust, which is something I value a quite a lot actually!
2
1
I done a bunch of both, I really like how easy to get started with Nim, and the code looks cleaner that Rust. But the error handling with exceptions is a big downside for me. Also the Nim ecosystem is quite lacking.
1
Yeah, I've had similar feelings coming away from D. Similarly default-nullability in a language is kind of a deal breaker for me these days. 😫 Would be cool to see more langs follow the example of C# 8.0 and add opt-in nullability retroactively.
1
Ecosystem is dependent on what you are doing though. When I started Rust's ecosystem was pretty rudimentary, and it's taken a bunch of excited, interested people to get it off the ground. I have to be excited to invest that energy though.



