Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

BLOG: Why Microsoft .Net failed

Andrew C. Oliver | Aug. 30, 2013
Microsoft tried, but it couldn't win the hearts and minds of developers who weren't already indoctrinated -- and it alienated others along the way

Off to legacy land
Now it's too late for .Net. As we move from IaaS to PaaS and SaaS, folks are simply unlikely to care about operating systems. If you don't care about operating systems, why not code as if you don't care about operating systems and code for the cloud? We've seen recently that Azure isn't lighting the world on fire. Why would we expect that to change?

Even if you believe that most companies will continue to build their own data centers to care and feed, while ignoring the cloud, the desktop monopoly is also dying. Consumers are net information consumers. If you don't work in tech, publishing, or entertainment, then you probably take in more media than you produce. With the iPad, Android, and such, writing .Net isn't a viable business option. Miguel de Icaza can create all the companies that begin with "x" that he likes, but people will continue to care less about Mono or be scared off by its patent ambiguity.

As users move from the desktop to the tablet and set top to view their pornography, cat pictures, and Netflix movies, the economics that caused folks to "target" Windows are abating. This results in a downward spiral for 'Softies hoping that writing to .Net is enough.

I could theorize about how Microsoft could extend .Net — but why should it? .Net was about extending Windows. In a cloudy BYOD, tablet-oriented, Internet-standards-driven world, there may no longer be room for Microsoft, let alone .Net. The .Net initiative failed, and if you were part of it, I hope you hedged your bets by learning a few other tricks along the way.



Previous Page  1  2 

Sign up for Computerworld eNewsletters.