Thinking about this amazing news from Scott Guthrie today. It’s been a long and winding road for .NET. Many of us have moved on completely, most of us now are polyglots. I’m excited for the prospect of solving problems with my familiar .net class libraries in new and different ways.
When I think of my beloved .NET, I often ponder this question – Would I launch a web-oriented startup based on .NET today?
Of course there’s many many factors involved in the answer to this, admittedly unfair question. Web startups are only one very small class of new projects that are started every second, and there are many times when the decision to use .NET is a no-brainer. But to me, this is one of the most interesting questions to ask about .NET today, and one I recently had to ask myself.
So why .NET in the stack? There were many reasons, but to name a few, I’d say low risk because of our existing knowledge of the platform was a big one, and free Azure hosting from BizSpark was another. I also LOVE Nancy.. But I have a nagging feeling that a stack with node would have been an good choice, and the fact that I could easily run on my mac, and just about anywhere else is a big, huge win.
And I know, it’s possible to do .net development in Mono on Mac and elsewhere – Nancy runs on Mono and Mono’s compatibility statement – “Everything in .NET 4.5 except WPF, WWF, and with limited WCF and limited ASP.NET 4.5 async stack.” is a huge mouthful of cross-platformy goodness. But I’ve never come across .net code in the wild that runs cross platform without special care taken to ensure that goal. Other stacks just work de facto cross-platform.
So, perhaps this news gets us one step closer to being on par with other stacks, where I don’t have to boot in to Parallels just to work, and I can kiss my old Windows installs goodbye forever.