Also why aren't we all using or moving to Ruby 1.9, instead of sticking with 1.8?
1.87 is a transitional release designed to ease some of the pain of moving to 1.9. Some gems and libraries, also, aren't fully 1.9 compatible. I think more so than even these is that getting people to change can be fairly difficult.
Ruby Enterprise Edition Version 1.8.7-20090928 Released
21–28 of 28 posts
Re: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#22Earlier quoted context omitted.
I migrated my site to Ruby 1.9.1 about a month ago and it was mostly painless. It's now running up to 4x as fast for some requests! It's finally time to start developing entirely in Ruby 1.9 guys. Trust me.
What does your deployment look like? Nginx/Apache in front of Thin/Mongrel?
Re: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#23Earlier quoted context omitted.
As far as I know: these REE releases/patches are for 1.8.7, a release of Ruby that isn't quite being actively developed, only maintained. Stuff similar to this is being folded into the official Ruby interpreter, which is now at 1.9.1 (1.9.2 soon!). The uptake of Ruby 1.9.1 has been slow, and people are staying on 1.8.7 for compatibility reasons. Thus, these patches are trying to bring better memory performance to the…
Swap 1.8.6 for 1.8.7 and you'd be more correct.
1.8.7 is being developed; 1.8.6 is in maintenance mode by way of EngineYard.
* Ruby 1.9 - Edge version of Ruby
o Ruby 1.9.1 - The latest stable release of Ruby 1.9 series.
* Ruby 1.8 - Stable development version of Ruby
o Ruby 1.8.6 - An ancient stable release of Ruby that Rails users love
o Ruby 1.8.7 - A stable release of Ruby for bridging a gap between the 1.8 and 1.9.
* Ruby - Version-independent topicsRe: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#24Earlier quoted context omitted.
I migrated my site to Ruby 1.9.1 about a month ago and it was mostly painless. It's now running up to 4x as fast for some requests! It's finally time to start developing entirely in Ruby 1.9 guys. Trust me.
What does your deployment look like? Nginx/Apache in front of Thin/Mongrel?
Our 1.9 deployment is Nginx -> HaProxy -> Thin
I had trouble getting Mongrel to work in 1.9 (it was my favorite in 1.8) although apparently you can do it. Thin just worked(tm) so I switched to it painlessly.
Re: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#25Earlier quoted context omitted.
What does your deployment look like? Nginx/Apache in front of Thin/Mongrel?
I'm guessing passenger... they've had support for 1.9 for some time now.
Monit may be harder to set up, but it works very well once it's running.
Re: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#26Earlier quoted context omitted.
I'm guessing passenger... they've had support for 1.9 for some time now.
I ran Passenger for a while in the past but I really didn't like how it would pause every rails process briefly when spinning up a new instance. Maybe that's been fixed now. Monit may be harder to set up, but it works very well once it's running.
Re: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#27Earlier quoted context omitted.
This may sound silly, but I think it's the language barrier. Also, Matz has been very loyal to the core group of Ruby maintainers even after Ruby has gone beyond fad status. Matz has been reluctant to put Ruby on a distributed SCM as well. I expect all of these issues to be resolved within the next few years...
I think you're right about the language barrier. Also, I don't really care if these community enhancements make it to the "proper" Ruby or not. The main thing is that it is available to the community, whether christened as the "Matz" Ruby or not.
Re: Ruby Enterprise Edition Version 1.8.7-20090928 Released
#28Earlier quoted context omitted.
I ran Passenger for a while in the past but I really didn't like how it would pause every rails process briefly when spinning up a new instance. Maybe that's been fixed now. Monit may be harder to set up, but it works very well once it's running.
you mean mongrel? Monit is a monitoring platform...
Ruby has a memory issue with long running processes. They seem to grow and grow and need to be restarted when they get out of hand. People commonly use Monit or God for this.
When you use Passenger, you can have it restart your processes after a certain amount of requests to prevent the memory leak issue, but when it happens it seems to block all requests to all processes for a short time, which is annoying to end users. It means your site can be speedy and zip along, then just pause.