Nim Version 1.6.6 Released
nim-lang.org
Nim Version 1.6.6 Released
1–10 of 116 posts
Re: Nim Version 1.6.6 Released
#2https://news.ycombinator.com/item?id=31238375
This whole question generates a lot of controversy for some reason
Re: Nim Version 1.6.6 Released
#3There is a question of getting rid of style sensitivity in Nim 2: https://news.ycombinator.com/item?id=31238375 This whole question generates a lot of controversy for some reason
There is trade offs to both sensitivity and insensitivity. Just because you are used to one approach from your favorite programming language does not mean the other way is "wrong".
Want a consistent style? Use that nice --styleCheck:usages option. No problem at all.
Honestly, I think Nim should keep the current approach just to filter out certain people.
Re: Nim Version 1.6.6 Released
#4There is a question of getting rid of style sensitivity in Nim 2: https://news.ycombinator.com/item?id=31238375 This whole question generates a lot of controversy for some reason
Maybe it's not so bad in practice, but looking from the outside, I think... really? To be specific, case-insensitivity doesn't bother me, but the automatic conversion from camel-case to snake-case... very much so.
Re: Nim Version 1.6.6 Released
#5There is a question of getting rid of style sensitivity in Nim 2: https://news.ycombinator.com/item?id=31238375 This whole question generates a lot of controversy for some reason
Re: Nim Version 1.6.6 Released
#6There is a question of getting rid of style sensitivity in Nim 2: https://news.ycombinator.com/item?id=31238375 This whole question generates a lot of controversy for some reason
It actually is something that gives me pause for thought. In my field of coding (finance) ambiguity is terrifying and eventually you get it wrong. Maybe it's not so bad in practice, but looking from the outside, I think... really? To be specific, case-insensitivity doesn't bother me, but the automatic conversion from camel-case to snake-case... very much so.
It prevents bugs where a developer mistakes one variable or proc for another having similar names.
For example in another language you might have variables isReady, isready, is_ready and use the wrong one, leading to a bug.
Nim does not allow defining 3 different variables like that.
Re: Nim Version 1.6.6 Released
#7This issue alone means I can't use it at work, and I haven't put much time and thought into Nim as a whole because I could only use it in private toy projects.
I understand it's mostly the AV vendors fault and the devs shouldn't have to worry about a problem they haven't caused, but for me, this grinds real-life adoption of the whole thing to a halt.
Re: Nim Version 1.6.6 Released
#8While the main team works on bigger things drawing v2 closer, there's still lots of issues of various magnitude and lots of housekeeping bits that can be done while getting yourself acquainted with the project's structure.
Here's a few links for your consideration:
* https://github.com/nim-lang/Nim/issues?q=is%3Aissue+is%3Aope...
* https://dev.to/xflywind/best-ways-to-make-your-first-contrib...
Re: Nim Version 1.6.6 Released
#9I wish they would take the antivirus issue on Windows more seriously https://github.com/nim-lang/Nim/issues/17820 This issue alone means I can't use it at work, and I haven't put much time and thought into Nim as a whole because I could only use it in private toy projects. I understand it's mostly the AV vendors fault and the devs shouldn't have to worry about a problem they haven't caused, but for me, this grinds re…