Been working with it off and on for over a year, now. Would do it full time if I could make it pay.
In case you missed it, "doesn't scale" is an "inside rails" joke. NYT ran their election site last year on it, for one real-world example of "scales very well, thank you."
I'm extremely impressed with the ruby language; some pieces of Rails not so much, but with the merger with merb happening this year, Rails 3.0 is looking quite good, thank you.
The standard ruby interpreter on most systems seems to still be 1.8.x which is troubling, as 1.9.x is much faster, but the way they revised thread support in it broke a few things; use Is It Ruby 1.9? to see if you can switch to it.
Since the thread model in standard ruby interpreters is broken by design, probably the fastest and most solid interpreter to use at the moment is jRuby (disclaimer, I haven't tried IronRuby, the CLR implementation of it) at least until MagLev ships. Ruby 1.9.x is a step forward, but still isn't using native system threads (it imposes a lock to keep threads from running on multiple cores in a multi-core processor; IOW, ruby 1.9.x will only run on one core of your server's quad-core processor, while jRuby will cheerfully scatter its threads over all available cores). In a recent benchmark test, jRuby solved the Josephus problem just a smidge faster than ruby 1.9 (but both beat PHP5 by a factor of 4, if you want some context).
Great to find another Rails head in this territory.
have fun,
arlen
----------
In God We Trust, all others must provide data.
I heard
it doesn't scale....
I do
Been working with it off and on for over a year, now. Would do it full time if I could make it pay.
In case you missed it, "doesn't scale" is an "inside rails" joke. NYT ran their election site last year on it, for one real-world example of "scales very well, thank you."
I'm extremely impressed with the ruby language; some pieces of Rails not so much, but with the merger with merb happening this year, Rails 3.0 is looking quite good, thank you.
The standard ruby interpreter on most systems seems to still be 1.8.x which is troubling, as 1.9.x is much faster, but the way they revised thread support in it broke a few things; use Is It Ruby 1.9? to see if you can switch to it.
Since the thread model in standard ruby interpreters is broken by design, probably the fastest and most solid interpreter to use at the moment is jRuby (disclaimer, I haven't tried IronRuby, the CLR implementation of it) at least until MagLev ships. Ruby 1.9.x is a step forward, but still isn't using native system threads (it imposes a lock to keep threads from running on multiple cores in a multi-core processor; IOW, ruby 1.9.x will only run on one core of your server's quad-core processor, while jRuby will cheerfully scatter its threads over all available cores). In a recent benchmark test, jRuby solved the Josephus problem just a smidge faster than ruby 1.9 (but both beat PHP5 by a factor of 4, if you want some context).
Great to find another Rails head in this territory.
have fun,
arlen
----------
In God We Trust, all others must provide data.