Slashdot Mirror


Microsoft Vista User Interface Guidelines Published

SEMW writes "Microsoft has published the preliminary Official User Interface Guidelines for Windows Vista. Highlights include Top 12 Rules for the Windows Vista User Experience — and the use of screenshots from Windows XP as examples of what not to do. The full guidelines are as yet incomplete, but what is there makes for interesting reading."

30 of 269 comments (clear)

  1. Breaking your own rules by Allicorn · · Score: 3, Insightful

    So I guess we can take these rules as a fairly good indicator of what interface features the next version of Office will NOT follow. It's been my impression that whatever interface guidelines MS publish, they always seem to very rapidly diverge from them in the own applications.

    --
    OMG!!! Ponies!!!
  2. This made me laugh. by radicalnerd · · Score: 5, Funny

    Be polite, supportive, and encouraging. The user should never feel condescended to, blamed, or intimidated.

    1. Re:This made me laugh. by Bones3D_mac · · Score: 4, Funny

      The user should never feel condescended to, blamed, or intimidated.

      You mean Vista is doing away with DRM?!

      About damned time!

      --


      8==8 Bones 8==8
    2. Re:This made me laugh. by BrynM · · Score: 4, Funny
      I personally got a chuckle out of the repetitive use of judiciously... why thank you Microsoft, I thought it would've been better to use certain functionallity foolishly!
      Rule 12 1/2 should have been: Use judiciously judiciously.
      --
      US Democracy:The best person for the job (among These pre-selected choices...)
    3. Re:This made me laugh. by kfg · · Score: 5, Funny

      The idea that their "Playskool" interface is an attempt to not be condescending is just too condescending to bear.

      KFG

    4. Re:This made me laugh. by PsychoSlashDot · · Score: 3, Interesting

      That's funny and all, but overall there's quite a bit of these guidelines to disagree with...

      While not everyone is going to agree with all of my critique, I suspect we're going to be fairly united overall. I'd like to question why the Start Button is now the "circular shape with the four-color windowpane kind of shape in it that was in the bottom left when you got your computer but might have been moved to any of the other three corners". I'd like to know why in MMC windows and Explorer windows the plus-sign/minus-sign symbols to expand/collapse nodes is now the "hollow arrow pointing to the right" and the "solid arrow pointing fourty-five degrees downwards from the right". I'd like to know why in a world where Citrix and Terminal Services are increasingly predominantly used, we get things like swirling colour effects moving through progress bars to tell you the processor hasn't halted, just to slow down the interface. These are my initial impressions of Vista, from the perspective of an IT professional who has hundreds of users he needs to train, support, and troubleshoot.

      Don't provide unnecessary details. A well-labeled progress bar provides sufficient information, so provide additional progress information only if users can do something with it.
      And there, in a nutshell is MS' philosophy. Assume things are going to go right. I call bullshit. If you provide scads of additional information, such as what file is being copied, or how many [giga/mega/kilo]bytes remain, or what registry key is being written, or what dll is being registered, normal users will ignore it. Those who know things will be able to help when things go wrong.

      Present choices and settings in terms of user goals, not technology.
      I understand the goal of making users feel squishy and loved, but this is a support headache in the making. Now instead of helpdesk/IT people being able to train that users should look for "duplexing" and turn it on, they have to look for whatever variant of "print on both sides of the paper" or "flip paper and print on other side" each manufacturer chooses to use for their drivers/programs. Technology-based description of options tend to be predictable because a precise, definitive word or phrase is applied to the option.

      While the minimum Windows Vista screen resolution remains at 800 x 600 pixels, resizable window layouts should be optimized for 1024 x 768 pixels.
      And there you have it. Shouldn't this read "window layouts should always be scalable down to a minimum of 800x600 and should be resizable by users"? Sure, an OK/Cancel box could arguably not be resizable... but then too it's harmless if it is.

      Never use confirmations as a form of user education.
      Are you sure you really want to reformat your hard drive? You should pick 'no' unless you are absolutely certain that you want to erase all of your data on [drive letter]. Picking 'yes' will delete all information without hope of recovery. Proceed with extreme caution.

      Make sure the properties are necessary. Don't clutter your pages with unnecessary properties just to avoid making hard design decisions.
      Because hard design decisions don't generally correspond to the simple fact that some people prefer Coke and some Pepsi. Right. Give the user options. Any time you're not sure which design or option is better, let them make the choice. Except the Taskbar which should always be along the bottom, period. Whoever let users move the singlemost fundamental Windows95+ UI element should be shot.

      Don't accompany error messages with sound effects. Doing so is jarring and unnecessary.
      Thanks. I'll keep the person who made this choice in mind next time I've got a massive file copy going and I elect to read a book or something and it stops 10% in because the destination runs out of room, or I lack perms to a source file or something and it's just sitting there waiting for me to click 'ignore' or something. If I want it to b

      --
      "Oh no... he found the .sig setting."
    5. Re:This made me laugh. by ChronosWS · · Score: 3, Insightful
      For brevity I am only quoting the rules you stated, not your responses to them.

      Don't provide unnecessary details. A well-labeled progress bar provides sufficient information, so provide additional progress information only if users can do something with it.

      Error log files should be provided for these cases. The single line of rapidly flashing text will either be ignored by most users or be cause for alarm (because a lot of very important/cryptic stuff is happening rapidly.) IT pros are already used to log files. I have, in fact, noticed more and more applications are providing logs of what occurred during lengthy operations and these have the capacity to provide much more useful information than a status bar. MS is right on this one, what they forgot to say was where such additional progress information should go.

      Present choices and settings in terms of user goals, not technology.

      I agree that from a helpdesk perspective, this is going to cause issues, but from a 'can the user get themselves through the first hour without reaching for a book of computer terminology' perspective it's probably more of a win. I am not sure which choice is better - it feels to me like either way you go you get problems. But given the general design theme MS is trying to achieve (not alienating the user with cryptic text) this rule is at least consistent.

      While the minimum Windows Vista screen resolution remains at 800 x 600 pixels, resizable window layouts should be optimized for 1024 x 768 pixels.

      "Optimized for" is not equal to "design only for." This rule is treated more completely in the detailed rules for Vista UI design. 800x600 is really, REALLY low resolution these days - you'd be hard pressed to find a Vista-capable computer that couldn't display 1280x1024 and be sold with a monitor to match. I suspect this particular element was influenced in part by the possibility that Media Center PCs would be hooked up to TVs or some other such case. I'd imagine the chances of a general application actually being constrained to this requirement is very small.

      Don't accompany error messages with sound effects. Doing so is jarring and unnecessary.

      This should probably read "Only use sound effects for critical error messages, not for less important notifications and warnings which do not require immediate user response." On the other hand, MS may have decided that if the user really cared about the operation, they'd be sitting at the machine actively tending the UI, and making undesired sounds would interrupt their other activities. I personally find the flashing window notification method in the task bar to be suitable when I am at the machine, even if I am reading a book. Again, if the immediate completion of the operation is important to me, I'll watch it. In the corporate IT environment perhaps this requirement is different.

      Don't use the warning icon for routine questions. Doing so is counter to the encouraging tone of Windows Vista and makes using your program feel like a hazardous activity. Assume users understand the consequences of cancelling a task before it is finished.

      MS is clearly trying to make computers "feel" less opaque than before, even if to the tech-oriented person that feel actually obscures the underlying operations. There is also an underlying meaning in this rule that the application developer should design their software such that cancelled operations have user-predictable outcomes. For instance, cancelling an install should NOT leave the application half-installed - it should revert any changes it has made. Cancelling the copying of a file shouldn't leave half of a file copied. On the other hand, users are expected to know that cancelling a format will not revert their drive to the previous state - this is why such irreversib

  3. The Rules: by iluvcapra · · Score: 4, Informative
    (emphasized elaborations mine)
    1. Use the Aero Theme and System Font (Segoe UI)
    2. Use common controls and common dialogs
    3. Use the standard window frame, use glass (transparency) judiciously
    4. Use icons and graphics consistent with the Windows Vista style and quality
    5. Use task dialogs for new or frequently used dialog boxes and error messages
    6. Use Aero Wizards
    7. Use Explorer-hosted, navigation-based user interfaces, provide a Back button
    8. Use the standard Windows Search (have a little iTunes style search box in your window's corner when appropriate)
    9. Use the Windows Vista tone in all UI text (use a professional writing style in you informative text)
    10. Clean up the user interface
    11. Use notifications judiciously
    12. Reserve development time for "fit and finish"!
    --
    Don't blame me, I voted for Baltar.
    1. Re:The Rules: by iluvcapra · · Score: 5, Interesting

      My thoughts:

      Use the Aero Theme and System Font (Segoe UI)

      Good, but obvious.

      Use common controls and common dialogs

      ibid

      Use the standard window frame, use glass (transparency) judiciously

      Good good. If MS keeps making such a big deal about transparent UI tho, silly developers are gonna use it everywhere.

      Use icons and graphics consistent with the Windows Vista style and quality

      Good. If you follow this suggestion closely enough, maybe we can convince the users at home that your application comes from Microsoft, too.

      Use task dialogs for new or frequently used dialog boxes and error messages

      Good.

      Use Aero Wizards

      If you're replacing a 97 Wizard, you should use an Aero wizard. If you're writing a new app, please do not use a wizard. They're obnoxious, and send the message: "We didn't know how to organize your options in any sort of logical way, so here's a powerpoint that lets you fill in the blanks, masquearding as a UI."

      Use Explorer-hosted, navigation-based user interfaces, provide a Back button

      In short: Consider making programs that aren't web browsers behave like web browsers, since people use those alot. This is interesting, but at some point you have to explain the difference between the "Back" button and the "Undo" button, and you might just end up making your program into a wizard

      Use the standard Windows Search (have a little iTunes style search box in your window's corner when appropriate)

      A total dig on my part, and I apologize, but that's basically what they're saying. Apple makes the same recommendation, and give a very slick API for making it work. So good suggestion.

      Use the Windows Vista tone in all UI text (use a professional writing style in you informative text)

      From Microsofts mouth to ghod's ears.

      Clean up the user interface

      On their page they list all kinds of things you can do to make your program more ergonomic, but they put it at the end of the list, and phrase it in such a way as to suggest that it should be something you do at the end of development, as opposed to at the beginning, when you're designing your windows on a whiteboard. "Organize your command (sic) into a simple, predictable, and easy to find presentation" is something you do before you start writing code- it is not something you do while "cleaning up".

      Use notifications judiciously

      Or not at all. The list makes no suggestion about keeping your damn icons out of the systray.

      Reserve development time for "fit and finish"!

      Fit and Finish has quickly become my least favorite phrase. Sorry, just snarky, I agree with this point. But I would say "Hire a designer" as opposed to "reserve development time", mainly because it will allow collaboration with someone who always has their eyes on the UI and can give the developers continual feedback on how their code is totally rocking for the user ... experience, or totally deviating from reality.

      --
      Don't blame me, I voted for Baltar.
    2. Re:The Rules: by adpsimpson · · Score: 3, Funny
      Use icons and graphics consistent with the Windows Vista style and quality
      From the article:
      Use .PNG compression for large icons to keep the .exe size under control.

      Did hell just freeze over? Is Windows Media Player Vista going to recommend .OGG for media files?

      --
      Is crushing a suspect's child's testicles illegal?
      John Yoo: "No, [if] the President thinks he needs to do that."
    3. Re:The Rules: by kestasjk · · Score: 3, Insightful

      If you're replacing a 97 Wizard, you should use an Aero wizard. If you're writing a new app, please do not use a wizard. They're obnoxious, and send the message: "We didn't know how to organize your options in any sort of logical way, so here's a powerpoint that lets you fill in the blanks, masquearding as a UI."

      Wizards are like many UI constructs; they are often abused but they can be very useful. Access data import Wizards, installation Wizards, Visual Studio database creation Wizards, etc.
      Whenever you need the user to enter a series of logically grouped options before you can begin to do what the user wants a Wizard is the way to go. It's either going to be a Wizard, or a large unwieldy dialog box.


      I think Microsoft's suggestions here are all good, but of course if you're the sort of developer that has to read them you're probably the sort of developer which doesn't care about the UI and won't implement them anyway. Which is a shame, because the UI can go a long way to make your program better.

      --
      // MD_Update(&m,buf,j);
  4. Wow... by ResidntGeek · · Score: 4, Funny

    That's a really bitching Notepad icon. They've clearly been hard at work.

    --
    ResidntGeek
  5. Guideline #1... by TheDarkener · · Score: 3, Funny

    "Keep the user guessing."

    --
    It is pitch black. You are likely to be eaten by a grue.
  6. user Rule #1 by Quiet_Desperation · · Score: 4, Funny

    Do not install Vista. :)

  7. Restart now? by DuranDuran · · Score: 5, Funny

    > examples of what not to do

    Updates complete. Restart now?
    What about now?
    Now?
    Now?
    Now?
    Just wanted to know if I should restart now?
    What about now?
    Are you ready to restart?
    Shall I restart now?
    Should I not restart later?
    I think I should restart now.
    Wouldn't it be good if I restarted now?
    Who's up for a restart??

    --
    "You can justify anything by putting it in quotes, adding a famous name and making it a sig" - Albert Einstein
    1. Re:Restart now? by PygmySurfer · · Score: 3, Informative

      They actually added something semi-useful to that dialog - now, you can select when it updates you again, up to 4 hours later. It also doesn't seem to eventually force you to reboot like the XP one.

  8. To do it right... by jcr · · Score: 4, Insightful

    Step One: write an app for the Mac.
    Step Two: get your UI reviewed by Apple's user interface evangelist, John Geleynse.
    Step Three: make all the changes recommended by Apple.
    Step Four: write a windows app that comes as close as you can get to your Mac version.

    Or, you can do what the people who wrote Visio or that guy who ripped off Delicious Library did, and just laboriously copy an existing app knowing that you'll never make it quite the same on Windows.

    -jcr

    --
    The only title of honor that a tyrant can grant is "Enemy of the State."
  9. Thank You Microsoft! by netsharc · · Score: 4, Interesting
    Put only program shortcuts on the Start menu. Never put shortcuts to the following on the Start menu:
    • Program uninstallers. Users access uninstallers through the Software Explorer control panel.
    • Help files. Users access Help topics directly from your program.
    • Control panels. Users access control panels from the Control Panel home page.
    • Program options. Users access program options from the Options command, usually found on the Tools menu.
    • Readme files. Reconsider the need for a Readme file because most users rarely look at them. If you do need a Readme file, let users access it from your setup program.
    • Web sites. Users access Web sites through appropriate links in your program. Exceptions are Microsoft Update and Windows Catalog.

    How I hate software that install all of that in their Start Menu entries. Or programs that insist they go into "C:\Program Files\My Stupid Software Company Inc\My Stupid Program".

    Talking about reform, I find the most illogical thing of user interfaces is the menubar.. how do you exit? Go to "File". Where are the options? Under "Tools".. why can't somebody offer a totally new way of making the menu. Start with "Program", where you have "Options" and "About" (maybe "Help" too), then "Document" or "File", and then "Edit", etc.. We're so used to File -> Exit that we stop thinking how illogical such a construct is... exit the file?
    --
    What time is it/will be over there? Check with my iPhone app!
    1. Re:Thank You Microsoft! by cbiffle · · Score: 3, Informative
      Talking about reform, I find the most illogical thing of user interfaces is the menubar.. how do you exit? Go to "File". Where are the options? Under "Tools".. why can't somebody offer a totally new way of making the menu. Start with "Program", where you have "Options" and "About" (maybe "Help" too), then "Document" or "File", and then "Edit", etc.. We're so used to File -> Exit that we stop thinking how illogical such a construct is... exit the file?


      It may be worth noting that you've just described the current Mac OS X menubar layout.

      Can't blame you; I think it makes more sense too. In fact, most of the Vista guide seems to have similar aspirations (which is my way of recognizing that, even though it looks like a complete rip, it may not be).
    2. Re:Thank You Microsoft! by Jedi+Alec · · Score: 3, Insightful

      Sorry, but I very much appreciate either a help or a readme to tell me what to look at if I can't get something working. Yes, I am perfectly capable of finding the readme.txt in the folder where the program was installed, but why hassle? If I really wanted to get rid of it I can always delete the shortcut, right? Same goes for links to websites that deal with troubleshooting. If the program doesn't work, you can't access the built-in help or links.

      --

      People replying to my sig annoy me. That's why I change it all the time.
  10. Integrity? by medoc · · Score: 4, Insightful

    From the article:

    Perception is reality, and if your customers don't experience quality in your product throughout, they may conclude there is lack of quality everywhere. A visual bug seen by all your customers might do more damage to your program's reputation than a rarely occurring crashing bug.

    Mind your icons, not your buffer overflows. Great! Will exploits follow the Vista guidelines too ?

  11. Two things catched my eye by Sun · · Score: 5, Insightful

    The first - the design guidelines (10 out of the 12 listed) are focused on appearance rather than on functionality. Making sure your icons look great (#4) comes long before producing a clean interface (#10).

    The second is that this document carries a severe undertone of "make sure your app only works on Vista, and looks out of place on anything other than Aero". The entire document keeps saying "use Vista only API whenever you can" and "visually design the application to look out of place when not using the Vista UI" (with a few exceptions).

    I guess this is how MS are trying to fight the competition formed by previous OSes being good enough. They try to make sure new applications don't work on them any more.

    Shachar

  12. Just wrapped it up tonight by sporkme · · Score: 3, Insightful

    Vista user experince... for crap. I spent the past couple of months testing this OS, and when my gaming XP boot feels like a safe haven, I know that something is definitely wrong. For migrating XP users, the interface feels counter-intuitive. Even more telling, my college-going roommate has only ever known Red Hat (thank you very much, he has only ever known linux on the front-room computer), and for him the simplest task, like installing Firefox (where's the package?) was torture (not to say there has been a change here). I became so frustrated with ctrl-esc,r yielding a "r" in the ever-so-laggy search sub-start dialogue (instead of a run window) tonight that I just blew out the whole partition. I actually wanted to run iexplore for once! I am downloading Mandrake 64 now, thank the creator.

    I found Vista to be too heavy on the eye candy, and it seemed that "power tools" and control panel received heavy design attention, while the ~deeper~ apps like regedit and msconfig are the same old barf. Vista = skinned XP != new OS. Meh. Shiny? Yes. New? No.

  13. user Rule #2 by BiggerIsBetter · · Score: 4, Funny

    Do NOT install Vista. ;-)

    --
    Forget thrust, drag, lift and weight. Airplanes fly because of money.
  14. the best bit by joe+155 · · Score: 4, Funny

    I just loved this bit;

    "# Focus on what users really need to know. Don't avoid important text--be explicit whenever necessary--but don't be redundant or verbose. Because users often scan text, make every word count. Simple, concise text not only saves screen space, it most effectively conveys an important idea or action.

    # Remove redundant text. Look for redundant text in window titles, main instructions, supplemental instructions, content areas, command links, and commit buttons. Generally, leave full text in instructions and interactive controls, and remove any redundancy from the other places.

    glad to see MS don't break their own rules!

    --
    *''I can't believe it's not a hyperlink.''
  15. Yes/No dialogs again by roskakori · · Score: 5, Insightful

    One of the worst misfeatures of Windows (and its developer community) is the retarded design of dialogs. AFAIK the pre-Vista API has a bunch a simple functions to do Yes/No and Ok/Cancel dialogs, but nothing to label buttons sensibly. So it's quite common to have a dialog with "Yes" and "No" buttons, and and huge text explaining what these options mean. Despite the fact that every at least semi-decent article or book about dialog design recommends to use verbs for button labels.

    I recently read that Vista finally offers an API to easily change the button labels. Yeah! And guideline 5 (Use task dialogs for new or frequently used dialog boxes and error messages) specifically recommends:

    Use positive commit buttons that are specific responses to the main instruction instead of generic labels (such as "OK"). Users should be able to quickly grasp the options by reading the button text alone. Always start commit button labels with a verb.

    Yeah again!

    However, above this guideline we can see a screenshot of the classic, super retarded Windowesque "Save changes? Yes/No/Cancel" dialog.

    I suggest for the final document they just copy this dialog from any random Mac OS application and put a Vista theme on it.

  16. I have one for Microsoft by Greyfox · · Score: 3, Insightful
    Don't let the application handle the window frame. Even their latest OS feels sluggish and unresponsive when retarded applications (Like Outlook) stop processing Window frame controls because they're syncing from the network or some other bullshit. I should always be able to move, minimize and close an application immediately no matter what that application is doing. This has been a pet peeve of mine ever since I was first exposed to Windows back in the 3.0 days. OS/2 actually had the threaded OS before Microsoft did and you could always tell the shoddy knock-off ports of Windows 3.1 software from the code that was actually written for OS/2 because proper OS/2 code at least made an effort to process events in threads, while the knock-off ports would hang the entire OS up when they stopped processing events to index disk and stuff and the system input queue filled up. At least Microsoft got that right and most of the time a misbehaving application will only lock up its own window.

    Now if an application were written properly this wouldn't be an issue -- the application would have a thread dedicated to UI work and in theory the interface should be highly responsive, but you're trusting all the application developers to implement their programs properly and not even Microsoft is capable of setting a good example. Their OS would almost not suck if they'd just fix this one design flaw and I'm going to keep blowing this horn until they do.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  17. Still, they make the same error by tetrode · · Score: 3, Informative

    Their common dialog box is still yes no cancel. While gnome and kde (i think) has adopted a different and in my opinion far better strategy.

    People are afraid of doing things wrong. Especially at a computer, as they have learned that a computer is *VERY* unforgiving. Turn it off, and your document isn't saved, you get chkdsk errors, your operating system does not start, you have to pay your local guru big bucks or a bottle of wine to keep the damn thing running. Turn the TV off and on again and it all works. You need to treat the computer with respect. So you say (err - click) yes to it - all of the time.

    Do you want to save the document: Yes
    Do you want do delete the folder: Yes (o shit)
    Do you want to uninstall this application: Yes (where were these disks again)
    Do you want to format this disk: Yes

    Now, look at gnome. That interface is talking to you in a quite different way. When you close gedit (the notepad equivalent) without saving, it will tell you

              Do you want to save the document 'xyz'
              If you don't save it, your changes of the last n seconds will be lost

              [Don't Save] [Cancel] [Save]

    Now that is informative, and i really have to make a meaningful choice. I need to choose between Save and Don't Save. Or I pick cancel which will surely take me back to the previous state.

    Much better than the windows common control, which has been devised in Windows 2.0 (I kid you not) and still in Windows fscking Vista, noone has had the courage to reread 'About Face' and reshape it.

    Sigh

    Mark

  18. Re:Rule 11 by UnknowingFool · · Score: 4, Funny
    Use notifications judiciously" which is a great change

    But will MS follow their own rules? Hold on a sec . . .

    I see that you are posting a reply. Would you like me to open a search on MSN? <Yes><No> Clicks No

    Anyway, given the many complaints on Vista's security, it would seem MS isn't following their own rules--
    You are posting a remark disparaging Microsoft. Would you like to learn more about the great company Microsoft? <Yes><No> Clicks No

    While there maybe good reason to lock down Vista, you would think that MS would make it less annoying--
    You maybe posting information which may harm security. Would you like to continue to do so? <Yes><No> Clicks Yes

    You have insufficient privileges to post this reply. Please contact the network administrator for privileges.

    WTF? %$%#&@!
    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  19. Don't dumb it down. Not all your users are dumb. by oyenstikker · · Score: 4, Insightful

    Present choices * and settings in terms of user goals, not technology. Use everyday words when you can. This is especially
    effective if you are explaining a complex technical concept or action. Imagine you are looking over the user's shoulder and explaining how to accomplish the task.

    Technology-based:
    * Enable Internet Connection Sharing host
    * Manual Duplex

    Goal-based:
    * Allow other network users to connect through this computer's Internet connection.
    * Print on both sides of the paper.


    This tendancy annoys me more and more with ever release of Windows, for many reasons:
    1) Most everybody knows what "duplex" means. Why not let those who don't learn what it means instead of pretending the word doesn't exist, and encouraging people to forget.
    2) When I am on the phone with a user, I can say "look for the options that says something like "Internet Connection Sharing". Most users will not find the goal-based option, as it does not include the word "sharing".
    3) I know what I'm looking for. I know what it was called in NT4, 2000, and 2003 server. Now I have to read paragraphs and guess that "Allow other network users to connect through this computer's Internet connection" is Internet Connection Sharing and not Web Proxy.
    4) It encourages the user to not learn about the very complex piece of equipment he just bought. If you provide a good searchable manual instead of dumbing everything down, the program will be easier to use, and the user will learn more.

    Imagine if your grill didn't say "Ignite" above the red button, but "Make the fire start", or if your toaster didn't say "Toast", but "Make your bread crispy", or if your car didn't say "ABS", but "Automatically remove and reapply pressure on the brake so your car doesn't skid. Don't pump your brakes".

    This is slashdot, so I need to reference either Orwell or Rand:
    Or are they trying to reduce English to a smaller set of simple words that everybody can understand? Double-plus ungood.
    --
    The masses are the crack whores of religion.