31–40 of 45 posts
Earlier quoted context omitted.
Yeah! I plan on to start learning Ruby.
Give Python a look as well. Also, never try to embed Ruby in a C/C++ application it's not designed for it.
Earlier quoted context omitted.
[deleted]
Well depends on the purpose. For general tasks it's really vastly superior to most other languages. I personally don't like some things about the syntax but that's just my personal opinion :)
I've never been so excited for an unstable release. 1.9.2's require was painfully slow without the patch. edit: by "unstable", I mean a dot.uneven number.
1.9.3 is not an unstable release. Ruby uses the third version number to represent a point release, i.e. you can expect 1.9.3 to be more stable than 1.9.2 over time. I think that the versioning policy did work the way you describe it at one point, but it's no longer the case.
x.ODD.z (e.g. 1.7.1) was unstable up until 1.9 though.
ruby-debug19 is still not updated...
Now, plug alert..
I'm having a 2 day 50% off on Ruby 1.9 Walkthrough to celebrate: http://www.rubyinside.com/19walkthrough/ .. Yes, totally a plug, but there isn't any more up to date walkthrough of 1.9 (which includes 1.9.3) so I'll take my chances ;-)
ruby-debug19 is still not updated...
The lack of a working ruby-debug19 has been the only thing keeping me from using 1.9.3.
in case any of you are using rvm, "rvm get head" should update the rvm from the git repository and then you can install ruby the usual way ("rvm install 1.9.3")
Went from leaking MBs per request to no leakage for days.
Earlier quoted context omitted.
Maybe there was something wrong with my 1.9.2, but when working with rails projects (rake, rails console etc), this feels a few orders of magnitude faster.
Here's the whole story behind this speed-up: http://www.rubyinside.com/ruby-1-9-3-faster-loading-times-re...
After running a few tests on the commandline, rake and rails commands are even faster than they were in RC1.
I'm a little unclear about threads in ruby 1.9. I've been told in the past that threads in ruby were problematic. Can anyone illuminate the current state of affairs?
1.8 had green threads and when the interpreter blocked on some operations it would block all the threads. 1.9 uses native threads but it has a global interpreter lock which has known issues. I am not sure what the improvements to locking in 1.9.3, as the changelog has quite a few commits related to that.