3 ms·
Nim for #3, I think. I've found Nim to be an incredibly productive language. I was able to write very performant and readable code after just a couple of hours
by xwowsersx 3y ago
Nim for #3, I think. I've found Nim to be an incredibly productive language. I was able to write very performant and readable code after just a couple of hours of reading the docs and looking at some tutorials. If the community and ecosystem grows larger, I could see building something large and non-trivial with Nim.
- deleted 3y ago[deleted]
- elcritch 3y agoAgreed! There's a couple of fairly large projects in Nim: https://nimbus.team/ https://nimbus.team/ (https://github.com/status-im/nimbus-eth2 https://github.com/status-im/nimbus-eth2) or https://github.com/zedeus/nitter https://github.com/zedeus/nitter Though there's still friction points I've been happy seeing the ecosystem grow lately. The compiler has seen a lot of bug fixes lately too which helps.
- xwowsersx 3y agoOh nice, didn't know nitter was built with Nim, that's awesome
- etra0 3y agoI really wanted to like Nim, but its async story is not that great (no multithreaded runtime AFAIK, no channels) and albeit justifiable, I don't like the way it treats imports. I think Crystal and Go are better in the async space. I thought I'd have more troubles with the case insensitivity thing, but it turns out, it wasn't a big issue at all, and UFCS is great.
- xwowsersx 3y agoAh, good to know. I hadn't checked out the async story in Nim at all.