The article was interesting
...and is often spot-on:
my personal view is that desktop applications need to be rewritten or modified for the touch environment
That. Non-touch apps don't work right for touch input. And touch apps suck with mouse/keyboard interfaces. And in lots of cases, very large parts of the code would have to be replaced (as much as 90%). This is why Metro doesn't make any sense, except on tablets. But again, it's not like we're given the choice of having the right kind of UI, everything is now a smartphone according to MS.
What Windows 8 needs is to go back to its roots and to become Windows again.
This. We'll wait it out for a while, but if Windows doesn't become Windows again then it just becomes a useless and irrelevant OS that I won't use on any device.
As for the comments:
windows 8 is trying to turn my killer machine into a mobile phone. this sucks! get the cell outta my pc!!!!!
+1 to that.
If this change takes hold, you should forget desktop computing for ever. Rich applications with rich output and capable interfaces using the desktop in an intelligent manner would be history for good.
Exactly. Almost all the software that makes using Windows worth it just doesn't and can't work with the Metro UI. It's just not suited to desktop computing. If MS pushes that aside then they greatly reduce the usefulness and relevance of Windows i.e. they're killing it.
On that page, the comment that appears just below this last comment sounds like an even more serious indictment of Metro, but I'm not a developer so I lack the expertise to assess it.
That's the same kind of stuff I've been saying all along, just with specific points and examples. It's far too limited, the apps are sandboxed (your access to anything is very limited), and yes, it's not exactly a mature development platform and things like the controls suck (and of course, everything is maximized now). That's why we don't plan on porting any of our software to Metro. Having to rewrite *huge* amounts of code at great expense, especially when most people believe Metro will be a complete flop, and that MS lately is quicker at killing or replacing their new developer tools? MFC (tech from 1992) still works today. But Winforms? Well, that's been replaced by WPF. Oh, wait, that's being replaced by WinRT. Silverlight? Forget that too, it's HTML5 now, and maybe WinRT. "Classic" ASP was replaced by ASP.NET, and that's being replaced by ASP.NET MVC. They seem to do this for all their recent stuff. They push hard for something then they just kill it off, and you end up having to re-learn how it works and by the time you're there they replace it again. So eventually you stop caring about the flavor-of-the-week stuff.
So yeah. Why incur the expense of porting existing Win32 apps that work great and already costed quite a lot to develop, having to re-think how every part of interface should work using touch, re-training all programmers for WinRT, writing all the new code (maintaining 2 separate code bases) and doing a lot of restructuring work so you can reuse parts of the old code. That's assuming that what you need to do can even be done in that sandboxed environment (in our case it can't be for most of our apps). Just so we can have a smartphone-like app which will only run on ~1% of our users' computers (those with Win8), only to see them use it with their mouse anyway? Most likely they'd hate it and just run the good old version on the desktop instead. It's just *so* not happening. You can imagine that lots of other companies, if not nearly all of them (except those who make smartphone apps), will do the same.