Slashdot Mirror


Are End Users to Blame for OS Flaws?

tomsHH writes to mention OSWeekly author Brandon Watts claims that really it is end users who should be blamed for many OS flaws. "Believe it or not, as users, we also have a large role to play in the evolution of an operating system. We use what's been created, and this means that we're the best people to turn to for judging what works and what doesn't. Passionate communities that are supportive aid development, and when users join their efforts to make their voices heard, this benefits everyone. Have you ever thought that if you wanted something to be improved, then maybe you should just speak up and offer a solution instead of quietly or publicly venting without offering any input? Nothing changes by staying the same. Companies are listening, and as taboo as it may seem, most of them want to make their users happy, so if you shout loud enough, you're bound to be heard. If you need proof of this, then just look at how Linux has progressed in its development."

14 of 278 comments (clear)

  1. answers: by N3wsByt3 · · Score: 5, Insightful

    Short answer: yes.

    Long answer: yes, but the OS should be robust enough to deal with clumsy endusers.

    --
    --- "To pee or not to pee, that is the question." ---
    1. Re:answers: by Jarjarthejedi · · Score: 4, Insightful

      The only problem with your long answer is that it's impossible to fully deal with clumsy users without restricting them severely.

      A famous quote by Douglas Adams was "A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools."

      In a perfect world with a perfect OS it would be robust enough to handle all user errors. In that same world we'd all be driving flying cars and live in peace, no one would ever starve and mySpace would never have been invented...oh, and the RIAA would promote people using the things they buy to their fullest :P

      --
      There are two kinds of fool One says 'This is old therefore good' Another says 'This is new therefore better'- Dean Ing
    2. Re:answers: by vertinox · · Score: 4, Insightful

      The only problem with your long answer is that it's impossible to fully deal with clumsy users without restricting them severely.

      Its not as much as restricting them but actually minimizing damage control.

      Take for example Excel 2003 (not really OS but still related in the menu structure)

      If you open a CSV file and add formulas and formatting, and then save it will warn you that if you save as a CSV it won't of course save the the formatting and formulas and asks if you are sure you want to save the file as CSV format.

      Of course most users will read this as "Do you really want to save the file" and hit yes when they really needed to go to file save as and choose .xls as the file format.

      Which is why you really need to word your prompts so that it isn't just a Yes or No button (OS X apps usually strive to do this... except for the MS ones for some reason) and that the prompt actually could be understood correctly when only skimming the words.

      Of course someone is always going to do the wrong thing, but you have to make it so a person would naturally choose the option that will hurt them less by default.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    3. Re:answers: by SnowZero · · Score: 4, Insightful

      Instead of taking the "one size fits all" approach, why not make the OS vary its approach depending on the knowledge of the user? I've often joked with friends that the first thing an OS should do when it installs is quiz the user about technical knowledge. Some people are willing to admit to being a novice, but many aren't. Forums are constantly full of people complaining about software, where it often turns out to be someone who decided to select "expert" and then got over their heads. You see a lot of this on computer hardware forums/rating sites as well -- people who got way ahead of their knowledge, broke something expensive, and now blame the company.

      Now, it would be a lot harder to design a variable UI which adjusts to the user's knowledge, and I don't expect one any time soon. However, that's the only long-term solution I can see where all users can be happy, from novices to experts. No single approach will ever fit all users.

    4. Re:answers: by dgatwood · · Score: 4, Insightful

      Right. The dialog should say "Are you sure you want to save as a CSV format file? ALL FORMATTING AND FORMULAS WILL BE LOST." Two buttons: "Save as CSV Anyway" and "Save as XLS". The default should be "Save as XLS" because the safe choice should always be the default. Maybe a cancel button, too.

      That said, the #1 best way to protect against user error is to not have problems like this in the first place---design every file format and application to support reverting to previous states. For example, if there is a file format that provides a limited data set, save the file, but save a second file right beside it with the full data set. Tell them what you are doing and why. "Note: The CSV format cannot support the formatting and/or formulas used in this document. For your convenience, a copy in XLS format has been saved in the same location with formatting and formulas included." Give them the ability to do what they ask (even if it is probably the wrong thing to do), but provide a way for them to get back to a known good state if they screwed up.

      In an ideal world, file formats would be designed to support this. An example of a good file format is the RCS format used by CVS. You have the current TOT stored as a complete copy, then every previous version as a reverse diff. I'd go one step farther, though. Add metarevisions that refer to arbitrary later revisions without branching. Revision 1.13 might incorporate changes, then 1.14 might revert to 1.12. Since 1.13 would now be defined as a diff from 1.12, the 1.12 revision diff from 1.13 would be cleared to reduce storage, and would be replaced by a metarevision that says "see 1.14". In this way, it becomes simple to have unlimited undo and redo without ever losing any of the states. If you undo ten revisions and make a new change, you could still back out that change, back out the undos, and you'd be back to effectively another branch.

      Combine this with a format that is unknown-data-tolerant and a software architecture designed to support passing along unknown attributes (such as XML) and you can create a very user-friendly environment that is version agnostic, OS agnostic, and fairly bulletproof. In an era where disk space is almost free, I'm surprised software developers aren't doing this already. It seems pretty obvious to me, and I've been advocating it for years.

      If every application made it so that any reasonable operation could be undone by the user if he/she made a mistake, computers would be a lot less scary for the naive user. Indeed, the prospect of ever being able to screw up and lose something forever is terrifying to non-geeks, and is the single largest user interface flaw in operating systems and application software today. Is it the part of the users? No, it is not.

      (Yes, I think log-structured filesystems are cool. Why do you ask?)

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

  2. I'd like some of what he's smoking... by rbanzai · · Score: 5, Insightful

    I found that to be an odd little opinion piece. It has something of the "chicken/egg" to it what with blaming users for not speaking up stridently enough... about the problems they have with the OS that... they didn't speak up stridently enough about?

    I think that most OSes receive PLENTY of feedback, strident and otherwise about perceived flaws and issues.

    This article is basically content free.

  3. Are Slashdot editors to blame for crappy articles? by Radres · · Score: 3, Insightful

    This article is nothing but flamebait intended to garnish click-through revenue regardless of whether you click on that Dice banner ad.

  4. Strongly Disagree by drinkypoo · · Score: 4, Insightful

    Companies are listening, and as taboo as it may seem, most of them want to make their users happy

    Microsoft doesn't give a shit about making you or I happy. They care about corporate customers with support contracts and umpteen-hojillion seats.

    if you shout loud enough, you're bound to be heard

    Even if you are heard, however, you're likely to be ignored. It's only when hundreds or thousands of voices in chorus ask for the same thing that any major developer gives a damn.

    If you need proof of this, then just look at how Linux has progressed in its development.

    This is an exceptionally ignorant thing to say, unless we're speaking exclusively about Open Source or Free Software or something, and we are not. Linux is driven by two groups; one is the major companies which cater to paying customers. If you have purchased a large support contract, they care about you. Otherwise not. The other group is the hobbyists. They want to implement first those things which they think would be cool, second those things which they think are necessary (these may be swapped depending on sensibilities) and third any other feature they think is cool, or would teach them something, or which would get them some props. This last can be the most powerful motivator but usually the competent are not the greatest seekers of glory.

    Compare this to a commercial corporation that only cares if you are important to the bottom line, and you will see how lame the comparison is.

    Let me tell you what companies actually care about: Money. No one cares if you say that you want the product to do X, unless lots of other people said it. But if a product comes out that does what you want and you buy it, well, that sort of thing tends to be noticed. People will then emulate that product, trying to give you what you want.

    Vote with your dollars. End of story, unless it's a free-as-in-beer Linux, and then you're either stroking someone's ego or helping their bottom line by growing their installed base and making their distribution look more desirable to corporate customers. If it's free-as-in-beer, vote with your feet, same concept. By all means tell people what you want, but don't expect to get it because unless everyone else wants it, you're probably not going to get it - again, if it's commercial.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  5. Re:Once you call it an OS flaw by Reaperducer · · Score: 3, Insightful

    A piece of industrial Sony software I work with every day is full of grammar problems.

    "Are you sure to delete?"

    Every time there's a Sony tech in the room I complain. In four years and several versions nothing's changed.

    Are end users to blame? Exactly how am I supposed to change an error message?

    --
    -- I'm old enough to have lived through six different meanings of the word "hacker."
  6. Re:Once you call it an OS flaw by OrangeSpyderMan · · Score: 4, Insightful

    I thought the same thing, a flaw is a bug. A bad implementation can be technically flawless.

    Bzzzt. Wrong, and this is the typically techy approach to OSes. An OS with no bugs is not necessarily flawless. Flaw can be other things than bugs - flawed usability (e.g. having to go through a menu, 2 sub menus and an option page just to get to a very frequently used search, or having a modern OS that only supports 320x200 on the display).
    Flaws are everywhere, in code, but also in DESIGN. And, of course, the design ones are often the hardest to fix, especially if you look at a list of flaws with only techy eyes ;)

    --
    Try NetBSD... safe,straightforward,useful.
  7. Re:Difference with Linux by westlake · · Score: 3, Insightful
    Linux users have another option not mentioned that isn't available to Windows or Mac-OS users... they can quietly/publicly vent, and then write a patch to fix the problem.

    If the Linux user base is limited to programmers than Apple and Microsoft have absolutely nothing to fear in competition for the desktop.

  8. Umm... this qualifies as a "technology column"? by dircha · · Score: 3, Insightful

    What a ridiculous little ad-filled blurb this is. This is a "column"? My mother could have written a more insightful technology column, and she doesn't even use computers.

    More infuriating is his use of the term "OS". What exactly are these user level features you are adding to your "OS"? Oh, right, things like internet browsers. Of course.

    This reads like it was written by grade school student.

    This wouldn't even pass as an insightful technical column on CNN. What is it doing here?

  9. People, collectively, will behave as people. by 91degrees · · Score: 3, Insightful

    This is a stupid argument.

    The users don't work collectively. Nor can we do anything except complain about the software flaws, which is a method that manifests itself by blaming the developers.

    So the argument seems to be we shouldn't blame the developers. We should blame ourselves for not blaming the developers.

  10. Devil Advocate by fishthegeek · · Score: 3, Insightful

    As long as end users are receiving messages like this this blaming the end user is still a bit of a stretch. What will really make a difference is when competition returns in full force to the operating system market. It took over a decade of the Big 3 auto makers making the automotive equivalent of a turd before the Japanese auto makers began to see large market gains, and the drivers didn't need to become mechanics in order to make that happen.

    Suggesting that the end user, the same people that answer "Word" when you ask them where they saved their file, could offer meaningful programming suggestions isn't very practical. End users aren't programmers and beyond feature requests or UI suggestions I can't really see them offering much. I apologize to those that like more in depth car analogies. It's been a long day and I just couldn't bring myself to try harder.

    --
    load "$",8,1