News for hackers. Stuff that matters.
Re:Ruby 2.2.0 Released by hackerboos on Thursday December 25, 2014 @07:09AM (#8796090)
That's what happens when you maintain two versions, one of which has fundamental breaking changes.

When the Ruby team makes changes the attitude is generally 'deal with it'. Sure they still do point releases on older versions but only for security issues AFAIK.

Python moves forward it just does a poor job of dragging everyone with it.

Re:Ruby 2.2.0 Released by dagw on Thursday December 25, 2014 @09:40AM (#8796298)
When the Ruby team makes changes the attitude is generally 'deal with it'

However they complement this attitude by being a lot better at working with big 3rd party library developers and making sure they are on board. To the best of knowledge there has never been a Ruby release that was incompatible with RoR for any period of time. Compare to Python that jumped to python 3 without either numpy or Django on board.

Re:Ruby 2.2.0 Released by yxhuvud on Thursday December 25, 2014 @02:44PM (#8796990)
Well, on the other hand I definitely remember a point release of 1.8.7 that broke Rails :)
Re:Ruby 2.2.0 Released by wycats on Thursday December 25, 2014 @07:19PM (#8797586)
Momentarily, and Matz appeared to feel so bad about it that they have been far more aggressive about tiny-version changes ever since.
Re:Ruby 2.2.0 Released by reledi on Thursday December 25, 2014 @07:24AM (#8796115)
Sounds about right. Coming from a Python background to Ruby, I think there's more to it though. For example, Ruby version managers such as rvm and rbenv help a lot with keeping the community moving forward. Python has virtualenv but it always felt awkward to me compared to what Ruby has.
Re:Ruby 2.2.0 Released by jrochkind1 on Thursday December 25, 2014 @10:07AM (#8796359)
Interesting, I haven't worked in python, but I was always jealous of python having a single 'official' solution in virtualenv, instead of ruby, where it's confusing for newcomers to figure out which one they should be using (rvm? rbenv? chruby?), and each solution has it's annoyances and problems. I always thought it would be better if the community unified it's efforts behind one solution and made sure it was bug-free, and where the language's binaries or behaviors might actually be changed when needed to support that solution.

Maybe it's just the grass is always greener.

Re:Ruby 2.2.0 Released by weaksauce on Thursday December 25, 2014 @12:49PM (#8796729)
Since you haven't used it you don't know how awkward it is compared to the Ruby iterations. Let's just say virtualenv and the packaging ecosystem is what drew me away from Python.
Re:Ruby 2.2.0 Released by nileshtrivedi on Thursday December 25, 2014 @12:15PM (#8796652)
Ideally, the operating system's package manager is supposed to solve this. User-installable alternative versions shouldn't be that hard.
Re:Ruby 2.2.0 Released by berdario on Thursday December 25, 2014 @08:03AM (#8796177)
You have a plethora of similar tools in the python world as well:

- Pythonz

- Conda

- Pew (disclaimer: I'm the author)

- Virtualenvwrapper

- Pyenv

Etc.

If you argue that people might not move to the latest and greatest as soon as possible due to the fact that people don't build their own interpreter, I can definitely agree with it: python users seem to truly prefer the python version that already comes pre-installed with their linux distribution

Re:Ruby 2.2.0 Released by reledi on Thursday December 25, 2014 @08:19AM (#8796199)
> python users seem to truly prefer the python version that already comes pre-installed with their linux distribution

Definitely. It's not that Python doesn't have the tools to switch between versions, but it's not as prevalent as is in the Ruby community. Most Python users will start their program with shebangs like

    #!/usr/bin/env python
or if they want Python 3+

    #!/usr/bin/env python3
while not necessarily using tools like virtualenv and virtualenvwrapper.

I feel like shebangs are not as commonly used in Ruby, instead you use tools and your Gemfile to specify Ruby version.

Re:Ruby 2.2.0 Released by alxndr on Thursday December 25, 2014 @11:28AM (#8796534)
Unfortunately that's lead me to need to specify my intended ruby version in several places on a ruby project (.ruby-version, Gemfile, CI config file...)
Re:Ruby 2.2.0 Released by weaksauce on Thursday December 25, 2014 @12:36PM (#8796703)
Well, Ruby version and the versions of all your dependencies and the versions of gems for different environments.
Re:Ruby 2.2.0 Released by kennyledet on Thursday December 25, 2014 @01:11PM (#8796764)
pythonz looks great, thanks