In the end it all boils down to use the best tool for you for the job you're working on. That aside, going from Rails to .NET MVC has been a lesson in patience

In the end it all boils down to use the best tool for you for the job you're working on. That aside, going from Rails to .NET MVC has been a lesson in patience. While I am glad to have skipped Webforms, there is still something about .NET MVC that weighs on new ideas. It's just easier to get up and running with a Rails stack and get your idea out there. But that's just me, maybe for you it's Python, or C or Assembly. Whatever it is you work best in that's what you use. Posts like this can help a community identify weak points though so I'm always glad to see them.