For me, this idea of voting is strange and even makes me uncomfortable. Does 
the creator of the language agree with this procedure? If this is not the case, 
we are following a wrong path here.

Moreover, are we going to vote for each presumably controversial topic, for 
instance the syntactically significant indentation? If would be the logical 
next step, but I’m not sure it will do any good to the language which will 
quickly look like some of these committee languages with lot of compromises to 
please a majority of users.

In fact, this is the first time I see such a fuss about case insensitivity. 
Before C, most languages were case insensitive. Now, if you choose 
insensitivity, you have to suffer recriminations from some users and have to 
justify why you don’t do as C does. It looks like programmers are getting more 
conservative nowadays.

Personally, I have used case sensitive and case insensitive languages without 
any problems. In both case, I write code in an insensitive way, following the 
style guide if it exists. Using case to differentiate identifiers is really the 
wrong thing to do. So, I can switch between Python and Nim without any 
difficulty despite Python being case sensitive (which, I think, is not the best 
choice for a language with implicit declaration).

Of course, case sensitivity is simpler for the user but may cause lot of 
problems later if someone misuses it. And we can be sure, it will happen. So 
case insensitivity is a better choice to avoid any problem. The only drawback 
are possible variations in the spelling of identifiers, but it can be solved 
with appropriate tools.

So, no vote for me. There are most important topics and this case sensitivity 
vs case insensitivity topic tends to become a little too much of a religious 
affair.

Reply via email to