Seems to me the whole win8 ui fiasco is something Microsoft does a lot.. Have a good idea, go way overboard with it, and end up having to pull back and find a more refined middle ground in a future release. If only they'd find a way to internalize this process instead of making us all into a usability study...
Fortunately they didn't manage to really screw up Visual Studio in any significant way, and the dark interface skin looks great.
It's nerve wracking when they announce a new release :-).
I'm pretty handy with VS but given its sheer size I don't need any extra impediments. RANDOM ALL CAPS MAKES THIS SENTENCE DISTRACTING. I HAVE TO LOOK AT MENUS A LOT.
Contrast with the Outlook ribbon's "Home" tab which puts 95% of what I need to do right there always visible by default. I don't have to hunt around at the top of my SCREEN WHICH IS IN DISTRACTING ALL CAPS nearly as much.
The first thing I do after installing VS2012/VS2013 is to edit the registry to return the correct casing to the top level menus.
The icon scheme for SSDT in VS2012 was the worst. No colour, just symbols. Want to add a primary key? Look for the key icon. Sounds good in practice but there's lots of monochromatic key symbols overlaid onto other monochromatic symbols (primary key on table, symmetric key, foreign key). At least with the colour I can more easily distinguish the primary key is gold and the blue square it's in front of is a table.
FWIW I don't think I was significantly less productive in VS2012 than 2010 but it's a moot point now since VS2013 put colour back in.
[1] Best I could do: http://i.msdn.microsoft.com/dynimg/IC653694.png
[2] http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communit...
The fact that the betas had wildly different casing seems to point to some designers holding the product to their whims, instead of based on any sort of intelligent thought.