Why would a .NET programmer learn Rails? 5
Stephen Chu has a nice article over at InfoQ about why a .NET programmer would want to learn Rails.
There are a few hurdles I had to go through in learning Ruby. First, I had to go through the emotions of accepting the fact that it will take longer to find a new Ruby solution than to use an existing technology that I am comfortable in. This is by far the most painful experience. But, after a while, you will start cherishing the fact that you are starting to develop multiple ways to solving different problems, and that’s where the pleasure comes in.
Good stuff, Stephen.
I think you summed it up nicely. New ways of solving problems, differently, sometimes more elegantly, other times more effectively, but in some cases, less so. It's a matter of picking and choosing the right tools.
Oh, and also, .NET is definetely not the best choice for a quick and dirty application with a simple db backend that is used for example on an intranet. There's too many hoops to jump through to get even the simplest stuff up, doing the same little things in all sorts of different places. I enjoy the DRY philosophy, even if it is only pragmatic. - ben @ http://rubyonrailsblog.com
I completely agree with the article. From my experience, learning Ruby made me a better C# developer. Learning Rails made me realize how much better things can be in ASP.NET. Web development does not have to be that hard… Now I am just waiting for the ActionPack for .NET. :)
The architectonic of practical reason proves the validity of our sense perceptions, but the things in themselves are by their very nature contradictory.
Pure reason excludes the possibility of the Antinomies.