Hacker News Reader

I would say that the policy of rapid movement it has its ups and downsides; Python code is generally very stable between versions and breakage is well-documented. So far I haven't seen the same thing going on in Ruby land.

JRuby is clearly more advanced that Jython. I'm guessing that with the advance of PyPy, other Python interpreters just aren't getting that much attention, which is a bit unfortunate.

View on HN

rapid movement definitely has it's downsides. However, I don't know what you mean when you say that ruby code isn't stable between versions. Do you mean between versions of ruby? If so, again, the transition from ruby 1.8 to ruby 1.9 was much much better than the transition from python 2 to python 3.

Python 2 to Python 3 is a big jump once in a lifetime. what about ruby 1.9 to ruby 2.0?

ruby 2.0 will likely be just as easy as 1.8 to 1.9, if not easier.

so, it's not as easy as python 2.x to 2.(x+1) and python 3.x to 3.(x+1). will every version update of Ruby will suffer as mush as Ruby 1.8 to 1.9?

Reply on news.ycombinator.com