News for hackers. Stuff that matters.
Re:PEP 492 – Coroutines with async and await syntax by lmm on Saturday April 18, 2015 @04:02AM (#9398673)
With Perl 6 we saw even bigger fuss and ultimately failure.

Ruby 2.0 had similar levels of incompatibility; I think people simply didn't have those large enterprise codebases in Ruby to make a fuss about.

Java, .net and C++ go to extreme efforts for backwards compatibility, compromising their current/future versions as a result.

Re:PEP 492 – Coroutines with async and await syntax by Rafert on Saturday April 18, 2015 @08:42AM (#9399239)
Afaik Ruby 1.9.3 -> 2.0 was less painful than getting from 1.8.7 to 1.9.3. See http://nerds.airbnb.com/upgrading-from-ree-187-to-ruby-193/
Re:PEP 492 – Coroutines with async and await syntax by pjmlp on Saturday April 18, 2015 @04:40AM (#9398752)
> Java, .net and C++ go to extreme efforts for backwards compatibility, compromising their current/future versions as a result.

True, but they still introduce breaking changes as well.

I just posted all the Java release notes in a sibling post, and could do the same for .NET and C++.

Maybe the amount of breakage isn't as big as Python 2 -> 3, but it does happen.

Re:PEP 492 – Coroutines with async and await syntax by lmm on Saturday April 18, 2015 @05:43AM (#9398843)
The breaking changes really are tiny though. You can take a random Java 7 app and build/run it with Java 8 and be >99% confident that it will work, whereas with Python 2 -> 3 I'd be 99% confident it would fail (quite possibly even a syntax error).