Please do, just to end the debate. I do not personally care, but it sucks the air out of the room every time the language enters the conversation.

I have only written a toy amount of code in the language, but it ticks so many of the right boxes. Fast, easy to read, GCed by default, single executable, easy C interop, etc. If only there was a larger corporate sponsor who could drive development.

This seems to be a pretty divisive issue within the community. Part of the division is understanding how off-putting other devs really find it vs. just using it as an excuse to not learn more.

I'll be honest and say it's something I really dislike about Nim.

Is it why I don't use it more? No, but I think case insensitivity was a poor decision for a variety of reasons and encourages problems down the road. I think making it case sensitive would just take away one more excuse, real or perceived.

I guess I can think of reasons for case sensitivity, but no real convincing (to me) arguments for case insensitivity. The arguments in favor of keeping insensitivity just seem to come down to resistance to change.

I'm a little surprised they are even considering removing the feature. It seems like a key selling point of Nim.

I think if they did remove insensitivity then there would be an immediate cry for "import restyling" of some kind, but I'm not sure that is so hard to do at the same time. Something like import lib {.unstyled.} would make the feature both more precise (just imported symbols, not also w_HIl_E) and more explicit (just listed libraries). And it could (maybe) be more explicit still like import lib {.style: asCamel.}

Why do we need all the options--couldn't Nim decide on a case-style is and import as that? Perhaps the time of that choice has passed.