Great work. Thanks for the Christmas gift. btw: anyone else thinks Rails was mentioned too much in the release note?
Rails was mentioned once, unless I missed something.
Ruby 2.2.0 Released
11–20 of 82 posts
Re: Ruby 2.2.0 Released
#12Great work to the ruby team, the improvements in Ruby's performance since 2.x have been very impressive to say the least. Well done and Merry Christmas to everyone that worked hard on this release.
Indeed, by upgrading Ruby from 1.9.3 to 2.1.2 we cut the time spent running our specs in half for our Rails project.
You should get another boost with 2.2. This release is much faster, I've noticed.
Re: Ruby 2.2.0 Released
#13Re: Ruby 2.2.0 Released
#14It's a bit weird that symbols are garbage collected. I wouldn't think it could delete them without making the same symbols unequal some of the time.
They are only garbage collected if they were introduced at runtime and there is no reference to them anymore. (detailed explanations can be found in the presentation linked in the announcement)
This allows you to symbolize external hash keys without fear of a DOS attack.
Re: Ruby 2.2.0 Released
#15Great work. Thanks for the Christmas gift. btw: anyone else thinks Rails was mentioned too much in the release note?
Yes I also thought the same thing... on the other hand, it shows dedication to the most important driver of Ruby adoption.
I'm not sure, most of my Ruby jobs are puppet and chef nowadays.
Re: Ruby 2.2.0 Released
#16Ruby seems to continuously move forward. Great to see that they manage to keep this project alive without a python 2vs3 disaster.
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
#17Interesting: vfork support.
Vfork in most older systems is like fork except it doesn't deeply duplicate all process state immediately (file handles, memory, such), so it can be faster if all the app wants to do is fork/exec. (We had to implement both fork and vfork in minix 2.x in uni.^)
But according to SO, most OSes implement fork lazily, so there's not much point in using it when fork will be just as fast without any change.
If there were a slowly-performing platform that has a specific performance issue identified by profiling as caused by fork, then mature optimization could follow. Otherwise, it seems like adding LoC without a clear goal.
The Symbol GC sounds good. Maybe this will imply code can associated with classes and modules can be GCed and required anew once all objects are freed (live upgrade apps without restarts).
^ The first thing I did to the Minix codebase was set keyboard repeat rate to the fastest possible values. Everyone else seemed content to waste their life waiting for their editor and debugger to move at a snail's pace. Of course, no else had x86 asm / pc hw io experience.
Re: Ruby 2.2.0 Released
#18Earlier quoted context omitted.
Yes I also thought the same thing... on the other hand, it shows dedication to the most important driver of Ruby adoption.
I'm not sure, most of my Ruby jobs are puppet and chef nowadays.
I promise that puppet and chef are not how the majority of people first hear of Ruby.
Re: Ruby 2.2.0 Released
#19Ruby seems to continuously move forward. Great to see that they manage to keep this project alive without a python 2vs3 disaster.
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.
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
#20[deleted]