So, I already attempted to make a reply to tell you guys why I'm not using Nim 
as my programming language, even though, I really would like too. I'm unable to 
describe the problem I have with Nim, but I don't have to, because somebody 
else already did and I'm so glad that I'm not alone with this thought and 
mindset.

I had planed writing a massive orchestration software and I'd love to write it 
in Nim. But as a maintainer of such a large-scale codebase I imagine it to be a 
nightmore doing code reviews on GitHub, not knowing what is coming from where. 
You could argue with "Use qualified imports blah blah blah" but who really does 
that. And it doesn't cooperate well with the general Nim coder with this 
"freedom mindset".

In my point of view Nim is great for prototyping, CLI tools, "scripting" and 
maybe even minor-ish web applications. But you just can't do large-scale stuff 
with it and I'm not gonna believe anything else if not proven otherwise. (And 
please don't come up with Status' Ethereum Client "Nimbus". Have a look first.)

It's actually pretty sad. I'd really like to use Nim for something large-scale 
but Nim, in its current state, feels more like a scripting language with a "AoT 
facade".

Reply via email to