Live data from Hacker News

Work has started on Ruby 2.0

github.com

1–10 of 62 posts

Re: Work has started on Ruby 2.0

#3

Let's hope it will gain more acceptance and usage than Python3. Do they intend major changes?

For good or bad, the ruby community tends to embrace changes faster than the Python community. For example Rails is going to drop 1.8.7 support in the next release 3.2

Re: Work has started on Ruby 2.0

#8

Let's hope it will gain more acceptance and usage than Python3. Do they intend major changes?

For good or bad, the ruby community tends to embrace changes faster than the Python community. For example Rails is going to drop 1.8.7 support in the next release 3.2

From personal experience the community at large is eager to move to Python 3. It has more to do with tremendous inertia generated by critical components being tricky to port to Python 3. Usual suspects Django and Twisted come to mind. IIRC NumPy gained support only recently.

The Wall of Shame gives a very partial overview of the situation: http://python3wos.appspot.com/

It does not help that useful stuff from 3.x get backported to 2.x or available via __future__, and that IMHO Python 2.7 is awesome so the urge is not quite there (well, not as much as working with Ruby 1.8 when you tasted 1.9)

Re: Work has started on Ruby 2.0

#10

Let's hope it will gain more acceptance and usage than Python3. Do they intend major changes?

Not a direct answer to the question but Ruby 2.0 is expected to be backwards compatible with the current production release, 1.9.2, while just adding extra features. I'm not particularly well versed in Python 3 but I believe it wasn't intended to be backwards compatible.
Post reply on HN