from http://feeds.feedburner.com/~r/AyendeRahien/~3/160655144/JAOO–Day-I.aspx
I like the ideas being evolved in Ruby, but I have reservation about doing development there. I know that I say this as a person who didn’t do any real project there, but I have the feeling that Ruby isn’t for me. Basically doesn’t provide a significant advantage over what I already have in .Net
Wow. I have to say I agree, but I couldn’t spell it out the same as Oren does. I don’t think my reasons are exactly the same, since I deal very little with profiling, debugging, deployment and monitoring.
With all the talk about Ruby recently in the .NET community, I find this quote to be refreshing. Some people are suggesting that we just jump ship and join the Ruby camp like many Java people did over the past few years. Jeremy Miller write a little bit about it recently in some thoughts about ALT.NET.
More than one person has questioned whether or not the ALT.NET canon and crowd is inevitably destined for Ruby and Ruby on Rails. There’s some thought, and at this point observation, that the alpha geeks in .Net are starting to drift into Ruby development instead.
Right now, for me, the major frustration is what Jeremy calls “MSDN way”. Bad (non-alt.net) development is done by many shops whose development environment consists of ONLY a Visual Studio installation. Not using excellent open tools like NUnit or MbUnit, StructureMap or Windsor, NMock or RhinoMocks, and others, these are the reasons why the “alpha geeks” are jumping to Ruby. Right now the average Ruby developer understands using open libraries. Most .NET shops don’t seem to think this way. We need to change our way of thinking.