3 ms·
I think you shouldn't over-think the question. If you already know C# but are new to Ruby/Django/PHP, it's probably better to go with ASP.NET. I personally go w
by tansey 16y ago
I think you shouldn't over-think the question. If you already know C# but are new to Ruby/Django/PHP, it's probably better to go with ASP.NET. I personally go with ASP.NET for the intellisense and refactoring support of Visual Studio. The main drawbacks for me are that deployment is more difficult and expensive than other frameworks.
If only I could just "azure push"...
- rbanffy 16y ago> If only I could just "azure push"... My bet is that it will be implemented as a button with the Azure logo on it.
- lucisferre 16y agoYeah my biggest pet-peve of being a .NET developer is deployment. It's as if we were never expected to actually ship something in .NET
- luffy 16y agoFor kicks, I deployed the same app on Ubuntu 10.04 and Windows 2008 R2 micro instances on AWS. I chose the plain Windows instance - with no software ( ie, IIS & .NET) pre installed. No database is used in this app. I had the mono/Ubuntu version up and running in about 30 minutes. The longest part of the install was that I chose to use Mono 2.6.7 which isn't officially supported, so you need to do some work to install it. The app was deployed using FastCGI and Nginx. It took about 90 minutes to get the Windows 2008 version running. Most of which time was spent waiting for the instance to start and waiting for the bloody Platform Installer (worst app ever!) to do whatever it does. The moral of this story: the Windows micro instances are unusable. But to scale vertically, use Windows. To scale horizontally, or if you are cheap||frugal, give mono/Ubuntu a shot. Can't wait to see what moving to LLVM is going to do to mono's performance.