3 ms·

Ruby 1.9.1 Released: First Stable Ruby 1.9 Release

47 points by mdasen 18y ago

deleted 18y ago
[deleted]
ROFISH 18y ago
I know the Rails team has worked hard towards getting 1.9 compatibility, but what are your opinions about using this on production servers? (I'm kinda edgey myself, it's why I ask.)
- fizx 18y ago
  Not yet. Think about all of the gem/plugin dependencies which may not be 1.9 compatible.
  - voxxit 18y ago
    Technically, you could check your gems, see which ones are not 1.9 compatible, fix the gems, and then release. :)
  - jcapote 18y ago
    But your saying that an out of the box rails 2.2.2 site works on ruby 1.9? If so, that's the first I've ever heard of it...
    - catch23 18y ago
      in the rails 2.2 release notes, it did mention 1.9 compatibility.
    - sho 18y ago
      I think Rails itself works, the problem is the servers. Mongrel doesn't work on 1.9, and the others have problems too. Also the DB libraries. Plenty of other gems don't work either, basic ones like JSON (works only in pure Ruby mode). Hopefully the stable 1.9 release spurs maintainers on a bit, but I imagine it'll take a while.
      - catch23 18y ago
        Then there are the DB libraries that only work in 1.9 like NeverBlock.
- nickb 18y ago
  I wonder what will happen to 1.9 branch. It's not supported well by anything. 1.9 is suppose to be a transitional branch anyway... a place where Matz can experiment a bit. 2.0 is suppose to be the next big thing (like Python 3000) but I have no idea if that will ever see the light of the day. I'm placing my bets on JRuby, Rubinius and MagLev in the meantime.
  - acangiano 18y ago
    Actually nickb, 1.9.1 is no longer thought of as a transitional/development release. It's a stable release we are all expected to migrate to sooner or later.
    - carbon8 18y ago
      This change in what version numbers mean definitely isn't known by the entire Ruby community. The O'Reilly books' statements about 1.9 versions being development versions and the fact that 1.9 has been in development until today has made this a little confusing.
  - catch23 18y ago
    I think we were all just used to seeing even numbers as stable release versions. I don't think there's anything wrong with having odd number production release versions. Also, 1.9 wasn't really an experimental place for Matz, it was initially YARV then Matz conceded it to be the next official ruby branch. None of the future VMs will/have been done by Matz. He actually joked about that during RubyConf 2007... the reason ruby VMs became fast was because Matz was taken out of the picture.
glomek 18y ago
I heard years ago that Ruby 1.9 was going to have tail call optimization, but I can't find it anywhere in the news file. Does anyone know if this made it in or not?
- catch23 18y ago
  I think it's been implemented in 1.9 for a long time, but it's not enabled by default. You have to set a #define to configure it, however I don't know why it's not enabled by default. Maybe someone in the "know" can tell us why.
  - Freaky 18y ago
    "In fact, I don't check this option. So some bugs may hide on this option. And backtrace (what you see on exception) is changed. It's convention issue." -- http://www.ruby-forum.com/topic/164263 http://www.ruby-forum.com/topic/164263

47 points by mdasen 18y ago

deleted 18y ago

[deleted]

I know the Rails team has worked hard towards getting 1.9 compatibility, but what are your opinions about using this on production servers? (I'm kinda edgey myself, it's why I ask.)

fizx 18y ago
Not yet. Think about all of the gem/plugin dependencies which may not be 1.9 compatible.
- voxxit 18y ago
  Technically, you could check your gems, see which ones are not 1.9 compatible, fix the gems, and then release. :)
- jcapote 18y ago
  But your saying that an out of the box rails 2.2.2 site works on ruby 1.9? If so, that's the first I've ever heard of it...
  - catch23 18y ago
    in the rails 2.2 release notes, it did mention 1.9 compatibility.
  - sho 18y ago
    I think Rails itself works, the problem is the servers. Mongrel doesn't work on 1.9, and the others have problems too. Also the DB libraries. Plenty of other gems don't work either, basic ones like JSON (works only in pure Ruby mode). Hopefully the stable 1.9 release spurs maintainers on a bit, but I imagine it'll take a while.
    - catch23 18y ago
      Then there are the DB libraries that only work in 1.9 like NeverBlock.
nickb 18y ago
I wonder what will happen to 1.9 branch. It's not supported well by anything. 1.9 is suppose to be a transitional branch anyway... a place where Matz can experiment a bit. 2.0 is suppose to be the next big thing (like Python 3000) but I have no idea if that will ever see the light of the day. I'm placing my bets on JRuby, Rubinius and MagLev in the meantime.
- acangiano 18y ago
  Actually nickb, 1.9.1 is no longer thought of as a transitional/development release. It's a stable release we are all expected to migrate to sooner or later.
  - carbon8 18y ago
    This change in what version numbers mean definitely isn't known by the entire Ruby community. The O'Reilly books' statements about 1.9 versions being development versions and the fact that 1.9 has been in development until today has made this a little confusing.
- catch23 18y ago
  I think we were all just used to seeing even numbers as stable release versions. I don't think there's anything wrong with having odd number production release versions. Also, 1.9 wasn't really an experimental place for Matz, it was initially YARV then Matz conceded it to be the next official ruby branch. None of the future VMs will/have been done by Matz. He actually joked about that during RubyConf 2007... the reason ruby VMs became fast was because Matz was taken out of the picture.

glomek 18y ago

I heard years ago that Ruby 1.9 was going to have tail call optimization, but I can't find it anywhere in the news file. Does anyone know if this made it in or not?

catch23 18y ago
I think it's been implemented in 1.9 for a long time, but it's not enabled by default. You have to set a #define to configure it, however I don't know why it's not enabled by default. Maybe someone in the "know" can tell us why.
- Freaky 18y ago
  "In fact, I don't check this option. So some bugs may hide on this option. And backtrace (what you see on exception) is changed. It's convention issue." -- http://www.ruby-forum.com/topic/164263 http://www.ruby-forum.com/topic/164263