Came across this post by Mark Haliday on the Rails mailing list today and thought you fellow .Net developers might find it funny.

Why RoR sucks: 1. It’s smarter than me. Just when I think I’ll have to do some mundane thing (like I use to in PHP or ASP), I find out RoR does it already for me. 2. It takes about half or less code to put my stuff together in RoR than it did in PHP, ASP, ASP.NET, etc. It seems so unnatural that I can have a method with only 4 lines of code, and three of those were error handling – YET it does what it should, no fuss, no muss. 3. I use to worry about giving my client an estimate and then running over the alloted hours BIGTIME. Now, RoR has me UNDER the hours consistently. I feel so dirty now still giving my old school estimates that ASP smashed into my head repeatedly knowing I had to hand hold it all the way. 4. I can finally take those jobs that require “the other” databases like Postgresql, MySQL, etc. without rewritting my data layer. 5. RoR took away my connection strings! Now its just too easy :-) 6. RoR makes it easy to run tests across my code, next it will generate docs for me from my code … oh wait it’s buddy RDoc does that now…. 7. I use to enjoy those frustrating nights banging my head against the wall trying to figure out why my site worked on Windows 2000 but not Windows 2003, now with RoR, my sites “just work”. 8. Now when I see a .NET article I cannot seem to stop yawning. How many MSDN magazines now sit beside my desk STILL in their plastic wrappers? 9. AJAX in a few lines of code?? But, but ASP.NET taught me it takes a good 20+ lines AT LEAST.

If you want to you can read the thread that got spawned by Mark’s original post.