Earlier quoted context omitted.
99% of startups simply will never hit the performance problems you seem to be talking about.
Yeah but its the ones that matter, that do? The successful ones with traction.
Ask HN: Would a .Net back-end put off potential acquisitors?
61–70 of 103 posts
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#62I'd like to raise a related point. While I think it's too early to worry about acquisitions, a .NET stack may put off early employees. Many engineers want to work with "hot" technologies for professional development reasons. For example, I would not work for a company whose stack is built on top of PHP or .NET, regardless of pay. Not because these are "bad" technologies (in fact, they are a lot more stable than the h…
> a .NET stack may put off early employees. 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.
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#63The primary concern, if you are funding this and building this yourself, is getting to market. Each day is coming out of your pocket. Choose the technology stack that gets you off the ground fastest. A suitor is not going to reject your company because you aren't using the "hot" technologies.
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#64> If it makes any difference, I am funding this myself initially. The primary concern, if you are funding this and building this yourself, is getting to market. Each day is coming out of your pocket. Choose the technology stack that gets you off the ground fastest. A suitor is not going to reject your company because you aren't using the "hot" technologies.
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#65Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#66I'd like to raise a related point. While I think it's too early to worry about acquisitions, a .NET stack may put off early employees. Many engineers want to work with "hot" technologies for professional development reasons. For example, I would not work for a company whose stack is built on top of PHP or .NET, regardless of pay. Not because these are "bad" technologies (in fact, they are a lot more stable than the h…
> a .NET stack may put off early employees. Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#67Earlier quoted context omitted.
> a .NET stack may put off early employees. Any choice may put off early employees. By sheer numbers, choosing .NET gives you a much larger hiring pool than, say, Haskell or NodeJS.
Yes, but it's not about the size of the hiring pool. It's about the "quality" of the hiring pool (HN likes to call them 10x engineers). 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 intui…
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#68Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#69Earlier quoted context omitted.
Yes, but it's not about the size of the hiring pool. It's about the "quality" of the hiring pool (HN likes to call them 10x engineers). 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 intui…
Observer bias.
I'm sure there are good .NET engineers out there, but hiring/finding them is more like finding a needle in the haystack.
Re: Ask HN: Would a .Net back-end put off potential acquisitors?
#70This hits hiring as well. Someone mentioned the quantity of .NET programmers, and while this is true the quality is extremely, extremely poor on average. Having had to hire .NET programmers, the best success we have had, result wise, is to hire !.NET programmers (e.g. the hiring process started being about abstract problems that could be solved with anything, etc) and let them loose with C#/etc. If we limited ourselves to the .NET skillset we got tonnes of applications, almost all of which were terrible.