Re:How Microsoft Lost the API War [2004]
by protomyth on Wednesday December 22, 2010 @09:11PM
(#2033282)
I think your point #2 is the critical one and it seems to be at odds with the premise of the article. Microsoft is now trying to keep it's old API intact on a platform (tablet) that it is not suited for. If Microsoft had really got behind a new API (even if it was a OS X => iOS :: Windows 7 => ??? situation), it would have a better chance as opposed to the drumming it has taken.
Re:How Microsoft Lost the API War [2004]
by dkarl on Wednesday December 22, 2010 @10:48PM
(#2033443)
I don't think it's at odds with the article. Microsoft irritated developers by pushing wave after wave of new desktop APIs on them for no good reason, and now that they have a compelling justification (new form factors) to release a redesigned API they can't afford to risk it because they've worn out the patience of developers.
Re:How Microsoft Lost the API War [2004]
by yakisoft on Thursday December 23, 2010 @03:16AM
(#2033887)
This is so true, the constant churn of frameworks for desktop apps has left me very skeptical of anything they offer.
Re:How Microsoft Lost the API War [2004]
by protomyth on Wednesday December 22, 2010 @10:56PM
(#2033462)
I see your point. I was going from the premise of keeping the current API vs new platform needs angle. Your right that the "new cool way" wears thin. It almost seems that if you are a Microsoft developer you shouldn't use any new tech unless the Office division starts using it.
1. Advances in web application technology like HTML5, Sproutcore, and so forth.
2. New "platforms" like smart phones, tablets, and ebook readers where Microsoft doesn't dominate.
3. Getting back to point #1, the possibility that nobody uses desktop applications, where by "nobody," I mean "fewer than 10,000,000 people," to borrow Joel's phrase.