Hacker News Reader

Comment by _pius | Hacker News Reader

I'm loving Rails 3 Beta 1, but I'm surprised they've broken Ruby 1.9.1 compatibility with today's release. Not to be a hater, but I don't see the point of releasing a new beta after introducing a regression so serious that it causes the framework to segfault on the current stable Ruby.

View on HN

I don't think it's a bad thing. Ruby 1.9.1 needs to go. There are a number of bugs and quirks in 1.9.1 which have been fixed in 1.9.2. E.g. while developing Phusion Passenger I've noticed some VM deadlock bugs, all of which are now fixed.

Ruby 1.9.1 needs to go.

I agree, but I don't think Ruby 1.9.2 is slated for release until the end of August.

Well, that's less than 3 months away. Not so bad.

1.9.2 release plan, for those who missed it:

  - 31 Mar.  freeze the spec
  - 30 Apr.  freeze the code
  - 31 May.  release 1.9.2-preview2
  - 30 Jun.  release 1.9.2-rc
  - 31 Jul.  release 1.9.2-p0

It shouldn't even be possible to segfault an interpreted language like Ruby, let alone the "current stable" version. Sounds like it's Ruby-core's problem, not Rails-core's.

That said, I agree with you, it's strange. But I do think it's good they're pushing so hard for 1.9.2.

It shouldn't even be possible to segfault an interpreted language like Ruby, let alone the "current stable" version. Sounds like it's Ruby-core's problem, not Rails-core's.

Heh, good point.

Reply on news.ycombinator.com