Comments on: Ruby at 60 http://gurge.com/blog/2006/10/16/ruby-at-60/ Thu, 20 Nov 2008 22:22:52 +0000 http://wordpress.org/?v=2.3.3 By: Jf http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-5277 Jf Thu, 10 May 2007 03:42:18 +0000 http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-5277 You might be interested in reading my relatively early evaluation of Ruby. I'm a big fan of this post, though. http://fallenearth.org/blogs/barncover/2007/05/09/ruby-sparkles-and-impurities/ You might be interested in reading my relatively early evaluation of Ruby. I’m a big fan of this post, though.

http://fallenearth.org/blogs/barncover/2007/05/09/ruby-sparkles-and-impurities/

]]> By: Barn Cover » Blog Archive » Ruby - Sparkles and Impurities http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-5276 Barn Cover » Blog Archive » Ruby - Sparkles and Impurities Thu, 10 May 2007 03:40:50 +0000 http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-5276 [...] This is actually an old post that doesn’t display properly on my old blog, but which I feel has relevant information for this one. It’s also a precursor to a post I’ll hopefully make this week or next about the progress I’ve been making in the last–oh, MONTH? I decided to repost this because I read another good blog post griping about Ruby. [...] […] This is actually an old post that doesn’t display properly on my old blog, but which I feel has relevant information for this one. It’s also a precursor to a post I’ll hopefully make this week or next about the progress I’ve been making in the last–oh, MONTH? I decided to repost this because I read another good blog post griping about Ruby. […]

]]> By: Sam http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-66 Sam Wed, 18 Oct 2006 07:27:55 +0000 http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-66 So many of these problems would just vanish with the availabililty of a real honest-to-goodness interactive source-level debugger. It would not be difficult to provide -- with late-bound languages like ruby, python, and perl, even edit & continue is trivial. A decent debugging environment should be able to single step between script language and native code, too. It is an amazing testiment to the attractiveness of these scripting languages that they are so popular even though the complete lack of modern tools forces you back into 1960's mainframe-style development techniques. So many of these problems would just vanish with the availabililty of a real honest-to-goodness interactive source-level debugger. It would not be difficult to provide — with late-bound languages like ruby, python, and perl, even edit & continue is trivial. A decent debugging environment should be able to single step between script language and native code, too. It is an amazing testiment to the attractiveness of these scripting languages that they are so popular even though the complete lack of modern tools forces you back into 1960’s mainframe-style development techniques.

]]> By: Ken http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-63 Ken Mon, 16 Oct 2006 20:47:20 +0000 http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-63 I'll give you good odds that ruby will not kill perl any more than C++ killed C. In the near term Python seems to be a more realistic potential victim, as ruby sucks up any "new for newness's sake" interest that Python still has going for it. In the long term I think that Java stands the to lose the most as Ruby (with and without Rails) matures into to a "better" platform for building web apps. I’ll give you good odds that ruby will not kill perl any more than C++ killed C. In the near term Python seems to be a more realistic potential victim, as ruby sucks up any “new for newness’s sake” interest that Python still has going for it. In the long term I think that Java stands the to lose the most as Ruby (with and without Rails) matures into to a “better” platform for building web apps.

]]> By: joe http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-62 joe Mon, 16 Oct 2006 20:30:40 +0000 http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-62 re: the ++ operator That really <a href="http://www.43things.com/entries/view/295456" rel="nofollow">bugged me too</a> when I started writing ruby. re: the ++ operator

That really bugged me too when I started writing ruby.

]]> By: Steve http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-61 Steve Mon, 16 Oct 2006 20:09:08 +0000 http://gurge.com/blog/2006/10/16/ruby-at-60/#comment-61 Great article - I've been on about the same timeline on Ruby and agree with your observations. The biggest problem with Ruby is the culture: monkey patching is evil and should be abandoned but it seems like a lot of community members just love it. It will surely cause problems in the future, especially if the core libraries continue to rely on it to fix stuff, rather than refactoring to fix the actual problems.. Thanks for the thoughts! Great article - I’ve been on about the same timeline on Ruby and agree with your observations. The biggest problem with Ruby is the culture: monkey patching is evil and should be abandoned but it seems like a lot of community members just love it. It will surely cause problems in the future, especially if the core libraries continue to rely on it to fix stuff, rather than refactoring to fix the actual problems.. Thanks for the thoughts!

]]>