Why Would a .NET Programmer Learn Ruby on Rails?
Very well written and thoughtful article by Stephen Chu up at InfoQ.
To be fair, I still think .NET is great. It has offered me a place where I am consistently delivering great business value to my clients. However, I constantly remind myself that there are multiple ways and numerous technologies to solving a single problem, some better than others. By being loyal to one technology stack, I am bound to unconsciously make biased decisions, which will ultimately hinder my ability to deliver business value.
Here's some choice tidbits, emphasis mine:
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. Secondly, reading about Ruby/Rails only gets me so far. Practically using what I have learned helps me to remember what I have learned. Remember, use it or lose what you have invested time to read about.
This article says, better than I could, why .NET folks should look at Rails. If you're resistant to change (or installing things) try Instant Rails. If you refuse to install anything, and still want to Try Ruby, then try it directly in your browser.