Rails and ASP.NET MVC when to use each?

we have a mixed development environment using ASP.NET MVC and Ruby on Rails. We have come from a purely C# / ASP.NET background, but now have some rails experience and we love both. Problem is deci开发者_运维问答ding at the beginning of a project which one to use can sometimes be tricky.

Any tips for how to explain to the non technical members of our company and our clients why we would chose one over the other for various projects?

Thanks in advance.

---

• Deployment? Rails is interpreted, ASP.NET MVC requires compiling.
• Speed? One's bound to be faster than the other, I'm assuming (although I cannot be certain) that ASP.NET MVC would be slightly faster as its compiled.
• Platform? ASP.NET MVC obviously has to run in a Windows environment, whereas Rails could run on *nix/Windows/Mac
• Development time? You're all going to be more familiar with the constructs of one system over another meaning one will take you longer to develop in. If speed of development is required, one will be preferable.

---

To be honest if they are non-technical, why would it matter to them? It's pretty rare for a customer to come and ask for a specific technology, and it sounds like you would be picking for them. Then presumably they would trust you to pick the appropriate technology.

If you have to justify to management, I can see that mattering, though. I have developed mostly with Rails and a little with ASP.Net and I do have a favorite, in Rails. That said, I would just fall back on my default and then just tell them the requirement that requires me to jump to the other technology. They can probably understand most reasons, like the ones illustrated by Kezzer.

---

Any tips for how to explain to the non technical members of our company and our clients why we would chose one over the other for various projects?

If they're non-technical, I don't see why they would care.

However, you could just tell them Microsoft made ASP.NET MVC while Ruby on Rails was not made by Microsoft.

Or, for which ever one you choose, just tell them it gets the job done the fastest/easiest.

Giving them a good response would require them to be technical (performance, compiling, etc..).