Linked by Thom Holwerda on Mon 9th Jul 2012 02:01 UTC
Microsoft "Analyzing one of American corporate history's greatest mysteries - the lost decade of Microsoft - two-time George Polk Award winner (and V.F.'s newest contributing editor) Kurt Eichenwald traces the 'astonishingly foolish management decisions' at the company that 'could serve as a business-school case study on the pitfalls of success'."
Permalink for comment 526236
To read all comments associated with this story, please click here.
RE[5]: It is a shame
by TemporalBeing on Tue 10th Jul 2012 17:47 UTC in reply to "RE[4]: It is a shame"
TemporalBeing
Member since:
2007-08-22

"WPF didn't take off
"

True. It kind of went the way of Silverlight which was built on WPF. I'm not sure that it was solely dependent on .NET functionality, but needless to day it probably didn't get the attention it deserved. That said, I haven't used it, and have moved on to non-Microsoft stuff...Linux and Qt.

"(I believe that Visual Studio itself is a WPF app that's in pretty wide use, as well as accompanying apps like Blend)
"

I could believe that VS 2010 and later are WPF apps. But from what I hear they're mighty slow.

"You act like putting together a new app API framework and getting it widely adopted is easy. It ain't.


WPF was geared as an alternative to the old frameworks hence the comparison between WPF and those other frameworks is asinine at best. Amazing how Apple has been pushing and pushing Cocoa and how the hard work is paying off where as Microsoft has done nothing and as a result you see nothing happen by way of a modern API to replace win32 on which traditional desktop applications can be written.
"

Win32 has been around since roughly 1993-1994 when they releases Win 3.1 Win32s - a 32-bit port of Win3.1 that didn't get much attention; Win32 API wasn't widely used until Win95/NT4.

Then came MFC/ATL to build on top to make applications easier - but not really.

Then came .NET which was suppose to replace MFC/ATL, but that didn't work - too many people wanted the performance of a native program.

Then they added WPF and a number of other layers on top of .NET, but that didn't pull people in.

So now they're scrapping .NET and going to a new API - WinRT. If you want to write native apps for Win8 that runs on all Win8 platforms you have to write it for WinRT - no Win32 code except for the small bits that made it into WinRT, so MFC/ATL is out. .NET can be used but you'll probably have to refactor it to ensure it only uses the part of .NET that runs on WinRT - e.g. no DLL/COM/DCOM/ActiveX plug-ins that make use of Win32, etc.

We'll see how that one goes. Not likely any better.

Reply Parent Score: 2