I think you should revise your overreaching article to say 10 reasons why developing for win8 METRO might be painful. If half of the things you've said were true, none of the programs I'm currently using on my win8 slate, a PHYSICAL device and not a VM, would run but if you apply your statement to Metro specifically then yes, you're points are somewhat accurate but as someone who has written several Metro apps for Win8, I have to say that I didn't find the points you listed all that bad. Metro still allows .net so if you have a recently developed desktop application that you'd like to create a metro front end for, that code will migrate painlessly and you'll just have to recreate the gui...if you developed a web services based app, you'll be able to grab that data easily and use it in your application. This article raises some inaccurate points and to say Metro has been universally panned in also inaccurate as is your "virtual machine" requirement myth as evidenced by the fact that my reply was composed on my Samsung Series 7 Slate running Windows 8. I have serious doubts about the quality of this highly misleading article.