With only minor editing you get this!
for me personally, the trend towards making the Widows 8 desktop "easier to use" has had me running away from the platform as a Desktop.... the problem is if you are going to make a GUI(and as a result make command line configuration more difficult), that GUI better damn well work. And it doesn't. So I find myself constantly trying to figure out what they changed from the previous version(that isn't working in the current version), and of course constantly changing where things are located etc. doesn't help.
If you are going to change the desktop experience in order to make it "easier to use", you damn well better get it right, or else not only do you fail to capture a new audience, you end up alienating the current user base. That seems to be what Metro has done.
For me personally I develop on a mac, and run my test and prod on Widows 8(I've tried Windows server, and ironically it seems to suffer the same problems as a server as Widows 8 does as a Desktop, they tried to make it "easier to use", but didn't get the abstraction right and the result is a mess).
I was recently put in the unfortunate position of having to develop a PHP app, and I tried doing everything on Windows 8 with Metro, and.... that was just plain frustrating. The installer tried to be "easy to use", but often failed, the system got stuck in reboot but I couldn't figure out what service was failing because I couldn't get it to not show that stupid startup animation and instead show me the boot log etc. Eventually I got the machine booted and then just ssh into it from my Mac, much less frustrating.
Bottom line: don't make Widows 8 "easier to use" by breaking a bunch of shit.