4 ms·
99% of my work over the last several years has been with Ruby working within and without Rails in everything between FXRuby apps to Realtime Rails reporting sys
by pjonesdotca 16y ago
99% of my work over the last several years has been with Ruby working within and without Rails in everything between FXRuby apps to Realtime Rails reporting systems.
Please provide an example of your case that Ruby is "just too buggy for serious programming".
thanks.
- joe_the_user 16y agoOK, maybe buggy wasn't the right word. Maybe, "sloppy and ill-defined" - the only Ruby spec is the implementation of Ruby. Maybe, "main implementation problematic" - the main Ruby VM never gives allocated memory back to the system - it garbage collects and keeps it for further allocation. That means that if you copy a 1 gig file, your Ruby instance allocates a gig and keeps it forever (one of the Twitter people described to me his horror at discovering this - two years ago!). That's why its standard to kill Ruby instances after a while in most large Rails installations. Tell me those problems and problem like them are solved and I'll look at Ruby again. It's a beautiful language, the nicest syntax and approach I've seen.
- pjonesdotca 16y agoThanks for answering. Not sure how to address your concerns except that #1 is sort of pedantic. #2 is an interesting issue. Is this true of all versions (jruby, rubinius included) or just the MRI?