Like, as to that person who thought Nim to be a deal breaker because of whitespace, I think that this new information might help them to atleast try Nim!
Thanks, I learnt something new today thanks to ya!
In general Nim's syntax affords much, much more choice than Python, from UFCS to user-defined operators to macros to term re-writing macros to etc., etc. It's really a step up from Python in so many ways with a lot of compile-time checking and safety and essentially the same perf as C++. It's a shame it's not a little more popular.
I mean. sure they might be a bit disappointed but I didn't even know that () this syntax works, I mean {} is already used by something like set iiirc so something like it for nim might break existing functionality.
I just really thought about how to convince others who might have the same grievances with nim because personally I don't mind whitespace but I also want nim to succeed of sorts.
Nim to me is a love letter of sorts to programming in general. Maybe I romanticize nim but the only language I feel this sense of writing software in is maybe golang.
I am forced to write typescript/python tho, yes I know that nim can be transpiled to js but still, I want to learn Nim too and just build some side casual projects like how people are building with zig. I don't want to suffer with memory management right now so I would use their garbage collection and then if someone wants performance, they can modify my software rather easily for that purpose too.
I was thinking of creating a music player from scratch in nim just for learning it. idk, i really want to build something in nim / maybe even contribute to its small libraries to increase the library support