As stated before many many times by many people, what matters with syntax is the consistency. Choose one, stick to it.
Consistency is a large part of what helps code readability. Also - and I'm surprised this has to be stated - syntax **is not** a factor that increase or decrease Nim's adoption. Python has indentation based syntax and is widely used. In that regard style insensitivity for symbol actually **help** accomplish that, by allowing uniform style in a code base even while using external module with a different style. There is already a `stylecheck` options available warning you about inconsistent naming; otherwise to enforce a single style across codebase, you'd have to forbid snake_case (but that would actually be a PITA when working with C codebase). The only cases where style insensitivity are potentialy problematic are : * keywords; the fact that `pRoC` or `pr_oc` is valid feels strange (although it's not that important as I think it would take a very psychopathic developer to use a non standard variation of the keyword anyway) * Module name : having a file named `my_type` which define `type MyType = object` and then you try to instantiate `var myType : MyType` will cause issues because you accidentally have a variable with the same name as a module. This is one is the most problematic especially because the current lack of support for cyclic import force you to move type to a specific file.
