Visual Studio '11' Announced
11–20 of 196 posts
Re: Visual Studio '11' Announced
#12VS2010 is just damn slow and falls over on me at least 2-3 times a day which is not acceptable. When you pay for 25 VS2010 premium licenses with MSDN on top of your gold partner allowance, you expect it to work.
Re: Visual Studio '11' Announced
#13Re: Visual Studio '11' Announced
#14Re: Visual Studio '11' Announced
#15Maybe it's just me but I like the "Strong use of color" better. I find it hard to quickly find the tool button I want when they're all monochrome. I'm sure I'd get used to it, but I can't really say the colors in the GUI are my primary distraction when I'm coding...
In VS 11 we have transitioned to glyph style iconography throughout the product. While we understand that opinions on this new style of iconography may vary, an icon recognition study conducted with 76 participants, 40 existing and 36 new VS users, showed no negative effect in icon recognition rates for either group due to the glyph style transition. In the case of the new VS users they were able to successfully identify the new VS 11 icons faster than the VS 2010 icons (i.e., given a command, users were faster at pointing to the icon representing that command). In this and subsequent studies more developers have expressed a preference for the glyph style icons over the former style, especially after having spent time getting used to the new glyph style icons.
Re: Visual Studio '11' Announced
#16Re: Visual Studio '11' Announced
#17It's interesting that Microsoft chose to adopt monochrome icons after Mac OS X / iTunes adopted monochrome icons. I'd be curious if Apple's design was a major influence on Microsoft's designers, or if the idea for monochrome icons came primarily from independent research/user testing.
Apple might still me a influence, but I don’t think it’s minor.
Re: Visual Studio '11' Announced
#18Re: Visual Studio '11' Announced
#19Do new tabs still open to the left of the current tab? Drives me absolutely insane.
Check "Insert documents to the right of existing tabs".
Re: Visual Studio '11' Announced
#20So both MS and Apple teams may focus on what is "right" and avoid feature bloat in UI, avoid quick and dirty solutions etc. Yes, they must include some features quickly and efficiently to allow support for some new APIs in the new products. But the overall design and fit and finish is free to define however they want. They can spend time making it right and redoing it how they please. They have resources and expertise for that and they don't need be in a stressing "competition" mood.
I'm really disappointed by what Microsoft did with Visual Studio. They have great technology - great language, great compiler support and integration with editors. But the way it is all presented and organized is all boring mess of panels and tons of icons. They even understand all the icons are heavy for eyes, but instead of rethinking the design, they simply ask "40 existing and 36 new VS users" how do they like monochrome versions.
Apple's Xcode 3 was also a messy window/panel cluttered tool like many others. Many still considered it lighter than any other complex IDE, but it was fairly cluttered on its own. Next version, Xcode 4 was not designed by "asking developers". Developers want a pink pony and all the features in one click. Xcode 4 was designed. They made priorities and straightened UI so much it is now Plain Straight. One window, three panes, 7 buttons on toolbar. Just by learning a single screenshot with both sidebars opened, you already know how to navigate 80% of the time. It is crucial. You don't have to read huge manual to learn more and more useful things. They all are discoverable over time. Most important things are more visible, others are discovered over time.
Apple and Microsoft are rarely in position to throw old stuff out and replace it with brand new in their actual products that make money. Windows, Mac, iOS all have its legacy which must be dealt with. But UI for developer tools are different and Microsoft has no excuse not to make it interesting. Unless, of course, they don't want to maintain their own engineering culture.