Ask HN: Is using ASP.NET MVC, C# with Azure a bad idea for startup?
I have idea that I want to start working on (website first). I have experience with Microsoft stack c#, asp.net MVC 5 and Azure. I think these are very good tools if not the best. I am very excited for MVC 6. The only concern I have is to find people who would want to join me (In case I am on to something). the other option is to learn latest technologies in open source world and AWS but that will require lot of learning time for me.
Any thoughts?
22 comments
[ 3.2 ms ] story [ 65.1 ms ] threadI doubt that the .NET stack is the "best" for anything. But that's something to consider later down the road once you've proven your idea is good enough to warrant more sweat investment.
(Full disclosure: I build things using both ASP.NET MVC and node.js: they both have their strengths, and both have their weaknesses). Which one is "best"? IMO, it depends on the context, and what you're trying to do.
They're using NancyFX for their application server. MVC 5 for the consumer-facing website. Mobile app is written in C# using Xamarin.
We're in a smaller city, where everyone seems to use .NET, so finding people OUTSIDE the .NET world is actually a bigger problem where I'm at. Silicon Valley is certainly the exact opposite.
FYI go check out BizSpark which is a pretty amazing program - 60k/yr of hosting credits and whilst you continue to host on Azure there are no licensing costs. Architect your software stack properly using repositories/interfaces and develop against these if you are worried about lock-in to Azure - done correctly it will allow you to adopt a hybrid approach of mix and match of offerings between vendors.
Some basic considerations:
a) Ability to find quality .NET talent in your local area? (It's not hard to stand out and attract quality developers in .NET simply by adopting a strong open-source usage/contribution policy. Using languages such as F# behind the scenes will make you stick out even more.)
b) .NET makes hiring simpler - you'll obtain the opportunity to use and reuse the same language/code on the server-side as on the client side. Using Xamarin means you don't need to hire a Android mobile guy to do the app, then hire a iOS guy to redo the same project in another language. You get product/feature release parity for essentially free.
c) Are you in this for the long haul or are you aiming for exit? If exit consider the technology stack of potential acquirers.
For example, I wouldn't consider a job working with that kind of stack and I'm sure many other people like me exist.