Hacker News new | ask | show | jobs
by musaffa 3465 days ago
Python 2 to Python 3 was a disaster. Matz has made it clear in his speeches that he wont do the same mistake in Ruby. Performance and better memory management will hopefully come in the upcoming 2.5, 2.6 and 3.0 releases. What I want from all those changes is that all my current projects should just work.
1 comments

Funny, I thought it had happened before in the ruby world with the switch from ruby 1.8 to 1.9 and the pythonists simply followed suit.
That's the obvious comparison. But in the Ruby world, 1.8 has long been forgotten. I don't know anyone still using 1.8, and we're all better off.

In python, on the other hand, years later it's still a shit show. The community still hasn't embraced one or the other. Some people still refuse to upgrade to 3.x. Everything is splintered. It's especially hurtful to newcomers.