Nim programming language finally hit 1.0

Chris wendlec at
Wed Sep 25 14:36:44 UTC 2019

On Wednesday, 25 September 2019 at 14:24:39 UTC, Paulo Pinto 
> On Wednesday, 25 September 2019 at 10:59:55 UTC, Chris wrote:
>> On Wednesday, 25 September 2019 at 10:01:40 UTC, Rel wrote:
>>> Well, finally Nim team released 1.0. Now future releases 
>>> shouldn't break people's code and this fact should increase 
>>> language adoption. Still few things seems to be unfinished 
>>> (like their NewRuntime thing), but I'd like to congratulate 
>>> Nim's team with this big release. What do you think about it?
>> The link above reads almost like a summary of "Don't do what D 
>> did!". Congratulations! I've been looking at Nim on and off 
>> (like most people, I suppose). One thing that really turns me 
>> off is that indentation is an integral part of the syntax [1]. 
>> Nim designers seem to forget that Python introduced forced 
>> indentation, because Python was meant to be used by 
>> non-programmers (chemists, biologists etc.), and thus this 
>> feature was there to "help" non-programmers to keep their code 
>> clean and tidy (cf. Perl!). However, Nim is targeting 
>> (experienced) programmers who really don't need a patronizing 
>> feature like that. This is a real bummer, in my opinion, like 
>> selling a bottle of whiskey with a child safety lock to a 
>> publican.
>> [1] 
> Forced indentation goes back to 70's languages. Python did 
> nothing new there.

Let me guess, the reasoning behind it was the same in the 70ies. 
Force "clean code"? I.e. patronizing. Please enlighten me.

Anyway, Python made forced indentation popular. Python became a 
mainstream language "by accident", and because of its popularity 
people thought that forced indentation was great, although it has 
its merits only in contexts where most users are not programmers 
(e.g. natural sciences at universities).

More information about the Digitalmars-d mailing list