For me it came down to what I could build most rapidly given my skillset. I had experience in Java and C#/.NET and my partner (my husband, not my co-founder) could mostly only help in C#/.NET. So it really was a question of getting something built in 3 months versus 6 (or maybe not at all if I got discouraged and it took too long to market). The licensing fees are the things that weigh on my mind, but if my business is successful, I will be able to pay them or even re-write the application using the profits.
I know better than to expect to converse about our MS technology with the HN crowd, though.
It may well be that YC-funded startups consistently differ from the average startup. But that doesn't mean that such differences are due to fashion. The kind of people we fund are more consistent in knowing what they're doing than in being young. So if as a group they differ from the norm on technical matters, the more likely hypothesis is that the norm is lagging.
I'm comfortable assuming that the YC startups are above the average, but that doesn't mean they aren't also affected by the demographic that would most benefit and be able to participate in the YC program. In no way am I implying that YC would select someone younger for admission over someone more qualified - just that the nature of the program self-selects.
In my case, I'm still young but having a toddler puts me in a similar situation to a typical older entrepreneur. It would be incredibly difficult for me to take an X month block away from my family or to uproot my family. And a $10K investment doesn't mean to me what it does to a college grad, because I can make that in a couple of bonuses or consulting gigs. The thing I miss most in a program like YC is the mentorship, but for me it's not worth the aforementioned hardship.
It's not that I'm not interested in new technologies, I do tinker, but it's just a matter of priorities. Given that, you're probably right that the "norm" would be lagging in terms of using the newest and coolest technology. I don't think that equates to generally worse companies, just less fashionable, to tie back to the original point.
I'm not sure why. People talk about Clojure and Haskell and I'd bet good money that those are even less common for startups — heck, probably fewer people here can even read them. I don't personally like the Microsoft stack overall, but I do think some of the stuff they make is pretty compelling and it would be interesting to hear how it's used outside of a BigCo.
That could just be me, though.
Be careful here though ...
> I know better than to expect to converse about our MS technology with the HN crowd, though.
Lots of positive posts, even in this thread!
If you run a small group of machines and you know what you are doing, Windows could be just fine for you. The worst that can happen is you succeed and need to migrate your software to another platform.
edit: actually the worst that could happen is that you hit a technical problem the closed nature of Windows prevents you from solving and you have to port before you become profitable.
So it might influence us a bit, but we never know till we know other things that influence us a lot more.
.Net might just attract personality types that are more risk averse, aka programmers more interested in a steady paycheck than the ups/downs/stress of the startup life.
Having said this, I find the Microsoft platform dead simple, the tools best of breed, and the new MVC framework to have opened up the platform considerably.
Yeah, the thing people also don't realize on this topic is you can use MS SQL Express - which is free - to avoid paying/licensing issues.
The limits are almost entirely around ui, ease of use type features, not performance or scalability. Aka, you don't get the fancy VisualStudio-esq UI so you can't do diagramming, or things that you want generally when you are developing. But you still get a barebones management tool that's better than most of the mySql variants I've played with.
For use on a webserver, yeah it's a solid option esp if you are already having to use MS SQL because of other business requirements by your client/company.