Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.
Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.
I don't have any hard numbers to back this up, but based on personal experience almost exclusively all of the best engineers I have worked with prefer to work with open source technologies and would not touch .NET. One can think of several reasons for this correlation that make intuitive sense.
If pressed for work I'd even work sooner in a Node.JS shop, even if I feel that Node.js is attracting the sort of developers the Ruby community tries to break away from (i.e. the PHP and Java guys)
I'm sure there are good .NET engineers out there, but hiring/finding them is more like finding a needle in the haystack.
Also the vast majority of startups not building tech can get by with basic CRUD like apps for most of their business processes. Whatever gets you to market fastest. You will end up rewriting everything 3 times over probably in your company's life as I've learned but you won't get to do that unless you ship something.