Comments on: Ruby concerns http://www.tarkblog.org/general/245 The personal writings of Caleb and Annie Tennis Sat, 11 Oct 2008 11:28:52 +0000 http://wordpress.org/?v=2.6.2 By: bigD http://www.tarkblog.org/general/245#comment-542 bigD Mon, 19 Dec 2005 19:50:47 +0000 http://www.tarkblog.org/?p=245#comment-542 I bought teh wif some ruby earrings and necklace one tim for valentin's day. It led to good tims for bigD. I bought teh wif some ruby earrings and necklace one tim for valentin’s day. It led to good tims for bigD.

]]> By: Bean http://www.tarkblog.org/general/245#comment-541 Bean Mon, 19 Dec 2005 16:28:42 +0000 http://www.tarkblog.org/?p=245#comment-541 Eye Heart PHP Eye
Heart
PHP

]]> By: slyphon http://www.tarkblog.org/general/245#comment-537 slyphon Mon, 19 Dec 2005 04:46:59 +0000 http://www.tarkblog.org/?p=245#comment-537 I'm afraid I'd have to agree. Last year, i got a job at an enterprise search company and was given the (what at the time) was the short-term task of writing web-based demos of our engine. The language I was writing them in was PHP (and, coming from Python, this was a very unpleasant experience). After 5-6 months of PHP hell, I finally got the team to agree to allow me to write a Rails version. Everyone agreed after a month or two that Rails was a Good Thing, and Ruby was a Great Thing. The problem is that now it's 5 months after I first started writing the Rails demos, and the code is reaching maturity, however there are still some hard-to-track-down bugs in the code that I don't believe are the fault of Rails, or code that I've written. In Debian Sarge's ruby, there are the semi-frequent "[BUG] Segmentation Fault" errors when using development mode. In production, there are inconsistent and frustrating memory leaks, GC issues, and data corruption. (Getting to the point) The most frustrating thing about all of this is that upgrading to 1.8.3 or .4 only introduce *other* issues, and leaks and [FATAL] errors, so there's really no benefit. I have the expectation that the language will tend towards *increasing* stability in the "stable" branch, and Ruby (for all of it's benefits) has been poor in this regard. I'm not going to give up Ruby any time soon (they'll take my .rb files when they pry them from my cold, dead hands!), but I feel like a loving parent with an underachieving child. We all see how great Ruby is, and how much better it will be, but there are these persistent issues that make it difficult to defend attacks from absolute-stability minded hackers. I’m afraid I’d have to agree. Last year, i got a job at an enterprise search company and was given the (what at the time) was the short-term task of writing web-based demos of our engine. The language I was writing them in was PHP (and, coming from Python, this was a very unpleasant experience). After 5-6 months of PHP hell, I finally got the team to agree to allow me to write a Rails version. Everyone agreed after a month or two that Rails was a Good Thing, and Ruby was a Great Thing.

The problem is that now it’s 5 months after I first started writing the Rails demos, and the code is reaching maturity, however there are still some hard-to-track-down bugs in the code that I don’t believe are the fault of Rails, or code that I’ve written.

In Debian Sarge’s ruby, there are the semi-frequent “[BUG] Segmentation Fault” errors when using development mode. In production, there are inconsistent and frustrating memory leaks, GC issues, and data corruption. (Getting to the point) The most frustrating thing about all of this is that upgrading to 1.8.3 or .4 only introduce *other* issues, and leaks and [FATAL] errors, so there’s really no benefit. I have the expectation that the language will tend towards *increasing* stability in the “stable” branch, and Ruby (for all of it’s benefits) has been poor in this regard.

I’m not going to give up Ruby any time soon (they’ll take my .rb files when they pry them from my cold, dead hands!), but I feel like a loving parent with an underachieving child. We all see how great Ruby is, and how much better it will be, but there are these persistent issues that make it difficult to defend attacks from absolute-stability minded hackers.

]]>