3 ms·
My biggest problem with Nim is that it did not pick its niche. It tries to be everything to everyone and does not really have strong foundations for your averag
by mathverse 3y ago
My biggest problem with Nim is that it did not pick its niche. It tries to be everything to everyone and does not really have strong foundations for your average programmer to use it in Prod.
There is not really an ergonomic, performant http server that people converged to.
Anything production quality is mostly from Status.im and people like Treeform and Guzba who also have a production use case.
- michaelsbradley 3y agoIts greatest strength at present, and for a long while, has been serving as an “expert’s tool”. If you want to do systems programming with less hassles than C/++ (you understand them well), you appreciate the limits and pitfalls of AMM (and you don’t want/need Rust’s borrow checker), and you’re into metaprogramming, well then Nim is a great tool for your toolbox. It can also serve newcomers to programming decently well and enables DSLs such as Enu ( http://getenu.com/ http://getenu.com/ ). But it doesn’t take too long reading the Nim Manual and std lib docs to realize that a big focus is putting a power tool into the hands of developers who already understand the ins and outs of systems programming. This is all, of course, my personal take on it, other Nim users may disagree.
- kevin_thibedeau 3y agoThe big weakness now is the transition to 2.0 and all the old docs floating around that are obsolete. It's hard to find info on what the new idiomatic approach is for things that have changed. I had to port some pre-1.0 code a little while back and was puzzled for a bit about resolving various (justified) deprecation warnings.