Python 3 put-downs: What's the point?

[Gregor Horvath]

Am Mon, 05 Jul 2010 14:32:13 -0500
schrieb Tim Chase <python.list at tim.thechases.com>:

> On 07/05/2010 02:50 AM, Gregor Horvath wrote:
> > Am Sun, 04 Jul 2010 18:51:54 -0500
> > schrieb Tim Chase<python.list at tim.thechases.com>:
> >
> >> I think it's the same venting of frustration that caused veteran
> >> VB6 developers to start calling VB.Net "Visual Fred" -- the
> >> language was too different and too non-backwards-compatible.
> >>
> >
> > VB6 ->  VB.NET and Python 2 ->  3 is not a valid comparison.
> >
> > VB6 and VB.NET are totally different languages and technologies,
> > with some similarity in syntax. This is not true for Python 2->3.
> > This is an healthy organic language growth, not an abandon of a
> > language.
> 
> The quintessential example is Py3's breaking of Hello World. 
> It's a spectrum of language changes -- Visual Fred just happens 
> to be MUCH further down the same spectrum having more dramatic 
> changes.  Only a subset of $OLD_VER (whether Py2 or VB6) code 
> will run unmodified under $NEW_VER (whether Py3 or VB.Net).  It 

Don't you think that there is a really huge difference in an
evolutionary development of a language with some well founded
incompatibilities due to some muck outs on one side and and on the other
side stopping the development of a language and replacing it with one
derived from a completely different one and giving it a related name
and syntax?

And that such a big difference forbids any comparison, although there
are some superficial similarities?

--
Greg