5 ms·
Nim is far less complex, but isn't as popular. The community is working quite hard to change that though.
by jasfi 4y ago
Nim is far less complex, but isn't as popular. The community is working quite hard to change that though.
- xwowsersx 4y agoI really like Nim. I was able to build some non-trivial things in it after just a few hours of googling and reading documentation (supplemented with a few questions on IRC). I do sometimes worry though about investing in a language that, due to its lack of popularity of "catching on", may never have the richness of tooling and packages/libraries needed to use it in the context of a larger project or larger team. But perhaps that concern is misplaced...maybe it's a social thing where you feel a bit out on your own when there isn't a large community coalescing around the language.
- jasfi 4y agoI've had the same concerns. I made a Nim web framework, but I don't think anyone else has written a web app with it except for myself. My thinking now is to combine Nim with other languages and their frameworks. For example a NextJS/React front-end with some GraphQL servers in Nim. Alternatively Nim and Python mix quite well.
- xwowsersx 4y agoWhat's your web framework?
- rich_sasha 4y ago100% agreed, to the letter. My recent observation is that programming languages are a bit like warfare. We are drawn to discuss syntax and features, or machine guns and fighter jets, but what seems to trump these on any practical timeframe is logistics. When coding up a new project, I need a language which gets a lot of mileage, so the bugs are stamped out. It needs good tooling so I'm not stuck making it myself. It needs robust package support, so I can just type the project-specific code. Oh and the language can't be unworkable, and vaguely needs to fit technical spec. It's a sad chicken-and-egg situation, but users are often not in a position to take the risk.