4 ms·

I dunno, it is kind of reasonable. C# was designed with a different mindset, but the intents were the same - take a predecessor (VB / Python2) and make them mor

by zanny 14y ago

I dunno, it is kind of reasonable. C# was designed with a different mindset, but the intents were the same - take a predecessor (VB / Python2) and make them more modern, fix the gotchas and mindfuck, and produce something more refined that isn't backwards compatible. C# takes it much further, and iterates on syntax a lot more, but Python3's breakage from Python2's is comparable I feel, just not in nearly as extreme a case.

lucian1900 14y ago
It is trivial to write new projects that work on both Python 2.7 and 3.3. So trivial in fact that I did it without trying to several times.
masklinn 14y ago
> Python3's breakage from Python2's is comparable I feel They're not. You can create "single source" Python packages working on both Python 2 and Python 3. Good luck doing that with C# and VB.