While I agree with everything what Libman says I am also a bit afraid.

  * syntax wars will not be ceased in peaceful Nim world, they will be drag 
inside Nim world
  * Nim already allows using quite different styles. And it happens quite often 
that I am looking at someone's code and it take me time to understand. I loved 
that in Python with its quite easy schematic syntax and not many keywords I was 
able to pickup programs just by looking at them.
  * Programs are written by people and read by people. I do not care about AST. 
If I see two programs in Nim written in different syntax it is not very 
different situation for me if they were actually written in different 
languages. And so if I see program written in F# it does not help that I know 
VB and C# and all three are compiled to CLR.
  * For a long run I doubt that it is existence or lack of curly braces in 
language that makes it good or bad (or popular). This is only excuse in most 
cases. Programming in a specific language I am able to adapt to its 
specification. I want it to be concise, clear and allowing me to implement what 
I have on my mind. Also easy read examples and documentation.
  * It is already frustrating when I am adapting libraries or copy someone's 
else part of program and I find that it uses 2 spaces indentation (I am using 4 
because then I can see better, using tabs would solve this problem, but it was 
discussed somewhere else so I need to live with that). I can imagine if I had 
to merge two Nim different syntax programs. Automatic conversion could help but 
it is just another step to do and I doubt it would be perfect.


Reply via email to