Breaking backwards compatiblity

[Nick Sabalausky]

"Nick Sabalausky" <a at a.a> wrote in message 
news:jjgkb8$s1f$1 at digitalmars.com...
> "bearophile" <bearophileHUGS at lycos.com> wrote in message 
> news:jjgi8v$p1s$1 at digitalmars.com...
>> Walter:
>>
>>> I'm talking about the name change. It's far and away the most common 
>>> thing I
>>> have to edit when moving code from D1 <=> D2.
>>
>> We need good/better ways to manage Change and make it faster and less 
>> painful, instead of refusing almost all change right now.
>> Things like more fine-graded deprecation abilities, smarter error 
>> messages in libraries that suggest how to fix the code, tools that update 
>> the code (py2to3 or the Go language tool to update the programs), things 
>> like the strange "future" built-in Python package, and so on.
>>
>
> +1

To elaborate on that, stagnation with thinks that should have been *just 
fixed* is one of the reasons I got fed up with C++ and went looking for an 
alternative (and found D). I hate to see D starting to jump into the same 
boat so soon.