3 ms·

I had played with it a bit, and used it as my Advent of Code language this year. I really adore the language, it's been my go-to language for hobby projects lat

by aquova 4y ago

I had played with it a bit, and used it as my Advent of Code language this year. I really adore the language, it's been my go-to language for hobby projects lately. I wouldn't say it's quite production ready, but for personal projects I think it's great.

alberth 4y ago
> I wouldn't say it's quite production ready Would you mind elaborating why.
- synergy20 4y ago
  https://www.reddit.com/r/nim/comments/raduux/is_nim_production_ready_in_2022/ https://www.reddit.com/r/nim/comments/raduux/is_nim_producti...
  - tokai 4y ago
    The comments answers that it is ready.
- aquova 4y ago
  Some issues I've seen (and are pretty minor) are: - Nim is case-agnostic. Tokens ignore cases and underscore so foo_bar == foobar == fooBar. I personally find this enjoyable for my personal projects, but it remains a contentious subject. - Parallel support is pretty buggy. I've had loads of bizarre issues related to parallelism on the current version (1.6.10). However, from what I've tested in the release candidate, version 2.0.0 seems to have fixed a lot of these issues. - The official documentation is really good, but if you don't find something there, its hard to find it anywhere (details regarding its Javascript target remain pretty sparse, for example). All new languages will suffer from this though, and I don't think its severe enough to mark is as "not production ready" by itself, but it's worth noting.
  - monetus 4y ago
    > Nim is case-agnostic. Tokens ignore cases and underscore so foo_bar == foobar == fooBar. I have yet to be conviced it is a negative - or that the potential cons outway the potential pros, and I'm steadfastly stuck on this hill for now. Thanks for the comment.
    - gavinray 4y ago
      Well, for one, you can't accurately grep for all uses of a symbol, or at the very least it becomes much more difficult Want to know every library on GitHub that uses "mySpecialNimConst" in it's code? Enjoy the hunt
heywherelogingo 4y ago
I can't say I've encountered a reason for it not to be used in production.

by aquova 4y ago

alberth 4y ago

> I wouldn't say it's quite production ready Would you mind elaborating why.

synergy20 4y ago
https://www.reddit.com/r/nim/comments/raduux/is_nim_production_ready_in_2022/ https://www.reddit.com/r/nim/comments/raduux/is_nim_producti...
- tokai 4y ago
  The comments answers that it is ready.
aquova 4y ago
Some issues I've seen (and are pretty minor) are: - Nim is case-agnostic. Tokens ignore cases and underscore so foo_bar == foobar == fooBar. I personally find this enjoyable for my personal projects, but it remains a contentious subject. - Parallel support is pretty buggy. I've had loads of bizarre issues related to parallelism on the current version (1.6.10). However, from what I've tested in the release candidate, version 2.0.0 seems to have fixed a lot of these issues. - The official documentation is really good, but if you don't find something there, its hard to find it anywhere (details regarding its Javascript target remain pretty sparse, for example). All new languages will suffer from this though, and I don't think its severe enough to mark is as "not production ready" by itself, but it's worth noting.
- monetus 4y ago
  > Nim is case-agnostic. Tokens ignore cases and underscore so foo_bar == foobar == fooBar. I have yet to be conviced it is a negative - or that the potential cons outway the potential pros, and I'm steadfastly stuck on this hill for now. Thanks for the comment.
  - gavinray 4y ago
    Well, for one, you can't accurately grep for all uses of a symbol, or at the very least it becomes much more difficult Want to know every library on GitHub that uses "mySpecialNimConst" in it's code? Enjoy the hunt

heywherelogingo 4y ago

I can't say I've encountered a reason for it not to be used in production.