To me this is kinda akin to the people that complain about the magic in Rails or that Ruby includes so many things by default (like rand or sleep) without working on a couple of projects first. Those really aren't the problems that slow you down in Ruby and this isn't really something that is an issue in practice.
This plus the crazy global name space pollution. If you import something, everything is imported from that module. I have no idea what to name things because everything collides with everything else.
In Python, things are simple. Classes are 'CapitalCase' and functions are 'lower_case'. If I did the same thing in nim, they would collide. Also, in Python it is considered a terrible idea to do
from some_module import *
in Nim, it is the way things are done. Although, they are alternative methods that don't do this.also, the weird
var
a, b = 0
Perhaps you get used to it with time. But still namespace collision is always a problem for me especially when working with others' libs.However, it is currently the most painless way to write fast code and integrate with Python, which says a lot.
Edit: Looks like first letter matters now, so ignore that part of the comment.
I was reusing "paramStr" variable. This is a built in in the os module. I defined "param_str" in my module. Then wrote another module that was using the first one. Then realized I was overwriting an OS module function.
I actually have no idea how such collisions are handled. What if I import another module that overwrites the OS module? What if a 3rd party lib uses some variable that another 3rd party lib also defined?
A whole set of problems would be gone if such importing was looked down upon. I mean it is exactly the same situation in Python (but not exacerbated by the name canonicalization), and people realized a long time ago that doing this is not a good idea.
At least it's case sensitive for the first letter, which means that the traditional lowercase-for-identifiers, capitalised-for-types naming scheme works.
I've tried programming in Ada, which has case insensitive identifiers; it was deeply painful.
Edit: Plus, of course, case sensitivity is locale dependent. Are I and i the same letter? Not if you're Turkish. (Upper case i is İ; lower case I is ı.)
Yes, this matters. http://www.theinquirer.net/inquirer/news/1017243/cellphone-l...
Go and Haskell also have some special (unconventional) treatment of capital letters, which probably make them biased towards the English language.
> Go and Haskell also have some special (unconventional) treatment of capital letters, which probably make them biased towards the English language.
In Ruby an identifier is considered to start with an uppercase letter when it really starts with an uppercase letter or underscore; that probably is the best compromise for unicase scripts including CJK scripts.
userName == user_name == username == uS_eR_aN_mE
It used to be totally case insensitive now it is case sensitive for the first letter. Underscores are ignored: two identifiers are considered equal if the following algorithm returns true:
For me it is a capital violation of the "principle of least astonishment".