Boy, what ISN’T destroying Ruby these days?

February 26, 2008 at 8:37 pm · Filed under Ruby

What else?

(Note: Charles Oliver Nutter is helping when he tells us that Thread#raise, Thread#kill, and timeout.rb are broken.)

7 Comments »

  1. James Britt said,

    February 26, 2008 @ 10:30 pm

    No sense of history

  2. Devender said,

    February 27, 2008 @ 1:19 am

    I hope nothing kills Ruby, I love the language though I have experimented with other like Erlang and Python I keep going back to Ruby for doing everything.

  3. Sidu said,

    February 27, 2008 @ 3:05 am

    Much of what is listed is true, but some of these points are outdated. Among the outdated bits are:
    MRI/YARV/Rubinius/JRuby/XRuby, or ‘The Impending Ruby Fracture’ was written over a year and a half ago and none of David’s fears predicted has come to pass.
    JRuby, Rubinius and IronRUby all strive to remain true to CRuby and Ruby 1.9 is out (though every one isn’t that happy with it).

    Slowness: I’ve been running trunk builds of JRuby (we’re currently at 1.1 RC1 I think) and it is WAY faster than CRuby. At least 100% faster and often 200 to 500% faster. Ruby 1.9 is pretty good too. I tested one aspect (block invocation) here http://blog.sidu.in/2008/01/ruby-blocks-redux-ruby-190-ruby-186-and.html and the numbers are very interesting.

  4. E. James O'Kelly said,

    February 27, 2008 @ 9:52 am

    Funny, most of what you listed I see as strengths. Monkey-patching? Obviously you haven’t been forced to wait for vendor updates to a closed language. Cleverness? It’s what gets me up in the morning. No one true way? A bit fascist aren’t we? Freedom is good. YARV, JRuby, etc… Competition did well for evolution, it does well for language as well.

    As far as slowness…. easily overcome by using YARV, Rubinus, etc. Personally I wish it was faster, but I still find no NEED for any of the alternate implementations, Matz Ruby is fine with me. Most of us don’t get twitter traffic.

  5. Chris said,

    February 27, 2008 @ 10:43 am

    Maybe another thing destroying Ruby is the inability of Rubyists to read sarcasm in criticism of Ruby. ;)

  6. Jordan Glasner said,

    February 29, 2008 @ 10:14 am

    Ha, thanks Chris. Exactly what I was thinking :)

  7. markus said,

    March 4, 2008 @ 6:56 am

    “monkey-patching” is an insulting term for one strategy one can use in ruby.

    I believe not everyone is capable of deciding what feature to use in ruby and which to not use.

    In Python you have guido deciding what you will need.

    In Ruby *gasp* you have to take your own brain cells to do this job!

    ;-)

RSS feed for comments on this post · TrackBack URI

Leave a Comment