Hacker News Reader

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.

View on HN

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.

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.

This is so true, the constant churn of frameworks for desktop apps has left me very skeptical of anything they offer.

Reply on news.ycombinator.com