Slashdot Mirror
Microsoft Ignores Usability With All-Caps Menu in Visual Studio
mikejuk writes "The recent release of Visual Studio 2012 contained a UI element that few believed could make it into the final version — ALL-CAPS menus. After lots of user criticism and disbelief, Microsoft has moved swiftly to do something about it — by tweaking the typography. '... we explored designs with and without uppercase styling. In the end we determined it to be a very effective way of providing structure and emphasis to the top menu area in Visual Studio 2012.' This must be a new meaning of the word 'structure,' because putting the menu items into all-caps means that they are all the same height. When each menu items starts with a cap then there is structure because you can see the change in height, marking the start of the next menu item. The idea that putting a menu into all caps adds structure is something that is very difficult to see. If you wanted to put structure into a menu, well how about color? Oh wait, I forgot the design department dumped color in favour of the 'everything-is-grey UI.' Developers are the people who invented CamelCase to make sure that the structure of run together words would stand out better — and now we are asked to believe that making a menu all-caps adds structure. I don't think so."
You see, MS is so hip, so ahead of the curve, that they know already that COBOL is about to come back into style in the developer world. Soon everything will be in all caps, mainframes will be all the rage, and GUI's will be passe. Apple will be behind the times with their over-designed software, and MS will be out in front with their all caps, command-line interface only version of Windows 9--renamed "DOS 9 FOR TERMINALS."
GOOD JOB, MICROSOFT!
What political party do you join when you don't like Bible-thumpers *or* hippies?
Iâ(TM)m horrified. Absolutely shocked. I tell you, this is the final nail in Microsoft and Visual Studioâ(TM)s coffin. Oh, and âoeMy eyes, it burns! The goggles do nothing!â
If you want news from today, you have to come back tomorrow.
Previously barring a lot of eye candy that could be turned off , MS did generally get their UI about right. Now with spillover effect from Win8 they seem to have completely lost the plot and this is simply an example of them reloading the gun once more to take aim at whatever is left of their feet.
This is the company that gave us the ribbon. Otherwise known as the chaos strip, since it seems to randomly rearrange itself to ensure that function you're looking for is never less than half a dozen clicks away. It's a bit like a supermarket, where they deliberately move stuff around in order to make shoppers seek out the things they usually buy in the hope they might chance across - and end up buying - things they haven't seen before.
As I understand it road signs (or many of them) in the UK used to be in caps but studies showed that mixed-case was much easier to read (which mattered more as cars got faster) since we're looking for familiar patterns.
Looks like Microsoft will need to re-learn this lesson...
"Ignorance more frequently begets confidence than does knowledge"
- Charles Darwin
Only someone who has a website with such bad usability can truly see horrible usability in others' work.
"Developers are the people who invented CamelCase"
I think chemists has developers beat by a century or two. Now please pass the NaCl.
This is such a laughably bad decision, I can't see it making its way into the final product. I even tried to type this post in all-caps, but /. reminded me that it was wrong. When it comes to something people have known and taken for granted for years, it seems very odd that Microsoft would go backwards and decide on this. Exactly where is the leadership for this project?
How come they haven't created a 'ribbon menu' for Visual Studio? Perhaps this is tacit admission that the Ribbon Menu sucks and is inefficient.
love is just extroverted narcissism
Mod up! This is absurdly true. Office got a new interface that it didn't need that seems no better (just different) from its last interface. Now the same thing is being done for windows. Why not just add a "Tablet/Phone Shell Mode" and be done with it? I'd me much more interested in a faster file system, fast, usable search (still waiting, Microsoft), fewer blue screens, Azure presented in such a way that anyone can host any windows application, legacy or not (Once again, they miss the obvious).
In the last 20 years, Microsoft has been busy solving problems nobody I know seems to have had. I guess they're just going to continue the tradition.
Please do not read this sig. Thank you.
Next up: They are going to replace Clippy with a flying chair.
Have gnu, will travel.
If you go to the source, http://blogs.msdn.com/b/visualstudio/archive/2012/06/05/a-design-with-all-caps.aspx, they note that there will be an option to disable it.
There's also a blog post that shows the registry key that works today to disable it.
Even better: Circular backronyms!
FILE -- FILE Input Listing Element
EDIT -- EDIT Document Interface Tool
VIEW -- VIEW Interface Element Window
etc.
We know where leadership by an anti-intellectual "strongman" who scapegoats minorities and likes boisterous rallies goes
> In the last 20 years, Microsoft has been busy solving
> problems nobody I know seems to have had.
That's not entirely fair. In the last 10 years, Microsoft has been very busy solving problems they themselves created in the previous 10 years.
That being said, Windows 8 is looking like they're ready to start another 10 year cycle of creating new problems.
Log in or piss off.
Define "Mainframe". From what I can see, "mainframe" is a term for very expensive ultra performance hardware.
Nah, it's more than that. It's about redundancy, high I/O relative to compute power, optimization for throughput rather than latency, and high availability.
Speaking of Windows 8, maybe they should just get rid of the menus altogether! Instead, you should have to point to an invisible, 2-pixel-wide area of the lower-left corner of the window to see a full-screen page of active tiles representing what Visual Studio can do with your project. Each tile should move, spin, twirl, or change color in some way to keep your eyes busy while you look for the item you want. And since it's hard to do multi-touch on a desktop, it should require two mice to operate!
UK road signs were changed to their current style after testing in 1958, there's a nice summary on the BBC. This new mixed upper and lower case style became legally required on 01 January 1965.
So yes indeed, typographical designers understood this in the UK quite a while before it was a widely discussed computer interface debate..
The only people worse then programmers at design are designers who have become totally disconnected from their audience. Like say, the ones doing this. The audience is programmers. They probably know what they want, and the areas Visual Studio needs improvement in were not caps locked menus and monochrome grey icons.
Also, all caps is harder to read: http://www.bbc.co.uk/news/magazine-15990443 . We've known this for decades. It was determined before Microsoft existed. They were with the program for a while, then this "Metro" disease showed up in Redmond and now everybody is screwing everything up and calling it Metro (though when they call VS Metro I really don't know what they're talking about, unless Metro is code for ugly).
And while we're on it, what does Apple have to do with this? You're saying they should bash Apple for something that Microsoft just changed their UI to do. Since Microsoft wasn't doing it and now is, why wouldn't we go after them for screwing it up when they had it right before?
-- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates