Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ruby 1.8.7 retired

ruby-lang.org

Post reply on HN
Print view View original

41–50 of 67 posts

Re: Ruby 1.8.7 retired

#41

Post by judofyr »

__mp wrote: post #37

The whole ruby ecosystem is a nightmare for system administrators. Ubuntu/Debian still ships with ruby 1.8.7 and 1.9.1p0 (which is evil I heard). In order to install a new ruby version one has to most likely compile it from scratch: - Since there are no deb packages and there is no sane way to build deb packages - Overriding system ruby has to be avoided since we manage the whole infrastructure with puppet (yes you c…

Ubuntu/Debian does not ship with Ruby 1.9.1. They ship with Ruby 1.9.3 under the name of "ruby-1.9.1" because they are ABI compatible.

Re: Ruby 1.8.7 retired

#42

Post by jrochkind1 »

charliesome wrote: post #7
sergiotapia wrote: post #5

Earlier quoted context omitted.

No more RVM! Fantastic news!

Please don't let that tempt you to use system Ruby. You should always build your own, especially on a system like OS X. System Ruby is not there for you, it's there for the system to make use of (and yes, OS X does ship with quite a few Ruby scripts and a couple of Rails applications). Apple makes no guarantees of keeping this Ruby up to date.

What are the Rails applications OSX ships with? I have never heard of or noticed this before.

Re: Ruby 1.8.7 retired

#43

Post by JshWright »

bdcravens wrote: post #26
IzzyMurad wrote: post #22

That's exactly why I went with Django/Python instead of RoR/Ruby. I have no problem with keeping software up-to-date but I don't want to make that a main task because some "cool" kids easily get bored and keep phasing out stuff which break production apps and/or causes security issues.

Doesn't Django/Python have its own version headaches? (Python 3 came out 5 years ago, but Django didn't officially support until February of this year) Phasing out old version of the underlying language isn't uncommon. For example, Oracle doesn't even support Java 6 anymore, which was released in 2007.

I think the difference is that Python had a much more realistic plan for the backwards incompatible changes. The fact that the transition will likely take the better part of a decade is a _feature_, not an issue (and there will be supported versions of 2.x throughout that time).

Re: Ruby 1.8.7 retired

#44

Post by JshWright »

jammi wrote: post #33
IzzyMurad wrote: post #22

That's exactly why I went with Django/Python instead of RoR/Ruby. I have no problem with keeping software up-to-date but I don't want to make that a main task because some "cool" kids easily get bored and keep phasing out stuff which break production apps and/or causes security issues.

Yeah, there's nothing like the Python 2 to Python 3 transition going on there for the umteenth year.

The difference is, the Python developers had a realistic view of what this transition would look like, and it's very intentional that it will have taken the better part of a decade by the time all is said and done.

Re: Ruby 1.8.7 retired

#45

Post by evilduck »

jrochkind1 wrote: post #42
charliesome wrote: post #7

Earlier quoted context omitted.

Please don't let that tempt you to use system Ruby. You should always build your own, especially on a system like OS X. System Ruby is not there for you, it's there for the system to make use of (and yes, OS X does ship with quite a few Ruby scripts and a couple of Rails applications). Apple makes no guarantees of keeping this Ruby up to date.

What are the Rails applications OSX ships with? I have never heard of or noticed this before.

I don't know what "vanilla" OSX ships with, but I've seen references to Rails pop up in logs in Console.app for my OSX Server when I was screwing with replacing their Postgres db with my own.

Re: Ruby 1.8.7 retired

#46

Post by UNIXgod »

X-Istence wrote: post #24
UNIXgod wrote: post #23

Earlier quoted context omitted.

There's gentoo/alt and fink which predates DarwinPorts. I'm sure there is even a pkgsrc user out there. I've occasionally used this one called make. It's sort of a meta language to homebeer. In fact it comes in two flavors pmake and gmake. =P

You forgot bsdmake ... which up until OS X ML was still available on OS X.

I didn't forget it. That is pmake my friend =)

Re: Ruby 1.8.7 retired

#47

Post by wwweston »

pvnick wrote: post #8

My goodness, I have very little experience with Ruby and I'm currently in the process of trying to get a rails 3 app from github running on my osx system (1.8.7 default ruby version). I have spent the past several hours fighting with ruby versions and dependencies with the only glimmer of hope being successfully getting a hello world rails 4 app running. Seriously I thought ruby was supposed to be a beacon of simplic…

I've got a theory that this is one of the reasons that system configuration/deployment aids are so popular right now. My experience has been that there's trouble with this every time I spin up a new Ruby project (particularly Rails) and/or move to a new system. It does tend to get better as you get into individual projects, though.

Re: Ruby 1.8.7 retired

#48

Post by MattBearman »

pvnick wrote: post #8

My goodness, I have very little experience with Ruby and I'm currently in the process of trying to get a rails 3 app from github running on my osx system (1.8.7 default ruby version). I have spent the past several hours fighting with ruby versions and dependencies with the only glimmer of hope being successfully getting a hello world rails 4 app running. Seriously I thought ruby was supposed to be a beacon of simplic…

I found similar problems trying to get Rails running on OSX Lion. In the end I just went to using virtual machines running Ubuntu for development. I didn't bother with RVM, I just installed Ruby with apt-get and it was all really straight forward.

Re: Ruby 1.8.7 retired

#49

Post by IzzyMurad »

VeejayRampay wrote: post #34
IzzyMurad wrote: post #22

That's exactly why I went with Django/Python instead of RoR/Ruby. I have no problem with keeping software up-to-date but I don't want to make that a main task because some "cool" kids easily get bored and keep phasing out stuff which break production apps and/or causes security issues.

You went with Django/Python eh? Which Python exactly? 2.6? 2.7? 3.3? That a Python user of all people would whine about lack of stability and consistency is extremely funny.

Django 1.5 (latest stable version) requires Python 2.6.5 or above, so it doesn't matter.
Post reply on HN