Slashdot Mirror


Improving UI and UX: Changing the "Open Source Is Ugly" Perception (opensource.com)

jones_supa writes: For four years, Garth Braithwaite has been working at Adobe on open source projects as a design and code contributor. In addition to his work at the company, he also speaks at conferences about the power of design, improving designer-developer collaboration, and the benefits of open source. Still, he argues that the user experience is weak in many open source projects. One of the largest contributing factors is the lack of professional designers contributing to open source projects. Secondary to that, there are open source project owners who are unaware of the value of design or are unsure where to start with the design process. In an interview to Opensource.com, Braithwaite talks about the UX/UI topic, and gives some honorable mentions of projects that get it right.

402 comments

  1. No thanks by Anonymous Coward · · Score: 5, Insightful

    Mozilla put UI/UX people in charge of Firefox and destroyed the product. I'll take my "ugly" open source programs any day.

    1. Re:No thanks by mwvdlee · · Score: 5, Insightful

      The problem is that UX/UI people like to invent new and exciting stuff, while they should be making stuff familiar and boring.

      An interface that a user doesn't notice while using it, is an interface done right.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    2. Re:No thanks by Anonymous Coward · · Score: 5, Insightful

      From what I've seen and read a lot of newer UI/UX people are ignoring everything that the UI/UX people learned and built up over the last 20+ years. Instead of learning what works first and how to improve it, they inject their own ideas and follow what's popular. What we end up with is a "dark ages" of sorts of innovation where we take steps backwards and are stuck with it. I agree keep the old / ugly UI until we remember how to bring the past forward with us.

    3. Re:No thanks by iampiti · · Score: 5, Insightful

      +1 to that.
      To me a computer is a tool and I find arbitrary change in UI irritating.
      The concepts of menus, toolbars and so on that have been mostly the same for 30 years on GUIs and now are being discarded as obsolete by modern designers.
      It's logical that the interfaces for touchscreens are different but the problem is that now those interfaces are being applied to desktop programs as well. And they're less efficient and certainly not optimal for desktop apps.
      I don't want to spoil the party for anyone. You can have your "mobile" UIs on desktop PCs if you want as long as I get the option to use the classic, dense and featureful UI, but the problem is that option is available less and less often

    4. Re:No thanks by PopeRatzo · · Score: 3, Interesting

      An interface that a user doesn't notice while using it, is an interface done right.

      Absolutely. In 2015, there's no reason I should have to pay any attention to your interface. If I notice your UI, you've failed.

      --
      You are welcome on my lawn.
    5. Re:No thanks by Anonymous+Brave+Guy · · Score: 5, Interesting

      A lot of "new UI/UX people" seem to be following wherever a tiny number of people from very famous tech firms lead. Unfortunately, this remains true despite those tech firms themselves producing some of the most horrible user experiences I can recall in a multi-decade career recently, often as a direct result of following the same path themselves.

      For example, on a lot of web or graphic design forums, if you even try suggesting that flat design is almost always a bad idea that is built on poorly chosen basic design principles, you have a pretty good chance of being downvoted/modded/censored into oblivion. This remains true even if you try to present a neutral, objective case based on specific examples of poor usability, never mind trying to engage in wider debate about artificially limited tools leading to over-emphasis of icons (even though icons are frequently a bad choice for almost anything), over-emphasis of animations (even though animations often do more harm than good), trendy large and lightweight fonts harming readability, lack of brand differentiation because of the near-uniform appearance of everything, and so on.

      And don't even think about going beyond generic flat design to criticising Apple's recent design efforts or Google's Material Design, because you might as well just hand in your geek card on the spot.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    6. Re:No thanks by Anonymous Coward · · Score: 0

      Someone needs to tell Google and Microsoft. They keep switching their UIs around every release for absolutely no reason.

    7. Re:No thanks by radarskiy · · Score: 1

      "The problem is that UX/UI people like to invent new and exciting stuff, while they should be making stuff familiar and boring."

      Which is completely unlike non-UI/UX open source programming, right?

    8. Re:No thanks by Oligonicella · · Score: 1

      Just because non-UI/UX open source programming is screwing up doesn't mean you have to follow suit.

    9. Re:No thanks by Anonymous Coward · · Score: 2, Insightful

      Someone needs to tell Google and Microsoft. They keep switching their UIs around every release for absolutely no reason.

      The reason is always the same : how can we sell you the same crap over and over again ? Answer : we redesign the UI and pronto, we've got a new product on our hands.

    10. Re:No thanks by Anonymous Coward · · Score: 0

      Exactly. All the fancy design work usually comes with a big penalty when it slows things down and causes more crashes. Sometimes all people need is a functional program than does a job, not a work of art with a bazillion new features.

    11. Re:No thanks by chipschap · · Score: 3, Interesting

      +1 to that.

      To me a computer is a tool and I find arbitrary change in UI irritating.

      And +2 to your comment. I use a computer to Get Stuff Done. Hipsterism in the UI (look at Windows 8 if you want to see the worst of it) works against me, not for me.

      I don't mind a bit of style, but really, a plain old boring interface that enhances my ability to work is what I want.

      Maybe that's why I like text-mode interfaces (I'm a big Emacs user). Text mode is dull and boring but it lets me do my work effectively.

      Granted, everyone doesn't need or want to go to such a basic interface level. But how helpful are dancing cursors, animated icons, illegible fonts, and all the other "hip" things? My computer interface isn't a fashion statement, it's a tool!

    12. Re:No thanks by Hognoxious · · Score: 4, Interesting

      From what I've seen and read a lot of newer UI/UX people are ignoring everything that the UI/UX people learned and built up over the last 20+ years.

      The GUI was a solution to a problem, and the problem was the command line.

      Those who remember the command line, linux dweebs aside, are dead or retired. Correction: those who remember having nothing but a command line are dead or retired.

      Thus the current generation have forgotten what problemns have been solved, and they're creating them again. Bizarre cryptic commands, weird gestures on an unmarked screen area: both violate discoverability.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    13. Re:No thanks by Anonymous Coward · · Score: 0

      From what I've seen and read a lot of newer UI/UX people are ignoring everything that the UI/UX people learned and built up over the last 20+ years.

      The GUI was a solution to a problem, and the problem was the command line.

      Those who remember the command line, linux dweebs aside, are dead or retired. Correction: those who remember having nothing but a command line are dead or retired.

      Thus the current generation have forgotten what problemns have been solved, and they're creating them again. Bizarre cryptic commands, weird gestures on an unmarked screen area: both violate discoverability.

      Guess all the people using Power Shell are dead, according to you?

    14. Re:No thanks by JoeMerchant · · Score: 1

      A lot of "new UI/UX people" seem to be following wherever a tiny number of people from very famous tech firms lead.

      This is the world of fashion in general - trend spotters, hoping to be able to call out "the next big thing" before it hits often enough to make a name for themselves.

      It really has no place in UX, unless you're designing a trendy product like Candy Crush.

    15. Re:No thanks by JustAnotherOldGuy · · Score: 2

      The problem is that UX/UI people like to invent new and exciting stuff, while they should be making stuff familiar and boring.
      An interface that a user doesn't notice while using it, is an interface done right.

      Correct. Also, too many designers feel the need to fiddlefuck with stuff that works fine, hoping to make their mark or revolutionize something or other that doesn't need to be revolutionized.

      I think (correct me if I'm wrong) it was the fucksticks at GNOME who decided to remove the upper-right minimize/maximize/close buttons, because fuck users, they don't know what they need or want even if they tell us what they need or want. Even if they complain bitterly and leave in droves! Fuck those users, we'll decide what's best for them because we know better. Suck it, you filthy users!

      They took a perfectly good interface that was familiar and well-understood, and made a stupid, pointless change just because they could. No one was clamoring for this, they simply self-justified the change. And when people complained, they got all snippy and pissy about it. They couldn't even claim it was in the interests of "saving space" or some other creative bullshit because they didn't replace the buttons with anything, and removing them didn't magically make some space appear for other things. YA FUCKING ASSHOLES.

      --
      Just cruising through this digital world at 33 1/3 rpm...
    16. Re:No thanks by mrvan · · Score: 1

      those who remember having nothing but a command line are dead or retired

      Now this is just silly. I'm mid-30 and I started computing* on an Acorn Electron (around '85?). Although Windows 3.x was released a couple years later, I used MSDOS from the moment my parents acquired a PC until windows 95 (admittedly in addition to a Acorn Archmides, which was ahead of Windows by at least 10 years at that time).

      Nowadays I adminster a number of linux servers, and although I'm sure I could set up X forwarding, as far as I'm concerned I have nothing but the CLI to run them. I do use X forwarding to the virtual host to run virt-manage because I'm too stupid to learn the vritualization commands for the once a month I use them...

      So, not only do I vividly remember the pre-GUI days, I'm not even convinced that they're over, and I have yet to touch 40...

      *) OK, I was around 5, and computing meant loading games (using CHAIN) and typing a bit of code into BBC BASIC (of the 10 PRINT "MY BROTHER IS STUPID") level. But still :)

    17. Re:No thanks by JustAnotherOldGuy · · Score: 1

      Correction: those who remember having nothing but a command line are dead or retired.

      Well...I'm not dead (yet), but I am close to retirement. And yes, I'm one of those cranky old fucks who remembers having nothing but a command line. I welcomed the advent of the GUI (and still do).

      There's a time and a place for the command line and a time and a place for a GUI. And I confess, I think GUIs (when done right) are great 99% of the time. But sometimes a command line is truly da' shizzle, dawg!

      --
      Just cruising through this digital world at 33 1/3 rpm...
    18. Re:No thanks by Anonymous Coward · · Score: 0

      Yup. I want a stable, consistent, discoverable interface, not whatever fashion trend the UI/UX expert is drooling over as tomorrow's next big thing. I do not want to play guess what that pretty picture represents. I do not want to play guess that gesture. I do not want to play find the hidden option. I do not want to play whack-a-tile. I just want to use your program/app/whatever to do stuff with minimal hassle: that is all.

    19. Re:No thanks by mrvan · · Score: 1

      To me a computer is a tool and I find arbitrary change in UI irritating.

      Which is actually a very good reason to avoid most graphical interfaces. Icons jump all over the place, toolbars move, start buttons disappear and re-appear, Unities are invented and discarded.. but things like ls and rm stay put, and the interface convention / syntax of "command --option=value argument > file" also hasn't changed.

      If your computer is an important tool, spend the couple days weaning yourself off window managers and desktop environments, and breathe out a sigh of relief.

    20. Re:No thanks by Anonymous Coward · · Score: 0

      I don't want to spoil the party for anyone. You can have your "mobile" UIs on desktop PCs if you want as long as I get the option to use the classic, dense and featureful UI, but the problem is that option is available less and less often

      Well, wrong. You can have whatever user interface you like - just don't go with a monuculture like windows or apple. For if you do, you're bound to whatever 'improvements' they think up in the future.

      This is one of the best things with open source. If you don't want to go with the bandwagon - you don't have to! I got into linux before the gnome/kde stuff. I had a GUI, but it was mostly about positioning windows. Any serious work is done on the command line, or inside editors. Well, gnome and kde came along, offering a "user experience" with gui stuff for everything. Easier for those windows types, I guess. But also slower. So my choice was neither gnome nor kde. I stayed with what I had (icewm) and still do. 15 years later I run the latest linux, but still stay with icewm because I can do that. Gnome/kde is probably fine for those used to them - they have the freedom to use what they like too.

      One of the real strengths of open source - diversity. I am not being forced into a new paradigm - enough people who like the older stuff can keep it going for decades. You don't get that choice with windows. If you liked 'the xp way', you lost when they end-of-lifed it. You can't keep an old (but updated) UI on top of a recent OS like I can.

    21. Re:No thanks by Anonymous Coward · · Score: 0

      Agree.

      I liked Microsoft Word / Excel. Great productivity packages.

      Except that when they introduced the "ribbon" interface, i just stoped using them and sticked with openoffice / libreoffice.

      And guess what, they don't have the ribbon interface.

      Why would anyone have moving / changing menu options / toolbars depending on what one is doing / what is selected?

    22. Re:No thanks by Anonymous Coward · · Score: 1

      WTF does that even mean, "no reason I should have to pay any attention to your interface"?

      How can you NOT pay attention to the interface. What other interface knobs do you NOT have to pay attention to? The steering wheel of your car? The brake pedal?

      What a dumb ass thing to say. This whole thread is idiotic.

    23. Re:No thanks by Anonymous Coward · · Score: 4, Informative

      I believe the problem with UI/UIX is more general than people realize. In short, it's the classic solution searching for a problem. For years and years, we've had loads of small improvements and innovations in UI implementations. It's really come a long way from the very first attempts at it (hello DOS and mainframe systems!), but it seems for the longest time the industry got stuck in the typical Mac OS-look. So in the late 90's, there was a surge of "cool" music players (WinAMP) and whatnot, that started to break from the old principles, with apparent success and "coolness" that others wanted to possess too.

      The problem is, whoever tries to copy the true innovators, are often really bad at the game, so you get these really bad clones, and clones of those again. It's sort of a downward spiral where the herd is constantly trying to up their game, hoping for the same success as the true innovators had. In the meanwhile, these old innovators died, probably because, despite being good innovators, they were terrible at business!

      This fad-driven development (FDD) has lead to horrible design-ideas over the years. Acolytes tend to swarm to these like flies on shit: hiding infrequently-used menu choices, unnecessarily increasing complexity, nagging popup notifications (ie. in taskbar), hiding the menu itself(!), adding sidebars with questions in Control Panel for "extra navigation" (MS Windows), limiting usability (everything Apple), forcing touch-interface onto suspecting desktop users (MS Windows), extra widgets, applets and whatnot in addition to the iconized desktop (MS Windows), forcing 3D requirements to a 2D experience (Unity), ...

      Don't read me wrong: There's alot of good intentions and some good ideas in the UI/UIX-space that have far evolved since the early days, days where just displaying a window with a menu required arcane amounts of magic. For instance, W3C accessibility, universal and reactive design, and whatever they call it these days. Much of it are not really all new ideas, but it's compiled and packaged in a more understandable, copyable and standardized format, to more effectively distribute the core ideas.

      The problem is, for true innovation to happen, there has to be total ownership and compensation for the innovators. When that doesn't happen, they merely become followers and copiers, which really doesn't bring that much innovation on the table. True innovation is also more risky, so you both pay more and risk more. In most cases, it makes sense for businesses to lean on the conservative side. Capitalism along with most human organisation, sadly enough, rewards the averages more consistently in the longer run, and need to heed both business and politics as well.

      It all boils down to the basic requirements problem: What is the problem you want solved?

      There's just never one final answer to that question.

      Captcha: detail

    24. Re:No thanks by jedidiah · · Score: 2

      I've used my editor for 20 years and it's all muscle memory. I don't need to think or pay attention to it when I use it. This is an extreme example but a good model for how an effective UI works for a real person.

      "Normal people" have trouble learning anything new. If you subject them to unnecessary UI churn, you're just going to lose them. It doesn't even matter what kind of UI it is.

      In many ways, the "stable" nature of ancient but difficult interfaces are a superior alternative to user interfaces that have devolved into "fashion".

      --
      A Pirate and a Puritan look the same on a balance sheet.
    25. Re:No thanks by vtcodger · · Score: 4, Insightful

      As far as I can see, hiring a "professional" UI/UX person is roughly equivalent to replacing your amateur alchemist with a professional. At the end of the day, you still don't have any gold.

      I once had the misfortune to work on a project that was blessed withTWO UI experts. Those two dudes agreed on absolutely nothing except that the existing UI sucked.

      --
      You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
    26. Re:No thanks by Anonymous Coward · · Score: 0

      But how helpful are dancing cursors, animated icons

      They are indicators to what is happening.

      illegible fonts

      What fonts are being used (in what products) that are illegible?

      and all the other "hip" things?

      "hip" things?

    27. Re:No thanks by Ol+Olsoc · · Score: 4, Insightful

      For example, on a lot of web or graphic design forums, if you even try suggesting that flat design is almost always a bad idea that is built on poorly chosen basic design principles, you have a pretty good chance of being downvoted/modded/censored into oblivion.

      Oh - this - so much this! The backlash against skeuomorphics has produced some of the most boring and bland and ucking fugly interfaces seen by humans.

      It's like someone said "Good design is a square of a primary color, with a letter in it." To me, the problem is across the board - UI's are getting ugly, like we are returning to Commodore 64 days when there just wasn't enough resolution to make nice looking stuff.

      And don't even think about going beyond generic flat design to criticising Apple's recent design efforts or Google's Material Design, because you might as well just hand in your geek card on the spot.

      Patience, ABV. Design, like automobiles, goes through periods of massive ugly. And that is exactly where we are at right now. This too shall pass.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    28. Re:No thanks by lucm · · Score: 1

      until windows 95 (admittedly in addition to a Acorn Archmides, which was ahead of Windows by at least 10 years at that time)

      I think you've got a bad case of "he was my first" syndrome.

      --
      lucm, indeed.
    29. Re:No thanks by lucm · · Score: 1

      things like ls and rm stay put, and the interface convention / syntax of "command --option=value argument > file" also hasn't changed.

      I think systemd is going to rock your world.

      --
      lucm, indeed.
    30. Re:No thanks by lucm · · Score: 1

      One of the real strengths of open source - diversity. I am not being forced into a new paradigm - enough people who like the older stuff can keep it going for decades. You don't get that choice with windows.

      So you must be one of those 11 Devuan users?

      --
      lucm, indeed.
    31. Re:No thanks by Ol+Olsoc · · Score: 1

      Correction: those who remember having nothing but a command line are dead or retired.

      Well...I'm not dead (yet), but I am close to retirement. And yes, I'm one of those cranky old fucks who remembers having nothing but a command line. I welcomed the advent of the GUI (and still do).

      There's a time and a place for the command line and a time and a place for a GUI. And I confess, I think GUIs (when done right) are great 99% of the time. But sometimes a command line is truly da' shizzle, dawg!

      Amen. As a user of Unix and Linux, there are times when I really appreciate the Terminal. It does things by hand and instantly.

      And over the years, an odd thing has happened. Remember when Mac users were supposedly too dumb to use a command line? Man oh man, DOS was the shitz, and dont you forget it! Now I use Terminal all the time in OS X, and of course Linux, and so many Windows users think the command line doesn't exist any more. If they ever knew about it in the first place.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    32. Re:No thanks by Anonymous Coward · · Score: 0

      Reminds me of the multi-cultural 'paradise' Europe is now taking on. Everything's equal no matter what.

    33. Re:No thanks by angel'o'sphere · · Score: 1

      in addition to a Acorn Archmides, which was ahead of Windows by at least 10 years at that time).
      Isn't the Arcon Archimedes aka Risc Os, stil ten years ahead of the time of modern Windows?

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    34. Re:No thanks by Anonymous Coward · · Score: 0

      Why would anyone have moving / changing menu options / toolbars depending on what one is doing / what is selected?

      Because it shows you the tools relative to what you are doing...obviously.
      Why would anyone have all the possible options on the screen (and duplicated in the dropdowns on the menubar) at the same time even though most of them have nothing to do with what one is doing?

    35. Re: No thanks by Anonymous Coward · · Score: 1

      I know I'm fighting an uphill battle, but UI != UX. The overall experience of a product owes a lot to its look and feel, but UX is far more than just how it looksâ"it's a combination of useful, usable and desirable. I've been in UX for 15 years and couldn't design my way out of a paper bag. My specialty is in talking to customers, understanding their needs and prototyping solutions that a designer and developer will make real. I understand how people think, and spend more time delving into workflows than I'd ever spend on gradients and color scheme.

      We have a real problem in our industry that UX is considered nothing more than UI.

      And, we have a real problem in Open Source that it's issues are seen as just skin deep. The problem with most OS products I use is that they lack a central visionâ"they are inherently designed to meet a bunch of individual needs, they lack cohesion. Making sure the experience is holistic (the right features, easy to use, that have that extra something that makes it enjoyable) is a mainstay of UX.

      So, I agree OS misses UX, but not because it's ugly.

    36. Re:No thanks by NormalVisual · · Score: 2

      I think GUIs (when done right) are great 99% of the time. But sometimes a command line is truly da' shizzle, dawg!

      Absolutely. Right tool for the job and all.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    37. Re:No thanks by dbIII · · Score: 1

      Add the current gnome to that list.
      Enlightenment however has been doing "pretty" and "useful" at the same time for getting close to 20 years. Win7 with the little application snapshot windows looks startlingly like it could be a theme from Enlightenment in 1998.

    38. Re:No thanks by dbIII · · Score: 1

      I think (correct me if I'm wrong) it was the fucksticks at GNOME who decided to remove the upper-right minimize/maximize/close buttons

      Enlightenment did that at a time too, but the reason you don't hear people bitching about it is because they did it the right way. You didn't have to use the theme with that quirk if you did not want to and themes that kept old behaviours were updated just as quickly as their odd themes. The only two things they took away over time were the direct clone of an Apple GUI (beware of lawyers) and the "pie menu" style radial menus that were difficult to include in a new codebase.

      They took a perfectly good interface that was familiar and well-understood, and made a stupid, pointless change just because they could

      Hence offices with linux stuck on RHEL6/CentOS6) since the new gnome is not ready for a workplace yet.

    39. Re: No thanks by jd2112 · · Score: 2

      Not much of an achievement as Windows 8 set Windows UI back 20 years.

      --
      Any insufficiently advanced magic is indistinguishable from technology.
    40. Re: No thanks by bill_mcgonigle · · Score: 1

      > newer UI/UX people are ignoring everything that the UI/UX people learned and built up over the last 20+ years

      To the extent that UI/UX people are HCI scientists, there's nothing wrong with it. To the extent that they're not, it's all contemptible bullshit.

      I wish one of the FLOSS desktops would get serious religion about usability science. "Fitt's Law isn't just a good idea." It would be a huge boon to the community and the user base would swell.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    41. Re:No thanks by blackpaw · · Score: 1

      Word. I'm deeply distressed that KDE seems to be going down this path. Flat widgets, low washed out contrast, tiny fonts, reduced options. Possibly the most butt ugly default wallpaper in the history of wallpapers. The ridiculous rebranding/renumber of libs/apps/plasma, so no one can figure out what version of what they have.

      The moment you try to engage with any of the devs/designers re this, no matter how tactfully, they become very hostile. Its pointless

      I keep retrying with new releases, but can't tolerate it.

    42. Re:No thanks by whoever57 · · Score: 3, Insightful

      My gripe with GNOME, which shows how (IMHO) brain-dead the UI/UX people developing GNOME are is adding things to the Panel. In Gnome 1/2. this is achieved with a right-mouse button on the panel. In Gnome 3, it requires Meta-right-mouse key (I think). Why this change? It's not reasonably discoverable. The simple right-mouse-key on the panel does not perform some other important function (it does nothing).

      I'm sorry, but anyone who thinks that adding an extra key that must be pressed to get the same functionality as was achieved without it, unless there is a really good reason, is stupid.

      --
      The real "Libtards" are the Libertarians!
    43. Re: No thanks by slazzy · · Score: 1

      Command line image editing is kind of a pain, but the best for server admin and other tasks for sure.

      --
      Website Just Down For Me? Find out
    44. Re:No thanks by MrKrillls · · Score: 0

      Yes, a thousand times yes.

      --
      Don't step on the baby.
    45. Re:No thanks by PopeRatzo · · Score: 1

      How can you NOT pay attention to the interface. What other interface knobs do you NOT have to pay attention to? The steering wheel of your car? The brake pedal?

      If you're thinking about your steering wheel or brake pedal when you're driving, you're doing it wrong.

      --
      You are welcome on my lawn.
    46. Re:No thanks by MrKrillls · · Score: 0

      Still yes.

      --
      Don't step on the baby.
    47. Re: No thanks by luvirini · · Score: 1

      Actually I have found command line image editing much better than any GUI tool I have seen when the need was to manipulate more than a tiny number of images. Doing things like creating down sampled versions of 10 000 images is so much easier with command line.

      Again getting back to the point of right tool. Unix style command line tools tend to be much better than any GUI tool when you need to repeat the same operation on multiple files.

    48. Re:No thanks by luvirini · · Score: 1

      Indeed. I wonder why people work so hard to ruin things.

      The old saying of "Never attribute to malice what can be explained by stupidity", might be true in some cases, but it boggles my mind to think that ALL UI designers could be stupid. So I am starting to think that it must be a conspiracy to make using computers hard again or something similar.

    49. Re:No thanks by luvirini · · Score: 1

      I do not know about recent UI people as I do not work with such, but when it comes to other computer education, people with recent such seem to have a lot of horrible gaps in their learning of basics way too often,

      We have had people with masters degree in Computer science that has included a large number of programming courses when asked "Name three sorting algorithms, describe the basic idea of each of them with a few words and tell when each might be a good choice" just look at you blankly. And many similar gaps.

      So I am afraid that the UI people might well be the same.

    50. Re:No thanks by Anonymous Coward · · Score: 1

      The other problem on graphic design forums is that UX gets reduced and mashed together with UI. UI deals with looks. UX deals with interaction and flow of data to and from the user. Visual elements play a role in UX, but they're just a sub-set. Visit any UX forums and you'll see a lot of graphical designs, but rarely do you see anything like flowcharts or narratives describing the experience. Mostly it's like bad programming: people start with the fun stuff - the graphics - before thinking the grand design over and formulating a plan.

    51. Re:No thanks by arglebargle_xiv · · Score: 1

      That's exactly the problem. If you take a real UX person like Tog or Jakob Nielsen or Donald Norman then you'll get a really good, usable design. Take some frustrated-artist hipster wannabe like Asa Dotzler and you get exactly what Mozilla has ended up with.

    52. Re:No thanks by gl4ss · · Score: 1

      well, that pretty much sums it up.

      nobody of ANY "UX" experts I know seem to have ANY knowledge or information about UI concepts researched for years and years during late '80s and all '90s.

      like, some people think they're UX experts because they've used twitter, facebook etc. yet they have no concept of what should happen if you double click a word or if you triple click it.

      --
      world was created 5 seconds before this post as it is.
    53. Re:No thanks by Anonymous Coward · · Score: 0

      This is how much Adobe cares about its users. Your mistake is in believing that commercial software cares about usability. It does not. It cares about people giving it money, and there are several easier, more effective methods than improving usability.

    54. Re:No thanks by Anonymous Coward · · Score: 0

      Amen double! I recently retired, and remember when a command line on a terminal (or even a teletype) was an improvement. We used JCL and cards...

      It does come down to the right tool for the job, and the GUI (there were several, though Mac derived from Xerox won quickly) was the right thing for the job. But Americans seem to think that everything has to be done one way, so when the GUI fashion designers go off on a bender we all have to follow even if it's Really Stupid and a significant impediment to computer use.

      Oh BTW, in Firefox, right click on the top of the window and check "Menu Bar" - voila! Real menu is back.

    55. Re:No thanks by AchilleTalon · · Score: 2

      Right, poorly designed GUI are not specific to open source projects. There is a lot of commercial products with poorly designed interface. In fact, coming with a good and sound design is hard. That's why over years there were rules written to guide the design of GUI. A lot of studies on how users are using GUI and other human interfaces are required to understand and decide on a good design. Even some commercial products don't get it right. Corporations are not always willing to spend dollars on the GUI. Even those spending good dollars on design are not always succeeding (a la Windows 8).

      --
      Achille Talon
      Hop!
    56. Re: No thanks by Anonymous Coward · · Score: 0

      > Doing things like creating down sampled versions of 10 000 images is so much easier with command line.

      It really isn't a question of CLI vs. GUI but whether your tool is designed to do batch processing.

      I used GraphicConverter on the Mac for many years. It did 95% of what I needed and was unequivocally much easier to use than any CLI tool.

    57. Re:No thanks by ls671 · · Score: 1

      Is Acorn Archmides related to the mighty Acorn stairlift? Just wondering...

      http://www.acornstairlifts.com...

      --
      Everything I write is lies, read between the lines.
    58. Re:No thanks by chipschap · · Score: 1

      Dancing cursors and animated icons and the like are (at least to me) an irritant for the most part. Things like progress bars actually give you useful information.

      "Hip" stuff --- all the tile nonsense in Windows 8 and up, for instance. Maybe I don't have the right definition of "hip" but for some reason I see the tiles and am reminded of hipsters who proclaim avant-garde is good simply because it's avant-garde; and because they're right maybe 1% of the time they think they are always right.

    59. Re:No thanks by AmiMoJo · · Score: 1

      A flat design can work, buy it's very hard to get right. Google has it figured out with material design, which works well for touch apps and web pages. Not ideal for desktop apps but one size fits all is probably impossible.

      Everyone else imitates them, but gets it wrong. Microsoft on the desktop, Apple on mobile. Many other app developers everywhere.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    60. Re:No thanks by davester666 · · Score: 1

      I am willing to travel anywhere and punch anybody who brings up "brand differentiation" in a discussion of UI. The idea that you will artificially make your UI less useful, just so the user will "know" which app they are using is beyond stupid.

      It is higher than "make it work the same for all platforms, regardless of each platforms UI conventions" on the scale of 0 to mind-numbing stupidity.

      --
      Sleep your way to a whiter smile...date a dentist!
    61. Re:No thanks by Aighearach · · Score: 3, Insightful

      The problem is that UX/UI people like to invent new and exciting stuff, while they should be making stuff familiar and boring.

      An interface that a user doesn't notice while using it, is an interface done right.

      Damn straight! I hate it when these jerks start trying to fluff my interface, or massage my paradigm. Leave it alone, it is a tool. That is why I chose open source, because I just want the tool that does the thing, and if I want it to do something else, I can add it.

      First they start diddling the paradigms and they say, "oh you can still use the old one" and then when a critical security patch is required, they say, "oh gosh, well you can just upgrade if you want it to be secure."

      Nothing goes to hell faster than a popular project. Give me a boring project that is grudgingly maintained with a few lines of bug fixes every few years. I'm still using gimp, it still works the same as in the 90s, and it still does all the stuff I need. I can still write plugins, now in new languages too. And it still looks the same way that people said was "ugly" and all sorts of nasty things. And the features are still in the same places. Being "ugly," for whatever reason people thought, never once stopped me from getting beautiful results with it.

    62. Re:No thanks by Anonymous Coward · · Score: 0

      One of the issues in UI design that pops up, seems to be a fashion sense. Take the Start button in Windows, which has morphed, disappeared, and reappeared over the iterations of the OS. Or the switch from skeumorphic UI design to the modern flat design which is popular now.

      What needs to be the focus isn't keeping up with the trends, but actual design, be it responsiveness (little things such as acknowledging a user double-clicked on an icon, scrolling) to consistency. Responsiveness is important. With the love for showing off the GPU, too much animation animation is perceived as slowing things down. Some animations that are quick make sense, but I've found that the perceived responsiveness of an Android device, once animations are completely turned off, is a lot better [1].

      Even though icons are overemphasized, one reason they seem to be used is that it is less text to translate, especially if an app is being written for a number of languages. Since English isn't politically correct anymore, being able to do everything with pictograms and symbols is a lot easier than trying to get people to translate Urdu, Hindi, Simplified Chinese, Traditional Chinese, and other languages.

      The thing about UIs, is that they shouldn't be the fashion statement. They display the content which is the latest "style". For example, NeXTStep, antique as it might be, did an excellent job of this. The UI elements were gray and stood in the background unless there was a warning or alert which needed color to stand out and get the user's attention. NeXTStep was probably as close to an ideal interface as you can get, since it was designed from the ground up, not just changed from another platform. The only thing it really needed would be the snappiness of IRIX's 4Dwm. However, form over function has won this round.

      Linux is where things are horrific in the UI department. With all the competing standards and libraries, how can there be a true Linux desktop? Because for an application to actually be usable, it either has to be linked statically, or be designed/engineered for one or two platforms (usually RedHat and downstreams and Debian/Ubuntu.) Plus, with each OS change, the UI radically changes as well, making it difficult on nontechnical users who have to relearn basic things, and are not going to just pop up a terminal window if they can't get a file to copy from one drive to another. Linux needs a graphical UI standard as much as a filesystem standard.

      [1]: Android has some nice features, especially allowing one to choose their UI, even when the default UI on a phone can vary significantly from the default on another.

    63. Re:No thanks by mwvdlee · · Score: 2

      Actually, you make a good analogy.

      If you are constantly distracted by the shape of your steering wheel or the inconsistent way the pedals work, they are grabbing your attention.
      When you're driving, you're typically thinking about what is happening on the road. If you are thinking about how to use the car; get off the road and hand in your drivers license.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    64. Re:No thanks by mwvdlee · · Score: 1

      Everybody likes to invent new and exciting stuff, including programmers, not just open source ones either.
      The difference is that in programming, building something that already exists results in a program nobody needs or wants.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    65. Re: No thanks by Anonymous Coward · · Score: 0

      Not Gmail. Even after 30 years of brogramming experience, I still have trouble assisting people in that interface. Search is dead simple and the innovation there was simplicity. Solutions should fit the problem, not be shoehorned on top of them.

    66. Re:No thanks by thegarbz · · Score: 1

      So how is a flat design based on poorly chosen design principles, or a bad user experience?

      I understand many of the interaction choices that accompany a flat UI design are flat out terrible (pun intended), but in many scenarios I don't see anything intrinsically be about them. The notable exception here is multitasking with a UI that allows arbitrary window placement. In that scenario having some depth or a drop shadow or something gives you a good indication of what is where in the work place, but on websites, phones, or within application windows what's the problem with a flat design?

      So far most of the arguments I've heard haven't been anything more substantial than "It looks fisher price and I don't like it."

    67. Re: No thanks by Anonymous Coward · · Score: 0

      As a general rule, command line options are more powerful because defining the GUI for a new feature is an additional effort that will always lag behind, or won't be done at all if the feature isn't popular with the majority of users. What makes this worse is the tendency for designers to be "minimalistic", ie make functionality inaccessible and have stuff pop up out of nowhere only to disappear again. It would be great to have an automatic graphical rendering of all available CLI options, with context help and input fields that accept/propose/hint at what kind of input is expected for a parameter. I know there are advanced shells but they're still very terminal-like and not really interactive and discoverable.

    68. Re: No thanks by Anonymous Coward · · Score: 0

      You say UI as if it was a bad word. UI is UI. Bad UI is bad UI. Same with UX, and anything else in the world. And UX is mostly UI by definition.

      It's like people "rejecting politics", because they understand today governments as the epitome of mediocrity. Well, guys, if people named politicians are that incompetent, it very logically means they are not politicians, by simple definition. So just stop calling them that, and find what true politics is about, instead of throwing everything out the window in rage...

      People rejecting UI, UX, accessibility, and testing, are being utterly stupid.

      What Firefox and Gnome/GTK got subjected to is precisely the opposite of UX. The people who made these stupid changes are just equally stupid. They are incompetent assholes with zero knowledge of UX. Just as most programmers rejecting UX. They are actually often the same people too. For sure there are more and more marketing types messing everything up, but it's not as if everything was rosy before. Programmers rejected UX long before, and many are now trying to push through, contributing heavily to today trash software environment.

      These people are in no way "UX experts", so just stop calling them that. I don't know what can be done to either retake the projects from their hands, or make them understand how incompetent and dangerous they are (well, I'm pretty sure some of them at least know all about it... M$ vengeance against geeks, anyone?), but it certainly won't start by negating UI, UX, accessibility, and testing, and their importance in software development.

    69. Re:No thanks by vtcodger · · Score: 4, Interesting

      By an odd coincidence, about 20 minutes after I posted that, my wife was confronted with a family emergency and needed driving instructions to a city around 400km from here. Google maps used to have a straightforward interface that worked well (albeit a bit slowly) with just about any browser. But about 6-8 months ago they replaced it with a modernized, low-contrast, monstrosity with one of the more opaque UIs I've ever encountered. Apparently it only works with a "modern browser", because I had to go through three PCs and 5 browsers to find one (Chromium as it happens) that would actually display and print driving instructions. I'm sure the folks at Google are very proud of their shiny new UI. I can't think why.

      I think perhaps I am expected to upgrade the user end of this workflow. i.e. I need to be replaced with a more modern user.

      --
      You can't see ANYTHING from a car, You've got to get out of the goddamned contraption and walk...Edward Abbey
    70. Re:No thanks by Anonymous Coward · · Score: 0

      Your reading comprehension is poor.

      > those who remember having nothing but a command line
      does not include, in its entirety, as a subset
      > all the people using Power Shell

    71. Re:No thanks by Anonymous+Brave+Guy · · Score: 1

      You imply a distinction where none exists. Any UI will inherently have some look and feel, in the format of CLI commands, the visual style chosen for icons in an application, the overall layout for a web page, or a thousand other factors. Any UI will therefore potentially become part of a brand image.

      It's not really about a UI being more or less useful. No UI exists in a vacuum, but usability is mostly an orthogonal consideration to branding IME. To the extent that it is not, a UI should be designed to meet the needs of the project as a whole, like any other part of a software project. You can have the best UI in the world, but that doesn't help if no-one is running your program, and so there are legitimate questions about for example making a UI easier for new users to discover but at the expense of being slightly less efficient for experienced "power users".

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    72. Re:No thanks by Half-pint+HAL · · Score: 4, Insightful

      Oh - this - so much this! The backlash against skeuomorphics has produced some of the most boring and bland and ucking fugly interfaces seen by humans.

      It's like someone said "Good design is a square of a primary color, with a letter in it." To me, the problem is across the board - UI's are getting ugly, like we are returning to Commodore 64 days when there just wasn't enough resolution to make nice looking stuff.

      There has been an overreaction, certainly, but that's due to people not listening to the complaints about skeuomorphism.

      The problem with skeuomorphic design is that it ignores the basic principles of what an "icon" is, and how the human brain works. The point is that the gradings and shadings and pseudo-3D projections on Windows XP icons were slower to process cognitively than their Windows 95 equivalents. The trick to a good icon is to find the simplest unambiguous "form" that prototypes the concept to the human brain. A good example of flat design is the icon for iBooks on iOS -- it's a minimal unambiguous representation of a book.

      A contrasting bad example would be the icon for Facetime. It's not instantly recognisable as a video camera, and even if it was, "video camera" is not a synonym of "video call".

      I specifically used two examples from iOS because this isn't about my views on Apple (the iPad was given to me, my laptop runs Windows and Linux), but just about the principles. Flat design is not a panacea -- it is just one principle of many that make up UI/UX design. Flat design on its own is useless -- flat design is supposed to make it easier to apply the other principles.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    73. Re:No thanks by Half-pint+HAL · · Score: 1

      Flat widgets, low washed out contrast,

      This shows a total failure to understand the point of flat design -- one of the arguments against skeuomorphism is that it often results in low contrast, slowing down mental recognition of icons. Flat design is supposed to mean high contrast. If you have low contrast in your flat UI, you're doing it wrong.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    74. Re:No thanks by Anonymous+Brave+Guy · · Score: 1

      I honestly thought your post was satirical for a moment. Then again, I honestly thought Google's introduction video when they launched Material Design was satirical too.

      Google are among the worst offenders with the flat design idea. Google Mail has a terrible case of iconitis, for example. But just look at the basic design elements in Material Design generally, and you can see many of the common criticisms of flat design perfectly illustrated. For example, MD can lack differentiation between component of a site/app, and thus may not clearly show how the user can interact with them and what any current status is, all a direct result of the limited palette of expressive options available to those designing UIs.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    75. Re: No thanks by Half-pint+HAL · · Score: 1

      Command line image editing is kind of a pain, but the best for server admin and other tasks for sure.

      Not if you want to make global changes to the image. If you're correcting contrast etc, a command line is often much quicker than faffing about with buttons and sliders.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    76. Re: No thanks by Z00L00K · · Score: 1

      Firefox isn't the worst example, Windows 8 is a recent horrible example together with the ribbon menus.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    77. Re:No thanks by Half-pint+HAL · · Score: 1

      Things like progress bars actually give you useful information.

      To power users, maybe. To average users, a progress bar is something that keeps stopping, making them think that the computer has crashed. Horses for courses -- if you have a task that you can use a progress bar for (ie the task has predictable time) then use it. If it doesn't, don't.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    78. Re:No thanks by Anonymous+Brave+Guy · · Score: 1

      My experience is a little different, in that I also know a few competent people who have resorted to putting UX in their job title just because of client/employer expectations. But yes, there are unfortunately a lot of people around who think putting UX in their job title makes them more important than someone who "only does UI", even if the latter person knows and can do more than the "UX expert" in almost every way.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    79. Re:No thanks by Half-pint+HAL · · Score: 1

      "The problem is that UX/UI people like to invent new and exciting stuff, while they should be making stuff familiar and boring."

      Which is completely unlike non-UI/UX open source programming, right?

      Yes. A heck of a lot of open-source software is just functional clones of commercial packages.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    80. Re:No thanks by Half-pint+HAL · · Score: 1

      The reason is always the same : how can we sell you the same crap over and over again ? Answer : we redesign the UI and pronto, we've got a new product on our hands.

      Except that Windows 10 is a free upgrade.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    81. Re:No thanks by Anonymous Coward · · Score: 0

      This is exactly what I would characterize as certainly a giant problem among open source developers. Add on to that that we've still got people who adamantly believe that if code was hard to write, the program should be hard to use, and we're still in a terrible state.

    82. Re:No thanks by Ol+Olsoc · · Score: 1

      Oh - this - so much this! The backlash against skeuomorphics has produced some of the most boring and bland and ucking fugly interfaces seen by humans.

      It's like someone said "Good design is a square of a primary color, with a letter in it." To me, the problem is across the board - UI's are getting ugly, like we are returning to Commodore 64 days when there just wasn't enough resolution to make nice looking stuff.

      There has been an overreaction, certainly, but that's due to people not listening to the complaints about skeuomorphism.

      There's no doubt that some got goofy with it, but abandoning it is like throwing the bby out with the washwater..

      The problem with skeuomorphic design is that it ignores the basic principles of what an "icon" is, and how the human brain works. The point is that the gradings and shadings and pseudo-3D projections on Windows XP icons were slower to process cognitively than their Windows 95 equivalents. The trick to a good icon is to find the simplest unambiguous "form" that prototypes the concept to the human brain.

      While I won't presume to say the XP icons were good, some attractiveness would be nice. The king of the 3-D look was Apple of course, and interestingly enough, was used by a lot of artist and Illustrators, th elatter of whom know a lot abotu this kind of thing.

      And while I'm not always in love with the new icons in OS X, they've retained a little of their 3-D look.

      Now the thing about processing icons cognitively. I don't really need to process icons. They are just what I use to access the programs I want. What I want from my desktop is something attractive to look at.

      Now we are into an entirely different field of ambiguity. Since I find flat squares with a little text inside soul suckingly boring, and artless, I don't want to look at them. Others might find them beautiful. All a matter of taste.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    83. Re:No thanks by Anonymous Coward · · Score: 0

      Oh - this - so much this! The backlash against skeuomorphics has produced some of the most boring and bland and ucking fugly interfaces seen by humans.

      It's like someone said "Good design is a square of a primary color, with a letter in it." To me, the problem is across the board - UI's are getting ugly, like we are returning to Commodore 64 days when there just wasn't enough resolution to make nice looking stuff.

      There has been an overreaction, certainly, but that's due to people not listening to the complaints about skeuomorphism.

      The problem with skeuomorphic design is that it ignores the basic principles of what an "icon" is, and how the human brain works. The point is that the gradings and shadings and pseudo-3D projections on Windows XP icons were slower to process cognitively than their Windows 95 equivalents. The trick to a good icon is to find the simplest unambiguous "form" that prototypes the concept to the human brain. A good example of flat design is the icon for iBooks on iOS -- it's a minimal unambiguous representation of a book.

      A contrasting bad example would be the icon for Facetime. It's not instantly recognisable as a video camera, and even if it was, "video camera" is not a synonym of "video call".

      I specifically used two examples from iOS because this isn't about my views on Apple (the iPad was given to me, my laptop runs Windows and Linux), but just about the principles. Flat design is not a panacea -- it is just one principle of many that make up UI/UX design. Flat design on its own is useless -- flat design is supposed to make it easier to apply the other principles.

      The problem with using icons is that they lose meaning over time. How many children today will recognize a receiver from an analog telephone? You can use that icon to imply it has to do with a phone, but modern phones don't use that design. Same with the 3.5 inch floppy disk icon for the Save function. When was the last time you saw a physical floppy disk? The speaker icon is another one. You don't see many speakers that look like that in the modern world. How about the mouse with a cord icon? My point is that words would work better than icons. If you have to associate a word with an icon display, then it does not really represent what you intend(Save listed under the Floppy Disk, Paste under the Clipboard, etc.).

    84. Re:No thanks by Anonymous Coward · · Score: 0

      Hi, I just modded you down. Why? Because you can't add stuff to the panel in GNOME 3. If you're adding stuff to a panel, you're doing it on a non-official panel which is not governed by those UI/UX people that are developing GNOME.

      Also, while said designers have obviously done some stupid stuff, they are also (slowly) learning and undoing some of the damage. Yes, it would be nice if they could run their experiments on people in a lab, but it's open source and c'est la vie. And they did arrive at some stuff that's just obviously better in GNOME 3. For instance, I interact much less with the GUI (e.g. mostly just super + "term" RET for starting a terminal) compared to how what I used to.

    85. Re:No thanks by Anonymous Coward · · Score: 0

      So you must be one of those 11 Devuan users?

      People probably mocked the Pale Moon developers for forking Firefox because of their decisions that ignored the community, too. There are people out there that don't want systemd, and Devuan will try to fill that need.

    86. Re:No thanks by morgauxo · · Score: 1

      No, speakers pretty much still look like speakers. Well.. we do have a lot of ultra-portable equipment around like our phones and tablets which have flat speakers. Those all sound like shit though. If you open up anything with a half-way decent sound and look inside a speaker is still a cone with a magnet on the end. Don't open your stuff up? Do you have a car? Can't you see the speakers from underneath every time you open your trunk?

    87. Re:No thanks by Shark · · Score: 1

      Just imagine what would happen if car manufacturers went the same route with their 'interface'. Seat? Nope, that's old and outdated, you must now hang from a harness. Steering wheel? What is this, 1920? Have our new kinect-like steering control.

      --
      Mind the frickin' laser...
    88. Re:No thanks by drinkypoo · · Score: 3, Insightful

      The king of the 3-D look was Apple of course, and interestingly enough, was used by a lot of artist and Illustrators, th elatter of whom know a lot abotu this kind of thing.

      I really liked Be's vivid, isomorphic icon style. It was a fad for a moment and then died down, but I miss it. The icons were very clear and easy to see, but also attractive.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    89. Re:No thanks by drinkypoo · · Score: 1

      Now I use Terminal all the time in OS X, and of course Linux, and so many Windows users think the command line doesn't exist any more. If they ever knew about it in the first place.

      Most likely, you are simply an unusual user. However, I do often see the answer to a Mac users' question be "enter this cryptic command into Terminal" and then I laugh and laugh, or usually just sort of smirk because who actually lols all the time over this nerd crap? But seriously, for ages the Mac users were smug upon smug over Windows users having to go to the command line, or having to bang on the registry. Now Mac users have a command line, and plists that get boned. Meanwhile, Windows just works most of the time. Too bad it's super-duper spyware now. I was, no shit, legitimately excited about Windows 10. Not very, but a little bit. Now I'm just wondering which Linux distribution I'm going to get excited about next, and happy about the ongoing trend in Linux gaming support. I've got a Windows 7 PC for gaming, and that's working just fine.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    90. Re:No thanks by drinkypoo · · Score: 1

      Hi, I just modded you down. Why? Because you can't add stuff to the panel in GNOME 3. If you're adding stuff to a panel, you're doing it on a non-official panel which is not governed by those UI/UX people that are developing GNOME.

      When you slow down for long enough to remove the GNOME'S gcock from your gmouth, maybe you'll consider that you just jerked off with negative moderation when you could have spent that point positively somewhere, encouraging something you'd like to see more of... instead, you served as GNOME's gimp, while they're clearly in the process of continuing to shit all over something that people used to use and then acting all superior over it. That you cannot add things to the panel is beyond idiotic, not something to downmod someone over.

      Yes, it would be nice if they could run their experiments on people in a lab, but it's open source and c'est la vie.

      Yes, the users have left in droves, and c'est la vie.

      For instance, I interact much less with the GUI (e.g. mostly just super + "term" RET for starting a terminal) compared to how what I used to.

      I don't want to have to use the keyboard to get things done any more than I want to have to use the mouse. Taking away functionality from the user is not the answer, especially when it was possible to configure that functionality away before, anyway.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    91. Re:No thanks by Ol+Olsoc · · Score: 1

      The king of the 3-D look was Apple of course, and interestingly enough, was used by a lot of artist and Illustrators, th elatter of whom know a lot abotu this kind of thing.

      I really liked Be's vivid, isomorphic icon style. It was a fad for a moment and then died down, but I miss it. The icons were very clear and easy to see, but also attractive.

      I looked it up since I wasn't familiar, and it definitely is vivid with a lot of color. Very cute. And no problem whatsoever with understanding the icons.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    92. Re:No thanks by Ol+Olsoc · · Score: 1

      Now I use Terminal all the time in OS X, and of course Linux, and so many Windows users think the command line doesn't exist any more. If they ever knew about it in the first place.

      Most likely, you are simply an unusual user.

      Very possibly. Years ago our head of computer security was a Mac Guru, and took me under his wing. Then a Linux/Mac nerd adopted me, and it was almost like the magic of my Commodore 64 days of computing discovery

      However, I do often see the answer to a Mac users' question be "enter this cryptic command into Terminal" and then I laugh and laugh, or usually just sort of smirk because who actually lols all the time over this nerd crap?

      I'm guilty.

      But seriously, for ages the Mac users were smug upon smug over Windows users having to go to the command line, or having to bang on the registry.

      Part of the fun of moving over to Unix, I guess.

      Too bad it's super-duper spyware now. I was, no shit, legitimately excited about Windows 10. Not very, but a little bit.

      The pity is, the damn OS itself works so well. But the spyware, key logger, and mandatory updates bitching up people's computers really piss me off. There are some serious audio issues in W10 that are making Teamviewer my most used program any more. The user uses the troubleshoot function which says "No problem here sonny!" and the user doesn't believe me when I say ignore the troubleshooter. - some have become pissed even. So it's just easier to use Teamviewer to go in and fix it myself. 100 percent post fix I get a "Huh, you were right".

      Now I'm just wondering which Linux distribution I'm going to get excited about next, and happy about the ongoing trend in Linux gaming support. I've got a Windows 7 PC for gaming, and that's working just fine.

      7 on my Mac with bootcamp, a W10 machine with nothing on it but the software I have to run, and I really like Mint Cinnamon - evaluating Mate now - for desktops and decent laptops, and Ubuntu for my old Netbook. And Mint is plenty pretty enough as well.

      --
      The shepherds did so well protecting the flock that the sheep no longer believed that wolves existed.
    93. Re:No thanks by geminidomino · · Score: 1

      I'm still using gimp, it still works the same as in the 90s

      Did you stop updating at 2.6, too?

      The GIMP project isn't immune to this kind of dumbfuckery either - they decided to remove file conversion from the "save as" function, and require an explicit export command because "that's what professional users expect" (reality: "Professional" users use professional tools, which still behave as one would expect.)

      Their response to complaints: "Use something else, you're obviously an amateur."

    94. Re: No thanks by geminidomino · · Score: 1

      We have a real problem in our industry that UX is considered nothing more than UI.

      Having dealt with too many UX "professionals", I am comfortable saying that the real problem in our industry is that UX people don't understand the basic damn concepts of UI. "Discoverability" shows up pretty frequently in this thread, for good reason. "Consistency" is another one.

      Hell, half the time I end up scratching my head and wondering if the UX guy thinks a "Use Case" is a fancy new iPhone accessory.

    95. Re:No thanks by Anonymous Coward · · Score: 0

      I am actually sick of the HYPOCRISY of people like you. Mozilla copies Chrome because Chrome was cleaner and easier to use for normal people. Then people like you bitch about Firefox and say "we should use Chrome". Just frigging lame.

      If you were going to be productive, you would have suggested "forking" Firefox, but I think you are butt-hurt that you are now in the minority, and most people want Firefox's UI exactly as it is, just like Chrome, Safari and Edge.

    96. Re:No thanks by LateArthurDent · · Score: 1

      Why this change? It's not reasonably discoverable.

      As stupid as that reasoning is, that's the point.

      There's a fad among certain UI people that you shouldn't confuse users with options, and give them only what they need. The small number of people who need to do more stuff than the majority of people, should either not do what they want to, and adapt to what the interface presents you, or go through a painful process to figure out how to do it. The idea being that if you're computer savvy enough to do something different than the majority of users, you're computer savvy enough to google and go through the extra process. If it's easily discoverable, the non-computer savvy user will come across it and get confused / perform an action he didn't mean to and doesn't know how to do undo.

      I can't emphasize enough how stupid that is, but the gnome people have always suffered from it. I like their window manager a lot honestly, this is my one gripe. Options are good, people.

    97. Re:No thanks by medoc · · Score: 1

      Those who remember the command line, linux dweebs aside, are dead or retired. Correction: those who remember having nothing but a command line are dead or retired.

      Still alive, beg to differ. I'd even venture that there are some people who began with punchcards who are still around.

    98. Re:No thanks by Anonymous Coward · · Score: 0

      The common DOS users of the 80's and 90's who were aware of the simple fact that classic Mac users were "too dumb to use a command line" are not the typical contemporary Windows users that think "the command line doesn't exist anymore." Big changes were set in motion in the mid to late '90s with the rise of the consumer internet. Now all mainstream computer interfaces are made for idiots.

    99. Re:No thanks by Anonymous Coward · · Score: 0

      This is my experience as well. I even had some designer send me an article written by some apple design guru saying that folders within folders was an idea created by geeks for geeks. As if the idea of a taxonomy was created in the last twenty years. It was such utter crap. But the worst thing was that the designed didn't seem to want to spend a minute understanding who the audience was for our project, instead they kept trying to shoe horn us into the latest theme of the day in design lala land.

    100. Re:No thanks by Anonymous Coward · · Score: 0

      Wow! A Slashdot poster that is deeply familiar with the Devuan project but has never heard of Slackware or any of the BSDs. There's an opinion we should all take notice of!

    101. Re: No thanks by Anonymous Coward · · Score: 0

      Have you ever seen A/UX's Commando dialogs?

      They were an interesting idea and very helpful to me when I was learning command line options, but I think Apple realized that the GUI users weren't going to do command line options anyway, and the command line users preferred man pages to radio buttons!

    102. Re:No thanks by gustygolf · · Score: 1

      I reckon it might be Apple's influence. They have this feature where you "right click" by holding down Option when clicking the left mouse button. [1]

      I happen to think Apple's behaviour is very handy, especially on laptops. Right clicking on every track pad I've run across has been an ergonomic nightmare. (The bad part, of course, is that you have to have a hand on the keyboard.)

      It doesn't excuse GNOME's behaviour though (assuming what you say is true).

      [1] or "only mouse button", if you're one of those silly Apple-bashers.

      --
      "Slow Down Cowboy! It's been 58 minutes since you last successfully posted a comment" -- slashdot, driving users away.
    103. Re:No thanks by Anonymous Coward · · Score: 0

      I am willing to travel anywhere and punch anybody

      LOL! Look at the e-tough "badass". Are you also a former Marine Corps sniper with over 500 confirmed kills and an expert in MMA?

    104. Re:No thanks by Anonymous Coward · · Score: 0

      Except that Windows 10 is a free upgrade.

      Aside from all of the spyware and desktop integrated advertising you mean.

      It's only free if you don't care about your personal information, intellectual property, time or sanity. Oh and because it's a worse OS than its predecessors, it's technically a downgrade.

    105. Re:No thanks by Anonymous+Brave+Guy · · Score: 1

      So how is a flat design based on poorly chosen design principles, or a bad user experience?

      One problem that comes directly from the flat aspect is that there isn't enough variation to clearly identify the interactive aspects of a UI. A horizontal line could be a divider between separate content areas, marking off a heading from a lightly formatted list or table, or an editable text entry field. A filled rectangle could be a text field, a button, a notification message, or just some highlighted content. Numerous examples can be found of basic UI controls like radio buttons and check boxes where it is literally impossible to tell whether the current state is meant to be on or off unless you're already familiar with the convention they use, or sometimes even whether a group of such controls are mutually exclusive or not. Circular or rounded elements sometimes get introduced to distinguish some of these cases, but then those in turn have the same problem that there's no useful affordance in the presentation.

      A related problem with the lack of tools to distinguish different parts of a screen is that you often see large colour blocks used for backgrounds. These may themselves become distracting or, worse, clash horribly with the typical strong colours often used with flat designs. Alternatively, ever-increasing amounts of white space get introduced to separate different areas, resulting in an empty-looking UI with very poor information density.

      Then we get to the illustrations. In the absence of things like depth and texture, flat design icons tend to become pretty much line art and/or colour blocks. Line art is particularly popular because of icon fonts, which have problems of their own, but that's not strictly a flat design issue so I won't get into it here. What is a problem with either common style of flat design icons is that they can easily become so similar as to be hard to tell apart, again giving poor usability. How often have you see two or more very similar variations of straight/hooked/circular arrows, crosses, stars, plus signs, or other common icons in the same UI, which firstly did completely different things despite looking almost the same, and secondly didn't convey any particularly helpful indication of what they would do in at least one of those cases anyway? We could add some text to help clarify, but then the main tools we have available to indicate that the text and icon are related are proximity, lines, or background colour blocks, which have all the same problems I already mentioned.

      I could also get into how poor a lot of the typography and animations typically used with flat design tend to be, but again these aren't inherently a problem with flat design itself, so maybe a little off-topic here. It certainly would be fair to heavily criticise specific implementations of flat design from the likes of Microsoft and Apple on these grounds, though.

      That's just off the top of my head, but if you're interested in more, people a lot more eloquent than me have written much longer and more detailed critiques of why flat design is almost universally awful from a usability perspective. I'm sure your search engine of choice will turn up a few of the main ones if you'd like to read them.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    106. Re:No thanks by Anonymous+Brave+Guy · · Score: 1

      The buzzwords don't help, IMHO. Creating a UI has always been about more than mere cosmetic details. Good UI designers have considered interaction design and numerous other aspects since long before anyone invented terms like UX, never mind created any of those UX forums. UI work was never just about looks, in all the decades I've been doing it.

      However, as with anything, a lot of people who don't have the full set of related skills also invent new terms for what they do that emphasize the skills they do have and gloss over the gaps. Thus we get interaction designers, and UX evangelists, and usability researchers, and visual designers, and animation artists, and front-end developers. This isn't necessarily a criticism, BTW, because of course everyone has to start somewhere. However, it's also true that there are more experienced practitioners who really do have all of those skills and really can build a major UI with one person or perhaps a small team that is better than what a whole bunch of relatively inexperienced specialists would produce.

      Also as with anything, people invent new buzzwords to describe the same old stuff that good practitioners have done forever. Presumably they think it looks more impressive to clueless people on a CV or Powerpoint slide. Personally I find the whole UI vs. UX distinction to be completely artificial and unhelpful, but YMMV.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    107. Re:No thanks by Anonymous Coward · · Score: 0

      Mozilla put UI/UX people in charge of Firefox and destroyed the product

      mozilla doesn't have "ui/ux people", they have rape artists that swipe the look of chrome and put it on firefox..

    108. Re:No thanks by Anonymous Coward · · Score: 0

      Google's "material design" is amateurish garbage that is every bit as bad as Microsoft's Metro shit that it ripped off. I'm so sick of seeing sites and apps adopting that shit. Did all of the good graphics artists die off or something?

    109. Re:No thanks by Anonymous Coward · · Score: 0

      CLI makes simple tasks complicated and complex tasks possible.

      GUI makes simple tasks simple and complex tasks impossible.

    110. Re:No thanks by Anonymous Coward · · Score: 0

      Its so CBasso's aunt Tillie do not accidentally remove something off the panel...

    111. Re:No thanks by Half-pint+HAL · · Score: 1

      There's no doubt that some got goofy with it, but abandoning it is like throwing the bby out with the washwater..

      ++disagree

      Now the thing about processing icons cognitively. I don't really need to process icons. They are just what I use to access the programs I want. What I want from my desktop is something attractive to look at.

      Of course you have to process the icon cognitively -- how can you use the icon to access the program you want if you don't know what icon you're looking at?

      The point behind the move against skeuomorphism was that operating a computer is about working with abstractions, and the more realistic the operating environment becomes, the more you have to actively reason. Fluent computer use is symbolic in mature, even when there are spacial relations involved. UI elements are words, not physical controls.

      Now we are into an entirely different field of ambiguity. Since I find flat squares with a little text inside soul suckingly boring, and artless, I don't want to look at them. Others might find them beautiful. All a matter of taste.

      Well such flat squares have low iconicity, which is precisely what I was saying about many "flat" interfaces missing the point.

      --
      Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
    112. Re: No thanks by Anonymous Coward · · Score: 0

      Nah, GUI is better. I can batch process without having to remember arcane commandline parameters and see previews before modifying thousands of files in a GUI.

    113. Re:No thanks by Rakarra · · Score: 1

      No, speakers pretty much still look like speakers. Well.. we do have a lot of ultra-portable equipment around like our phones and tablets which have flat speakers. Those all sound like shit though. If you open up anything with a half-way decent sound and look inside a speaker is still a cone with a magnet on the end. Don't open your stuff up? Do you have a car? Can't you see the speakers from underneath every time you open your trunk?

      You're touching up against a bigger problem -- many, many people today are perfectly fine with with things that look and sound like shit. "I'll watch the new Star Wars on my phone! That won't degrade the viewing experience at all!"

    114. Re:No thanks by Anonymous Coward · · Score: 0

      It's not hypocrisy, it's logic. If Firefox is going to just be a cheap copy of Chrome, then you might as well use Chrome since Mozilla has now removed all reason to use Firefox.

    115. Re:No thanks by Anonymous Coward · · Score: 0

      > GUI makes simple tasks simple and complex tasks impossible.

      Ridiculous. There's nothing you can do with a command line that you can't do with a GUI.

      However, there are things you can do with scripts that you can't do with a GUI - at least not without implementing a kind of "graphical script."

    116. Re:No thanks by Aighearach · · Score: 1

      Right, when you keep it functional and don't make changes, the level of importance of the so-called "problems" ends up being that some people complain that a feature is given an extra line in a pull-down menu. Oh the horrors, instead of clicking one word in a menu, you click a different word in the same exact menu. This proves how awesome they do at not fiddle-faddling my interface to meet the whims of the silly. There are real reasons why some users like that feature; it communicates function to them. It doesn't harm me for it to be one way, or the other way.

      Reality: GIMP is a professional tool that anybody can use because it is Free Software. Their response to complaints is that they are serious professional users themselves, and they don't want to fiddle-faddle their software to pander to the masses. If you don't use it the way they use it, either write a plugin that changes it to your way, or quit whining. There are lots of options. That they don't care what you think is the feature that prevents them from making excess changes, because they're not new and not trying to make a name for themselves by changing what was there. It shows the real value in a long-term maintainer culture instead of "community driven" culture.

    117. Re:No thanks by Anonymous Coward · · Score: 0

      So what are you using gnome for? You could do that with dmenu years ago.

    118. Re:No thanks by Anonymous Coward · · Score: 0

      It's still better than back when we'd watch Star Wars on VHS on old crappy CRT TVs with a single shitty mono speaker. A modern phone is much higher resolution, has better colour and stereo speakers.

    119. Re:No thanks by Anonymous Coward · · Score: 0

      The problem with using icons is that they lose meaning over time. How many children today will recognize a receiver from an analog telephone? You can use that icon to imply it has to do with a phone, but modern phones don't use that design. Same with the 3.5 inch floppy disk icon for the Save function. When was the last time you saw a physical floppy disk?

      Nobody is saying the icons should never change.

      Okay, nobody but Jayne is saying the icons should never change.

      The point is that you shouldn't have to think about what an icon does once you've internalized it as a symbol. Anything that interferes with that "muscle memory" (changing the representation, making it blend into the background, animating or moving it, etc.) is counterproductive.

    120. Re:No thanks by thegarbz · · Score: 1

      One problem that comes directly from the flat aspect is that there isn't enough variation to clearly identify the interactive aspects of a UI.

      That is an implementation problem. It is quite simple to show what area is interactive i.e. based purely on colour.

      Numerous examples can be found of basic UI controls like radio buttons and check boxes where it is literally impossible to tell whether the current state is meant to be on or off unless you're already familiar with the convention they use

      That is a problem with your thought process. I look at a radio button from old windows XP era and my current flat designed Android and there is literally no difference other than an internal emboss on the background, and a specular highlight on the dot. It is still 100% identical in the way it displays, a circle that's empty when not selected, and a circle with a dot in it when selected. That is nothing to do with a flat UI design, and is something you need to go out of your way to screw up if that's your intention.

      What is a problem with either common style of flat design icons is that they can easily become so similar as to be hard to tell apart, again giving poor usability. How often have you see two or more very similar variations of straight/hooked/circular arrows, crosses, stars, plus signs, or other common icons in the same UI, which firstly did completely different things despite looking almost the same, and secondly didn't convey any particularly helpful indication of what they would do in at least one of those cases anyway?

      This I agree with but I can't in good faith attribute this to flat design as opposed to stupid idiots deciding the world runs on indecipherable icons. You don't need a flat UI to not have a damn clue what half of those god damn buttons in Firefox do. Sorry I get worked up about this. It is not a flat UI feature, it's luancy from people who should be taken out the back and put out of their misery so they can't fuck up computers for the rest of us. Ironically I think a good example of someone who didn't screw things up like this was Microsoft with Office 2013. But then they started adopting that shit in Windows 8 so there goes all hope that Microsoft still had someone with any brains working in their UI department. Also when the hell did 3 little bars turn into "menu".

      I am actually interested in more if you have them. I do agree with the flat design having difficulty separating content from control to some degree, especially with defaults chosen. I.e. the very first thing I need to do to make any new office install usable is set it to a dark theme so it separates the page, but once that is done I don't find the flat UI design to be much of a problem.

      I think a lot of the flack that the flat UI gets is due to the brain dead defaults in the colouring scheme used by some developers thinking they are being "clean".

    121. Re:No thanks by morgauxo · · Score: 1

      You had me until the speakers.

      The screens are pretty nice. Obviously there is no comparison to the big screen but the quality is better than most old CRT TVs. You might miss some detail though simply because it is too small to notice. I watch movies and tv shows on my cellphone all the time. So long as I am watching for the story and not for the effects it's just fine.

      But the sound...

      The sound of any cellphone is shit. Stereo? Even if you have a left and a right speaker in your cellphone there is no separation. They would have to be closer together than your ears are! Stereo does not work that way.

      Fortunately though watching stuff on a cellphone is almost universaly a solitary experience. Two people just aren't going to want to share such a small screen. So.. use headphones.

    122. Re:No thanks by Anonymous+Brave+Guy · · Score: 1

      It is quite simple to show what area is interactive i.e. based purely on colour.

      Up to a point, perhaps. But any guidance for a user that relies purely on colour for essential meaning is risky, for all the usual reasons: different colours have different connotations in different cultures, not everyone physically sees colours the same way, and so on. Also, even if you do adopt colour for this, it's tricky to establish a universal convention (which is helpful for usability) since different systems will have different colour schemes.

      Please consider that while the UI designer constrained to use flat design has to grapple with those issues, the UI designer with a wider range of tools available might be using completely different effects to distinguish a button and its extent, and has colour available for subtle cues like highlighting the main call to action or next step button, or adding a red or green tinge around dangerous or confirmation buttons.

      I look at a radio button from old windows XP era and my current flat designed Android and there is literally no difference other than an internal emboss on the background, and a specular highlight on the dot. It is still 100% identical in the way it displays, a circle that's empty when not selected, and a circle with a dot in it when selected.

      And as long as UIs stick with that widely used convention, going flat is fine. Unfortunately, lots of UIs don't.

      Take a look at the on/off toggles on recent iOS, for example, which are completely meaningless if you see them in isolation. There is no indication of which side means yes/on/true. In light of the ambiguities of using colour blocks as mentioned above, even that doesn't necessarily help much. To find out what's going on, the user needs to start activating things, which they might or might not want to do. Even how to toggle the control isn't immediately obvious, as it looks like a slider but in fact responds to a simple tap.

      At least those toggle sliders, while awfully designed in almost every way I can think of, have the virtue of being a standard on that platform and so something users will probably learn to recognise fairly quickly once they've seen it a few times. The random presentation of toggle controls that you see on a lot of web sites or over-stylised mobile apps doesn't even have that going for it.

      Also when the hell did 3 little bars turn into "menu".

      It didn't, and actual data from real users consistently shows the hamburger menu and its dotty or griddy variants underperforming. If you ever run into a designer who maintains that using a hamburger menu is a good idea, and who doesn't have a very clear argument for that in some very specific context, you can probably assume you're talking to someone who isn't very good.

      I do agree with the flat design having difficulty separating content from control to some degree, especially with defaults chosen.

      It's more than just the defaults though. Quite simply, flat design artificially and quite severely limits the range of tools available to the designer to convey meaning. Anything flat design can do well, you can also do well in other visual styles, and you've still got all those other options to use if you need more variation or just some subtle contrast to give an extra cue to the user. The opposite isn't -- and can't be -- true.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    123. Re:No thanks by Anonymous Coward · · Score: 0

      Over simplified and wrong.

      Command line is not necessarily a problem. It's a problem for non-technical people who just need an email client, word processor, spread sheet and web browser. UI was introduced to make usage easier and more approachable for those people.

      For *nix system administrators we regularly use command line ONLY. Obviously not on our desktops... but most *nix servers are primarily command line only. Additionally, for a seasoned administrator who is comfortable on the command line, it's usually faster and more effective than GUIs for administrative tasks. Pipes baby, pipes!

      Programmers outside of the MS world typically like command line as well. It's much easier to produce command line tools than it is to create GUI tools. And when you add in the benefit of easy scripting it's a no-brainer.

      As for us command-line gurus being dead or retired; I'm offended by your ignorance. My first computer usage was commodore 64 and I'm in my 30s so you are just way off with that one.

      The command line "problem" has not been solved. It's still around, heavily used by certain classes of users and it's not going anywhere.

    124. Re:No thanks by Anonymous Coward · · Score: 0

      From what I've seen and read a lot of newer UI/UX people are ignoring everything that the UI/UX people learned and built up over the last 20+ years. Instead of learning what works first and how to improve it, they inject their own ideas and follow what's popular. What we end up with is a "dark ages" of sorts of innovation where we take steps backwards and are stuck with it. I agree keep the old / ugly UI until we remember how to bring the past forward with us.

      I totally agree! When I look at Fedora 14 and what they've done to it since is sad. They moved their focus to anti-clutter of the desktop and put their efforts into going back to menus and sub-menus and more sub-menus. I felt like they wanted break usability of the GUI by lopping off the G from UI and drag us unwillingly back to the 90's. I've pretty much stopped using linux. Making excellent/solid code first should be the priority, make a UI that best fits it and then incrementally create better GUI's for it.

    125. Re:No thanks by Anonymous Coward · · Score: 0

      Command line is not necessarily a problem. It's a problem for non-technical people who just need an email client, word processor, spread sheet and web browser. UI was introduced to make usage easier and more approachable for those people.

      It's not that some people are "non-technical," it's that the command line takes time to learn, whereas with a well-designed GUI you can often start working right away, because the commands are right there in front of you for you to try.

      Learning a command line interface is like learning a language; you have to have it explained first and then commit it to memory so you know what to type. Often the commands are arcane, non-intuitive and finicky.

      If you read Apple's original Human Interface Guidelines, they talk about properties like discoverability, feedback, consistency and forgiveness - all of which make the GUI easier to learn and more pleasant to use.

    126. Re:No thanks by Rakarra · · Score: 1

      I am actually sick of the HYPOCRISY of people like you. Mozilla copies Chrome because Chrome was cleaner and easier to use for normal people.

      Most of Chrome's interface changes are not better (in just about any way), but Chrome was much lighter and faster than firefox. Much better at memory management as well. People were sick of Firefox's pokiness, slowness, and general instability, but the alternatives also sucked, so when Chrome came out and it was dazzlingly faster than Firefox was, people started to switch over.

      Mozilla, naturally, took away EXACTLY the wrong lessons from all of this; flailing and in a panic adding Chrome's interface without improving Firefox's reliability, CPU usage, memory footprint. Not surprisingly, the pace of users leaving Firefox accelerated even more.

    127. Re:No thanks by Anonymous Coward · · Score: 0

      Also when the hell did 3 little bars turn into "menu".

      That's at least as old as Windows 1.0, then mostly gone by Windows 3.0, though it persisted in many non-MS applications. Also, it appeared quite often in DOS text-windowed applications influenced by early Windows GUIs. Look to the upper-left corners of the windows/panels in the two linked examples.

      Everything old is new again.

      - T

    128. Re:No thanks by Anonymous Coward · · Score: 0

      It's even older than that!

      Nicknamed the "hambuger" icon, it goes all the way back to the Xerox Star.

    129. Re:No thanks by thegarbz · · Score: 1

      Thanks for that, it all makes a lot more sense now in that context and with those examples.

    130. Re:No thanks by Anonymous Coward · · Score: 0

      What? Timeline? MacOS (you mean like 1-8/9?) was cool? really? not that I remember in the real world anyway. As a bunch of others could point out as well, OS 1-8 were actually pretty messed up and ugly compared to what windows was doing at the same time. I had a 1998 iMac (blue and white, European)that ran OS8, what an ugly POS that was.

  2. No surprise by Anonymous Coward · · Score: 5, Insightful

    It's not a surprise that many of the larger open source projects lack professional UI/UX designers. These groups tend to become cliques where anyone who is not a programmer is seen as less than worthy. Who the hell wants to try to assist groups with attitudes like that? There are so many cases where professionalism is missing in the entire equation.

    Many programmers need to wake up and understand that it's their own staunch idealism that is driving people who could greatly improve things away.

    1. Re: No surprise by Anonymous Coward · · Score: 0

      Exactly. And it starts by not talking about the UI being perceived as ugly, but the UI being ugly.

    2. Re:No surprise by Anonymous Coward · · Score: 0

      It's not a surprise that many of the larger open source projects lack professional UI/UX designers. These groups tend to become cliques where anyone who is not a programmer is seen as less than worthy.

      That is because these larger projects frequently are popular, and attract a lot of users. Which means there are a big chunk of clueless noobs amongst them. Trying to rebut clueless noobs in a polite way is lots of work, especially when they swarm your mailing lists en masse.
      I maintain that a professional UI/UX designer realizes this, and manages to avoid sounding like a clueless noob, and will be a welcome extension to any group.

    3. Re:No surprise by angel'o'sphere · · Score: 1

      The problem with UI is less a design issue on 'how it looks' but more a design issue of the framework.
      GTK looks like a bastard between Motive, Sun OpenView and MS Foundation Classes. On API level as well as on look&feel. WxWindows e.g. is more or less an MS Foundation Classes clone.

      It is no wonder that programmers try to use a minimum of those 'APIs' to get 'stuff done'.

      Honestly: you don't need to be an expert about UI/UX to craft a working one, that looks good, too. Read a fucking book about it and be done with it.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    4. Re:No surprise by Hognoxious · · Score: 4, Insightful

      I maintain that a professional UI/UX designer doesn't exist. They're amateurs. Dabblers. Dilettantes. They're not much better than feng-shui mongers.

      In my day we had ergonomists and human factors people, with some actual basis in science.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    5. Re:No surprise by JoeMerchant · · Score: 1

      More and more of them are driving their designs with "big data" often gathered "in the cloud" - they'll still read their feng-shui training manuals under the covers with an (oh so stylish) itty bitty book light, but they'll be in your face with pie charts, graphs, and statistics to back up their arbitrary decrees.

    6. Re:No surprise by KGIII · · Score: 3, Insightful

      I maintain that open source is not, generally, ugly. I use LXDE in most cases - maybe Cinnamon. I like plain. I like knowing where stuff is when I go to look for it. I do change some colors but that's easy. It was fine the way it was and not ugly. I even make my own dock - now that's ugly.

      I like the older stuff. I don't need live tiles, I don't need fancy sliding things. I do like some transparency in a few things (like looking through the terminal to see the text behind it) but even my terminal is themed mostly like an old green screen TRS-80.

      I don't find it ugly at all. I find it just right. If I didn't, I'd change it.

      --
      "So long and thanks for all the fish."
    7. Re:No surprise by angel'o'sphere · · Score: 1
      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    8. Re:No surprise by DesignPsychology · · Score: 4, Informative

      Professional UI/UX designers do exist. We are ergonomists, and human factors people, with actual basis in science—and some of us used to work on open source projects. We don't anymore for other reasons other than we don't exist.

    9. Re:No surprise by NormalVisual · · Score: 2

      In my day we had ergonomists and human factors people, with some actual basis in science.

      This is where a lot of UI design falls down, I think. It's easy to make a UI look pretty. It's a different story when it comes to usability and actually streamlining whatever task the software is supposed to accomplish. So much time is spent on the visuals, and precious little on the flow.

      --
      Please stand clear of the doors, por favor mantenganse alejado de las puertas
    10. Re:No surprise by thegarbz · · Score: 1

      In my day we had ergonomists and human factors people, with some actual basis in science.

      I remember you day. It was a day of give the user every option all the time. Don't prioritise workloads, just make every thing your software do capable in the same number of menu clicks. Okay maybe not that bad (though some open source programs definitely are), but really there should exist a happy medium between the old way and the modern way.

    11. Re:No surprise by Anonymous Coward · · Score: 0

      At least the start menu in Cinnamon looks quite amateurish. :)

    12. Re:No surprise by KGIII · · Score: 1

      I'd agree with amateurish but I'd not agree that it was ugly. I'd say it's not my preference but I could live with it. (I do like it *more* with a bit of theming.)

      This isn't as nice as it *could* be but:
      http://i.imgur.com/DgpeDjN.png

      Note: Most of that stuff is normally full-screen. I made them smaller so that you can see a few examples.

      That's the desktop that I'm logged into, via VNC, right now. I'm actually only using a Live USB environment, locally, so there's no need to share that as it is pretty stock.

      The top-most (maybe kind of ugly, I've not yet changed the color to match the newly applied background) bar is a "dock" that I added myself simply by making and styling an extra panel, positioning it, and making it only appear when I mouse-over the top-most part of the screen. It's clean, light, and pretty speedy on modern hardware.

      That was not with a lot of work and it could still be a bit more aesthetically pleasing but I'm comfortable with it and don't find it ugly. I'm not a Microsoft hater or anything, by the way, I just liked the look of the penguin and the colors were nice enough to be able to use transparency comfortably. I've shown others similar screen-shots and they were happy enough to tell me that it looked surprisingly good to them.

      That's an example of something that I don't find to be ugly. I find it utilitarian, easy to look at, easy to navigate, and familiar. Familiarity has a bit important to me. I can (and do) accept change but I prefer familiar - I picked what is familiar because it matches my workflow best.

      Would you find that ugly and, if so, why? Beauty is (usually) in the eye of the beholder. Of course, I've fought a Beholder and they're not so very nice!

      --
      "So long and thanks for all the fish."
    13. Re:No surprise by Merk42 · · Score: 1

      UI/UX often is done by getting information about how users use the current version.
      Then one or more redesigns are done with that in mind.
      They are then tested by asking the users to go through the redesign (wireframe/paper) and/or giving one group of users a new design and one group of users the existing (control).
      You know, the same thing as the Scientific Method

      Just because you personaly don't like the results, doesn't mean the process was flawed.

    14. Re:No surprise by Anonymous Coward · · Score: 0

      To be fair to feng-shui it uses named patterns that describe proper layout and codify known problems both macro an micro.

      "Three dragon come down from mountain" == building areas around the mountain should avoid flood, avalanche and land slide risk.

      There are others, like building at a tee junction is risky when vehicle breaks fails, shelves above a door often results in stuff falling on your head etc.

      I can't say that new UI/UX is anywhere near as well thought out.

    15. Re:No surprise by MrKaos · · Score: 1

      I maintain that a professional UI/UX designer doesn't exist. They're amateurs. Dabblers. Dilettantes. They're not much better than feng-shui mongers.

      Indeed. I always thought of UI testing as another skill in the toolkit. Improving it was part of the user *acceptance* testing. I think implementing the domain design is much more challenging than what was going to be hooked up to my controllers. The UI testing was signalling the end nearing of a project. We design the tests and usually delegate it while focused on issues critical for delivery.

      If someone said there was a specialist UI/UX designer I would wonder what I could learn that I wasn't already doing. Maybe I'm missing something.

      In my day we had ergonomists and human factors people, with some actual basis in science.

      I don't know if it's what you experienced but during UAT, we recorded using cameras on the screen, face, keyboard and mouse of the users testing the software and then gave them a list of tasks to perform. You could then see the expression on their face and what they were doing that helped figure out how to resolve UI issues. I thought it was a pragmatic approach to UI design that the users could own, after all they would be stuck with it, not me. I see UI design as another thing that went sometime with the domain being implemented. Great if I can get users testing as soon as possible.

      UI design is an important thing amongst a lot of important things, some of which are more important, most of which are a lot more difficult.

      --
      My ism, it's full of beliefs.
    16. Re:No surprise by trawg · · Score: 1

      Reminder that this Dilbert exists:

      http://dilbert.com/strip/2014-...

    17. Re:No surprise by Anonymous Coward · · Score: 0

      Also this one: http://dilbert.com/strip/1994-09-30

      Interesting side note - I'm using a newer MacBook, and the URL in the location bar just said "dilbert.com" until I selected it to copy the URL, then I could actually see the whole thing.

      Safari now hides the URL of the page you are looking at by default because "URLs are ugly!" I wonder which UI/UX "genius" came up with that brilliant idea.

    18. Re: No surprise by Anonymous Coward · · Score: 0

      There isn't a damn bit of difference between those statements, other than who the observer is.

  3. Sigh... by ledow · · Score: 5, Funny

    Maybe he should get his employer (Adobe) to get rid of that shitty sidebar that only disappears if you click the word Tools (despite no indication that's what's active) and which comes back every time you restart Acrobat Reader.

    No to mention the billion-and-one things that can pop over the top of your PDF. Or the services, scheduled tasks, taskbar icons, startup entries, etc. that are recreated all the fucking time even when you disable them and tell it not to update. Or the horrendous options dialogs that hide all the options.

    People who live in glass houses...

    1. Re:Sigh... by 93+Escort+Wagon · · Score: 1

      Yeah, I reacted similarly. Not that it's the fault of this particular individual, as far as I know, but - when I think about good UI and/or UX, I tend to think about the opposite of my way-too-frequent experiences with Adobe software.

      I'm also trying to think what Adobe has actually originated versus what they've absorbed. The tools which are now part of the Creative Suite were already a bloated mess when Macromedia still existed... but Adobe, somehow, made them worse.

      --
      #DeleteChrome
    2. Re:Sigh... by Anonymous Coward · · Score: 0

      This is so true. The Adobe is a prime example of UI/UX designer driven asylum. Only a UX designer would create a installer, which deletes itself, even if the installation failed. Or throw any usability principle to away and replace them with a shiny Adobe Reader DC, which is now a completely useless PDF reader.

    3. Re:Sigh... by Hognoxious · · Score: 1

      Yeah, I reacted similarly. Not that it's the fault of this particular individual, as far as I know

      Have you looked at his blog? I'd say that beyond reasonable doubt it probably is.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    4. Re:Sigh... by Zumbs · · Score: 1

      Only a UX designer would [snip] throw any usability principle to away and replace them with a shiny Adobe Reader DC

      One of the worst changes in the new UI for Adobe Reader DC is that a significant part of the UI is now *white*, causing it to lead my eyes away from the document that I am reading to the bloody UI. One should think that UI designers actually had taken the time to investigate the results of some 30 (40?) years of research into graphical UIs. One result that stuck in my mind is that you should design your UI to sink into the background while the actual task of the user should be highlighted. Earlier versions of Adobe Reader managed this by having a gray background for the UI so that the (typically white) document would stand out.

      UI design and implementation is such an important part of making a useful program that it just baffles my mind that Adobe and others hire UI designers that don't seem to know what the hell they are doing. I suspect that Garth Braithwaite is looking to get the people who do know what they are doing into Open Source UI design, which would be a good thing for all of us.

      --
      The truth may be out there, but lies are inside your head
    5. Re:Sigh... by Anonymous Coward · · Score: 0

      Amen bruthah SAY IT!!

      The dead last person on earth to listen to about UI/UX is someone who works at frickin Adobe.

    6. Re:Sigh... by jedidiah · · Score: 0

      We're talking about the whining of an another Adobe LOSER? Fuck em. They're all lazy ass morons.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    7. Re:Sigh... by Anonymous Coward · · Score: 0

      I agree. The designers or management believe that want people to use the applications as themselves. In reality, most people use applications to actually try to do produce or consume something with them and the actual content is the main thing, not the huge and obtrusive UI around it.

    8. Re:Sigh... by Anonymous Coward · · Score: 0

      They have finally added a fix for that "feature."

      1. Open a PDF
      2. Go to Edit > Preferences (or press Ctrl+K)
      3. Click on “Documents” in the Categories column
      4. Uncheck “Open tools pane for each document”
      5. Reboot at your convenience (The fix won’t take effect until you reboot)

      After doing this, it will remember the Tools Pane's last state (open or closed) whenever you close a PDF.

    9. Re:Sigh... by iampiti · · Score: 1

      But hey, we've got to make the application look modern that is: have the same mobile-inspired, mostly-filled-with-whitespace-and-large-letters UI everyone else has.
      Sensible UIs? That's so passé...

  4. Some projects don't want better UX by Anonymous Coward · · Score: 0

    No matter how much users want it.

  5. A bit rich coming from Adobe by Anonymous Coward · · Score: 0

    Perhaps he should spend his time working on the Photoshop / Illustrator UI which I find totally pants. http://adobegripes.tumblr.com/

  6. I agree to a point by Anonymous Coward · · Score: 0, Interesting

    I think some open source projects lack refinement in the user interface. Some of that I think comes from the people working with the projects. Sometimes I think interface polish is not a important focus and its much more about function. But let's also look at recent Windows UI and OS X. I think in general Windows 10 is ugly, and OS X has done little to change their user interface in OS X significantly in a long time. I do not count changes in fonts or adding small incremental changes as being any improvement. I also think this is why a lot of Windows users still like Windows 7 over everything else. Because when you have to look at the screen for hours, its nice to have a user interface that is easy on the eyes. I actually think Windows 10 is a big step back in ugly.

    1. Re: I agree to a point by Anonymous Coward · · Score: 1

      UX/UI generally deals with the visual functionality and workflow. If something is "ugly", that's a visual design issue, not UX/UI. Just because you don't like how something looks doesn't mean it has bad UX/UI.

  7. Gnome 3 by Anonymous Coward · · Score: 4, Insightful

    One of the largest contributing factors is the lack of professional designers contributing to open source projects

    How about that, he wants someone to pay him to fuck up other people's projects and wants to browbeat those people into letting him fuck up their projects by saying they need professional design.

    "open source is ugly, let's change things" is what turned Gnome 2, the best desktop environment of its day, into Gnome 3, which no one who has a choice uses.

    "professional designers" can go to hell.

    1. Re:Gnome 3 by SumDog · · Score: 1

      I was thinking of Gnome 3 in this regard.

      Also, they mention OSS projects are "ugly" but...did I miss in the article where they mention specific examples? I mean all GTK stuff looks ugly if you don't have a theme engine installed. Gtk3 widgets are the opposite, where they tried to be pretty by default and ended up being fucking ugly and useless.

    2. Re: Gnome 3 by Anonymous Coward · · Score: 0

      GTK+ has always been an awful toolkit. It was clearly inspired by Motif, but came about well after it became apparent that Motif's approach was outdated. Qt, on the other hand, has always been a great toolkit.

    3. Re:Gnome 3 by JoeMerchant · · Score: 1

      Isn't Unity a fairly styled / stylish environment? Or, is it still "ugly" because it hasn't completely transformed itself into a tablet full of quivering icons yet?

    4. Re:Gnome 3 by spauldo · · Score: 2

      That process didn't start with GNOME 3. GNOME 2 is a result of the exact same thing. And I'll enthusiastically disagree with your assessment that it was the "best desktop environment of its day." Maybe it was great if you were coming from Windows, but coming from earlier versions of GNOME or from other UNIX DEs, it was lackluster at best.

      Sun provided UX people for GNOME because it wanted to ditch CDE (ironically, right after it had switched to it from OpenLook). The Sun people came in and said, "fuck the power users, let's make things easy!" Options were considered confusing and omitted. The traditional UNIX workflow was replaced with a very Windows-like workflow. This lives on today in MATE - if you compare the standard Windows workflow with MATE, it's basically the same.

      Metacity is the perfect example here. It's the most brain-dead, unconfigurable window manager ever. It's less configurable than TWM. Thanks, GNOME, no, I don't want to be productive, what a silly idea! The first official WM for GNOME was Enlightenment, which was all kinds of configurable, and then Saw[mill|fish] (which I've been told was very configurable, although I didn't know LISP at the time so I never found out for myself). Going to Metacity was pretty much par for the course and indicative of their "options are evil" mentality.

      Those of us who started using GNOME back in the 0.x days watched our beloved features go away. Some adapted. Some, like me, ditched GNOME as a DE and ran a mixture of various software, including GNOME and KDE apps, and put up with the times when stuff just didn't work right. I eventually switched to KDE, since KDM can do most of what I wanted FVWM for and supports something closer to the traditional UNIX desktop workflow, but I can see where the UX people have been "innovating" there too.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    5. Re:Gnome 3 by Anonymous Coward · · Score: 0

      Unity still has too many colors. It must be modernized with light gray text over white background. And the fonts must be huge, after all, we all use our desktops with touchscreen. Bonus points are given if the user does not get any visual clue, which parts of UI are clickable and if some features of it are hidden to be uncovered only if mouse pointer is moved to some random location.

    6. Re:Gnome 3 by Anonymous Coward · · Score: 0

      Gnome has absolutely no business, in any of it's incarnations, of being called "good" by anyone at any point in time.

      Everything about gnome, gdk, gtk, is bad news. Very, very, very bad news.

      It always has been, and likely always will be (judging by the fact that I tried to submit a fix to a decades old bug in it, and was promptly told to fuck off)

    7. Re:Gnome 3 by Anonymous Coward · · Score: 0

      In MATE, it's easy to choose an alternative WM now. AFAIR you don't even need to re-login.

    8. Re:Gnome 3 by drinkypoo · · Score: 1

      GNOME 2 is a result of the exact same thing. And I'll enthusiastically disagree with your assessment that it was the "best desktop environment of its day." Maybe it was great if you were coming from Windows, but coming from earlier versions of GNOME or from other UNIX DEs, it was lackluster at best.

      Wait, what? I've used both earlier versions of GNOME and other Unix DEs, and I disagree uncategorically with your statement.

      Sun provided UX people for GNOME because it wanted to ditch CDE (ironically, right after it had switched to it from OpenLook).

      Yes, that's right. Nobody liked CDE, and nobody liked Motif. This hot-shit GTK+ thing was taking the FOSS world by storm, and by the way there was this other Qt thing, and projects to make each one able to use the other's theme engine to draw its own GUI elements. And statistically nobody was using Motif, and most of the people who were either didn't really want to do Unix software (Adobe) or were moving away from it (everyone else) and so they settled on GNOME, as the most familiar.

      OpenLook was never particularly discoverable and the coolest feature (tear-off menus) lacked management, it was too easy to tear off menus and lose them forever. CDE was fine as such things go, very Windows-like, but the panel was goofy and bulky. NeXT's Dock made it look like a big stinky turd. GNOME's panel was sleek and small by comparison to either.

      The Sun people came in and said, "fuck the power users, let's make things easy!" Options were considered confusing and omitted. The traditional UNIX workflow was replaced with a very Windows-like workflow. This lives on today in MATE - if you compare the standard Windows workflow with MATE, it's basically the same.

      How does this differ from GNOME 1? IIRC, it really doesn't. Things looked very much the same. But by contrast, what I personally did with GNOME 2 was to not even use the panel, and to augment it with compiz. I was able to build an OSX-like interface without any of the drawbacks and with complete configurability, with the eye candy features used primarily for functionality — except that I used the emerald window decorator to have pretty, translucent window decorations. Even that is functional; you can see things happen through it, like windows vanishing or updating. emerald isn't getting updated any more, nor avant-window-navigator, or I'd probably be doing that still.

      The first official WM for GNOME was Enlightenment, which was all kinds of configurable

      Except it was a massive bitch to configure it, and the documentation was shit. I have no idea if it's better now in either regard, because why would I bother.

      Those of us who started using GNOME back in the 0.x days watched our beloved features go away.

      So what's missing from say 2.x that was in 0.x?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Gnome 3 by Anonymous Coward · · Score: 0

      i guess it looks alright. Trying to use it is a fucking nightmare, though. First thing everyone does when faced with Unity, is google "How do I get rid of Unity?"

    10. Re:Gnome 3 by spauldo · · Score: 1

      It sounds like you don't use GNOME like it is intended either. Sure, you get what you want - for the most part - if you go without the panel and use compiz and build an OSX-like interface, etc. etc.

      At that point, you're not running GNOME. You're using GNOME components.

      As far as what's missing, it was like I said: configurability. There was a constant push to remove options from settings panels, and a constant push towards a Windows-like workflow. That's great for people coming from Windows. It sucks for people like me, who actually liked OpenLook, FVWM, and Afterstep, and whose first actions upon a new install is to put a launch icon for xterm and add a grid of desktops with edge flipping.

      It's been fifteen years, I can't give you specifics. The mailing lists should still be there, and you'll find people on them (including myself) complaining about the process. My point was merely that people have been complaining about UX designers mucking about with GNOME for long before 3.x.

      Oh, and I like Motif, too, in a strange sort of way. Want to talk about removal of configrability, just ask where X resources went.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    11. Re:Gnome 3 by drinkypoo · · Score: 1

      It sounds like you don't use GNOME like it is intended either. Sure, you get what you want - for the most part - if you go without the panel and use compiz and build an OSX-like interface, etc. etc.

      No, that's how I chose to use the GNOME desktop. I still used the gnome session manager, and nautilus, so I was categorically still using GNOME. I simply chose to sub out the panel.

      As far as what's missing, it was like I said: configurability.

      Yes, I used that configurability. It would let you configure it to use an alternate panel. That's what I did.

      It's been fifteen years, I can't give you specifics. The mailing lists should still be there, and you'll find people on them (including myself) complaining about the process.

      If you can't remember, it's not important. Stealing the window widgets, that's important. Whatever you forgot, not important.

      Oh, and I like Motif, too, in a strange sort of way. Want to talk about removal of configrability, just ask where X resources went.

      You like something about it. You don't like Motif. And on the subject of XResources and GTK, they were intentionally omitted because in practice they were little used and just increased the PITA factor. They were underused before, if you don't make them mandatory people don't implement them or don't implement them well. It was better to let them go away.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    12. Re:Gnome 3 by spitzak · · Score: 1

      Gnome 2 disabled the ability that existed in almost all earlier X11 window managers to work with overlapping windows, by forcing you to raise windows on click.

      There was an option in gconf to turn off raise-on-click, but for some reason it also disabled the ability of a program to raise its *own* windows. This effectively makes the option useless. The obvious reason is because the designers did not want that, because it might confuse those poor Windows users (Windows also forces clicks to raise windows). The gconf included a long comment about how absolutely logical and necessary this was and how any program relying on the ability to *decide* whether to raise on click was "broken". Surely one of the biggest pieces of bullshit I have seen in a long time. And these people are still working on this, making it worse and worse.

    13. Re:Gnome 3 by spitzak · · Score: 1

      So what's missing from say 2.x that was in 0.x?

      Ability to work on a window without raising it to the top.

    14. Re:Gnome 3 by Rakarra · · Score: 1

      How does this differ from GNOME 1? IIRC, it really doesn't. Things looked very much the same. But by contrast, what I personally did with GNOME 2 was to not even use the panel, and to augment it with compiz.

      I vaguely remember being disappointed with the Gnome 1 -> 2 transition when power user options were removed, most especially the keybindings for the window manager. "Oh, so I can't set a hotkey to toggle window title bars/decorations at will anymore? That just... can't be done?" Many, many things along that line. Over time, some stuff has gotten added back in, and other parts of the UI, like Nautilus and gvfs are far more feature-rich in later Gnome2 incarnations, and I'm pretty happy with Gnome2 in, say, RHEL6.

      Gnome3, however.. what a disaster. I'm not sure where to begin, not the least which was that Red Hat rushed it as the default interface in Fedora way WAAAY too early when it was very unstable and feature-poor. What a horrible intro to Gnome3! It's only now achieving some sort of stability and flexibility. Unfortunately, none of that stuff is going to make it to RHEL7. They rushed Gnome3 into RHEL as well.

  8. "weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 5, Insightful

    I edit code using emacs. It would make any "UX designer" throw up. To the clueless, it's "user experience" looks horrifically bad, especially how I have mine configured up old-school without menus or GUI buttons. Just text and a mode line.

    But you know what? I can utterly, totally, annihilate people using better "UX quality" text editors when it comes to heavy duty text editing. I've had people literally gasp out loud watching what can be done.

    I'll make a similar claim for other SW I've used, such as CAD systems, which are all but incomprehensible for novices but let experts work magic.

    People mistake "ease of newbies being able to do something" with "expert usability". These are not the same. Most of the time, UX designers optimize for the first thing at the expense of the second. It's one thing if you can manage to get both, and I'm not saying that's impossible or that it never happens. But most of the time when UX experts get their hands on something, actual usability for experts is sacrificed on the alter of hand-holding for novices.

    That's even becoming true of desktops now. Configurability is the enemy: it's too confusing, and we must not have anything which might require thought, no matter how useful it is. Computing is trending towards playskool-levels of being dumbed down.

    1. Re:"weak" UX often found w/ the most powerful SW by Hognoxious · · Score: 2

      People mistake "ease of newbies being able to do something" with "expert usability".

      They do. They also confuse looking good with working well.

      I'd say the latter is actually the bigger problem. Flat == shit.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    2. Re:"weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      Only if you're buying proprietary stuff, which means anyways you're getting fucked..

      On Linux, I installed Ubuntu. Unity got too CPU-intensive for my L4D2 gaming on Steam, so I installed Lubuntu and use XFCE on top of that again, since Lubunu didn't work. For other people, the default might be OK. But, with freedom, I can screw up my own systems the way I want it.
      I, like Linus, really just want it to work out-of-the-box though!

      We get what we choose.

    3. Re:"weak" UX often found w/ the most powerful SW by iampiti · · Score: 2
      Totally agree. You need look no further than Windows 10:
      • Edge, the new, wonderful browser that Microsoft wants you to use has a mobile UI even on a desktop, and has very few options
      • Microsoft have stated that all the configuration will be moved to the new "Settings" app and the Control Panel will be removed

      One can imagine this trend will continue until Windows 10 for desktops is more or less the same as the one for mobiles.
      I'm not against of makings things easy for novices but not at the cost of making them more difficult, cumbersome for power users

    4. Re:"weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      I've had people literally gasp out loud watching what can be done.

      And what exactly was it that made them do that?

    5. Re:"weak" UX often found w/ the most powerful SW by umafuckit · · Score: 1

      But you know what? I can utterly, totally, annihilate people using better "UX quality" text editors when it comes to heavy duty text editing. I've had people literally gasp out loud watching what can be done.

      Can you make a screen cast with stuff like this and explain it? I'm not asking to be a dick, I'm genuinely interested.

    6. Re:"weak" UX often found w/ the most powerful SW by bidule · · Score: 1

      If the default interface is standard and efficient, you don't need to configure everything. There's nothing more hateful than using another person's computer and being unable to do anything because they configured everything away and none of it fits your own configuring away. I had to force my gitconfig on everyone at the office to get around this.

      That's the problem with many Open Source UX, they apply their vi/emacs knowledge and force the user to adapt to the program instead of adapting the program to their use. If it doesn't work out-of-the-box, I'll find something else that does. Just look at Dwarf Fortress with its 3 ways to move the cursor, for instance.

      There's also the reverse problem, there are many cases where you'd like to know which command-line options matches that checkbox because it's much easier to change the config from the cli than to roam around the variable UI of the Mac / Win / Linux versions.

      --
      ID: the nose did not occur naturally, how would we wear glasses otherwise? (apologies to Voltaire)
    7. Re: "weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      You should check out vim. Its far better ux wise than emacs.

    8. Re:"weak" UX often found w/ the most powerful SW by brantondaveperson · · Score: 2

      Weren't you listening? It was 'Heavy Duty Text Editing'. Heavy Duty man. Not your grandfather's text editing, that's for sure. Probably such heavy duty actions as multiple search and replace, or multiple paste buffers, or search-and-replace while pasting, or regular expression search and replace in multiple paste buffers while simultaneously - oh I don't know - reading your email or something.

      Having a clever command line style interface to your text editor, which really amounts to good keyboard shortcuts, doesn't prevent the existence of an intelligent UX (or UI plus workflow plus underlying concepts, which is kind of what UX is short for).

      Computing isn't being dumbed down, you can do more today than you ever could. And people are still developing emacs, if that happens to be your bag.

    9. Re:"weak" UX often found w/ the most powerful SW by war4peace · · Score: 1

      So why not have both?
      To me, the best UX is the one which lets you point-n-click as well as use a hotkey/shortcut for each button or command.
      people gotta start somewhere, and people nowadays start with point-n-click, simply because they don't know all the hotkeys. If the point-n-click side is lacking, they will give up and go to the more friendly competitor - which might be worse from a functionality point of view but newbie-friendly.
      You also nee to remember that most users never pass amateur-level. All they need is the basics with the occasional foray into a more specific functionality, which they might need twice a year.

      --
      ...gis sdrawkcab (usually not responding to ACs; don't bother posting as AC)
    10. Re:"weak" UX often found w/ the most powerful SW by OhPlz · · Score: 1

      I'm assuming it's a porn reference.

    11. Re:"weak" UX often found w/ the most powerful SW by sysrammer · · Score: 1

      I've had people literally gasp out loud watching what can be done.

      And what exactly was it that made them do that?

      He created an ASCII picture of a beautiful nude using only one hand.

      --
      His ignorance covered the whole earth like a blanket, and there was hardly a hole in it anywhere. - Mark Twain
    12. Re:"weak" UX often found w/ the most powerful SW by chipschap · · Score: 1

      Can you make a screen cast with stuff like this and explain it?

      If I understand you correctly, yes. Emacs has good options for creating excellent presentation material. Not "slick" in the extreme way that can be done with PowerPoint, but presentations that communicate the material effectively, rather than just being overly showy (which, I think, distracts from the material).

      But I need to clarify two points.

      1) Emacs doesn't do things like, for instance, edit movies or do Disney-style animation. You will always need specialized tools when you reach some point.

      2) While Emacs can help make great presentations (such as with the LaTex Beamer class), there is a serious learning curve. I won't deny that this will eliminate 90%, maybe even 99%, of potential users. If you want something simple, this isn't it.

      On the other hand, if you do go to the trouble to get good at Emacs[1], you can get an amazing amount of work done with it.

      [1] YMMV but I would say a year of experience is needed to reach an expert level. Sounds like a long, long time. But how much experience do you need to be good at, say, golf? Or French (for an English speaker)? Some things take time but are worth it.

    13. Re:"weak" UX often found w/ the most powerful SW by JoeMerchant · · Score: 1

      I used to work in customized environments (text editors, Autocad, etc.) and it did make my work faster - on my desk.

      Thing is, I don't only work on my desk, I also work with other people on their desks, especially when they are working with my code/designs/documents/whatever. So, in those environments, it's nice to have the same interface as them so you can tell them quickly and easily how to get around in your stuff - otherwise you stand there like a moron mumbling "if I were back on my machine I could do this in half a second..."

    14. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 1

      This is what is wrong with open source! It mistakes good design with new-fangled, fewer features, and inefficient. And yet, I find that is only true of open source, not professional applications. Adding more features beyond 128 characters of ASCII, doesn't make programs suck (just the opposite).

      I've got a guy in the office just like you, only vim.

      You know what? He is only slightly faster than somebody with good sublime skills, and utterly lost when skills require him to do something more than text process on the command line. I totally run circles around him when it comes to weaving together CAD, graphics, 3D, presentations, vector work, and deep-level debugging in graphical debuggers. The other day I put together a presentation that was an amalgam of 3D cad, mechanical CAD, architectural CAD, photoshop, illustrator, graphical and 3D editors, video editing, and 2D animation. While his text processing is a bit deeper than mine, it doesn't make him very much more efficient at coding, cause that is bandwidth limited by thinking, yet his skill set is sooo much narrower.

      The "my command line is all I need" argument was lost 30 years ago. Text is just one of many things a GUI handles. But the thing a GUI does is provide a consistent framework that allows you to use another programs bringing 70% of your skill base to a new application, with little reboot time. Try moving vim guys to emac, and vice versa.

    15. Re:"weak" UX often found w/ the most powerful SW by JustAnotherOldGuy · · Score: 1

      I'd say the latter is actually the bigger problem. Flat == shit.

      Agreed.

      I'm forced to use Windows 10 at work and its flat design is infuriating. Sometimes it's hard to tell where one window ends or overlaps another. A little shadowing or texture or ridge or any-fucking-thing would help, but oh no, can't have that. We gotta make it look like some jackass from PlaySkool(r) designed the interface.

      --
      Just cruising through this digital world at 33 1/3 rpm...
    16. Re:"weak" UX often found w/ the most powerful SW by JoeMerchant · · Score: 1

      In 1991, there was a text editor in DOS called Brief, by a company named Underware. It was fast, it was powerful, nobody has done "block copy and paste" (where you can select a rectangle of text and insert it anywhere in the middle of lines) since then in a way that was so easy to use - it was all done with one modifier key commands like Alt-G Ctrl-V etc. Newer interfaces are using more and more modifier keys, and combining it with mouse manipulation and they just suck by comparison.

    17. Re: "weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      That's a damned shame. You should have gotten at least one or two bites from that. It was timely and actually a pretty good effort. It's definitely in the list of classics and you wielded it well. Maybe it's Sunday so they're just not biting.

    18. Re:"weak" UX often found w/ the most powerful SW by Zumbs · · Score: 1

      Not being a W10 user ... but doesn't the active window have a color that is different from the inactive windows? Or is the problem actually the inactive windows?

      --
      The truth may be out there, but lies are inside your head
    19. Re:"weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      Computing is trending towards playskool-levels of being dumbed down.

      No it is the things that you shouldn't have to worry about being removed in products designed for the majority. You can bitch and moan all you like that an iPad doesn't have the ability to manually configure its network interface or that Windows doesn't give you a setting to use your own HTML layout engine for the OS UI or that games consoles don't give you the settings to change AA/AF and shadow sampling settings ... but that is because in these cases computing is being simplified . This isnt about removing all configurability from everything but about eliminating the needless complexity from systems targeted at people who do not need that complexity. Many systems (CAD for example) do need that complexity yet there are often simplified versions that omit some functionality in favor of simplification too.

    20. Re:"weak" UX often found w/ the most powerful SW by brantondaveperson · · Score: 1

      Brief, by a company named Underware.

      Awesome.

      block copy and paste

      Visual Studio does a nice job with Alt+Drag. Or it might be the Visual Assist plugin, I'm not totally sure.

    21. Re:"weak" UX often found w/ the most powerful SW by dbIII · · Score: 1

      The other day I put together a presentation

      Maybe the text editor guy's job is not putting together presentations :)
      You have not told us enough to make your point and for all we know the guys job could be 99.9% manipulating text. High school kids can do better presentations than I but that's not my job apart from maybe an hour every second or third year.

      Try moving vim guys to emac, and vice versa.

      Why? Both are are cross-platform, free and can be downloaded and installed in less than five minutes. That's like forcing an airbrush artist to use a paintbrush just for the hell of it.

    22. Re:"weak" UX often found w/ the most powerful SW by JustAnotherOldGuy · · Score: 1

      Not being a W10 user ... but doesn't the active window have a color that is different from the inactive windows? Or is the problem actually the inactive windows?

      It's both, actually. The difference between an inactive or background window and a foreground window is often difficult to differentiate.

      --
      Just cruising through this digital world at 33 1/3 rpm...
    23. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 1

      i expect people in my team to be a broad as possible. If all you can do in manipulate text, it limits your potential, your perspective, your creativity, and the company

    24. Re:"weak" UX often found w/ the most powerful SW by dbIII · · Score: 1

      Are you sure that you are not expecting the CS guy to instantly come up to the same standard as a professional mechanical engineer with hundreds of hours on the drawing board and CAD software? Teach a few classes and you get a bit of perspective that your assumptions about what a default background is are probably wrong. Even being able to think well enough in 3D to draft or use CAD takes people a bit of time, you probably just can't remember because it was so long ago and you've never had to teach it to anyone else.

    25. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 1

      I don't work for a big company where everybody is siloed into narrow tasks. I want everybody to contribute to their upmost potential. I understand I may be one of the broadest engineers around, but that is a requirement in a startup environment. And I really hate when people say, it is "not my job", cause all problems are just problems not software, hardware, mechanical, architectural, UI/UX problems.

      If your toolbox is big enough, you can pick the right way to address the problem, not just the one you know.

    26. Re:"weak" UX often found w/ the most powerful SW by dbIII · · Score: 1

      Step back a bit. You'll see that your example has nothing to do with the software but has everything to do with the experience of the person using it in areas that are totally irrelevant to the software that they habitually use.
      You may as well have said that Serena Williams is not at a professional level at chess (I'm guessing) for just as irrelevant an example.

      Why should we expect text editing experience to apply in 3D drafting anyway? While I do use the text commands in AutoCAD quite a bit, there's still very little between even that use and a text editor.

    27. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 1

      If all you want is coding monkeys, then you are right.

      If you are doing real product development that comprises UI/UX, software, hardware, industrial design, PCB design, 3D mechanicals... like most products, then you are wrong.

    28. Re:"weak" UX often found w/ the most powerful SW by spauldo · · Score: 1

      Emacs doesn't do things like, for instance, edit movies or do Disney-style animation.

      The interesting thing about Emacs is that the above two limitations are not because Emacs can't do those things, but because no one was written the code to do them yet.

      Art mode's about due for an upgrade, anyway.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    29. Re:"weak" UX often found w/ the most powerful SW by spauldo · · Score: 1

      Emacs by default has menus and point-and-click functionality. A lot of users turn all that off. Of course, that's not saying that Emacs is easy, even with all that turned on, but what does market share mean to an open source project, anyway? As long as enough people use it to maintain the community, the project continues.

      I don't disable the menus because they're useful for rarely-used functions. I spend most of my time in org-mode or one of the programming modes, but every now and again I run something off-the-wall and the menu comes in handy. And hey, what's the point of having large monitors if I can't give up a few pixels for a menu?

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    30. Re:"weak" UX often found w/ the most powerful SW by spauldo · · Score: 2

      So, you have coworker with a different skillset, and you blame his choice of tools rather than the person himself?

      Did you come here from 4chan?

      I can't make out your point. Something about Unicode, some implication that open source doesn't offer features (which is false), a bunch of talk about various graphical stuff with the implication that those are unavailable in open source (the only one that might apply to is CAD, but I don't do CAD so I don't know), and then some sort of rant about GUI vs. CLI that doesn't apply to any of this (are you under the impression that all open source apps are CLI?).

      I hope your coworker is more coherent than you.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
    31. Re: "weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      That's a horrible thing to say. Forcing your own config on people makes you a little dictator, and that's not something to be proud of. How would you like it if I hacked into your computer and changed all the configs to something I like, just for fun? I am Anonymous. We are legion.

    32. Re:"weak" UX often found w/ the most powerful SW by chipschap · · Score: 1

      You have a good point. There are Emacs packages for unexpected things. Emacs, for instance, is my favorite audio player (the EMMS package among others are available) and that isn't even an extreme example.

    33. Re:"weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      block copy and paste

      Visual Studio does a nice job with Alt+Drag. Or it might be the Visual Assist plugin, I'm not totally sure.

      Plain old Visual Studio will do so just fine. As will Notepad++. And you can Alt+Drag select a block in Notepad++ and copy it to Visual Studio.

      IIRC MultiEdit (DOS version from mid-90's) used to have fairly similar functionality.

    34. Re:"weak" UX often found w/ the most powerful SW by Anonymuous+Coward · · Score: 1

      Try moving vim guys to emac, and vice versa.

      It's much easier than you think. Once you broke out of repetitive mechanical editing and learnt to use a programmable editor, should it be ed, teco, edt, ex/vi or emacs, it's easy to switch to a new paradigm, even if you happen to detest it. It's just a matter of taste and muscle memory from that point on.

      On the contrary, going back to some obtuse "user-friendly" interface, where you can't combine actions other than by tediously repeating them, is simply torture; it feels like slaving for the machine that was supposed to be serving you.

    35. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 0

      Interestingly, just reading the preferred environments of winning competition coders, few list a command line editor. Most a IDE or and heavy-duty GUI editor like sublime.

      I think this retro movement is a knee-jerk to "user-friendly" or "simplicity", as if that means "not expert". But as a Wired article recently made clear, most serious GUI tools are not simple at all. But the good ones are "Clear". Clarity only helps power-user tools, and certainly no unbiased observer would call a GUI editor or IDE "obtuse", and vim or emacs "Clear". Most command line tools need are solutions to their self-imposed problems. Back in the day we only had command line tools we could only dream of good IDEs that we have today.

      P.S. hat are all these tedious actions? Spend all my time thinking, architecting, then writing... mostly once.

    36. Re:"weak" UX often found w/ the most powerful SW by dbIII · · Score: 1

      You have misunderstood my post as if you did not read it.

      The software you mentioned has nothing at all to do with having wide experience or not.

    37. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 1

      not at all.
      software = tools.
      more tools, more things you can build.

    38. Re:"weak" UX often found w/ the most powerful SW by dbIII · · Score: 1

      With respect, an issue of someone being excellent at one tool but not at others has nothing at all to do with the tool itself.
      I'm starting to hope that you are just joking around because otherwise you are just exposing a personal problem you have with working in a team to the readership - quite literally a poor workman blaming the tools.

    39. Re:"weak" UX often found w/ the most powerful SW by hackertourist · · Score: 1

      People mistake "ease of newbies being able to do something" with "expert usability".

      The trouble with the Emacs/CAD approach is the steep learning curve. If you optimize you application for expert usability only, people have to become an expert before they are able to use the application at all.
      This is sort-of acceptable for one class of applications, i.e. those applications where you can expect the user to commit to this investment in time. Typically this sort of application will be the environment the user spends his entire day in.

      The problem is, those jobs are rare. These days people are expected to use a large number of applications in the course of a day. There is no time to become an expert in all of them, so the application UI has to facilitate more people than just experts. So we need both ease of newbies being able to do something AND expert usability.

    40. Re:"weak" UX often found w/ the most powerful SW by serviscope_minor · · Score: 1

      If you use a problem a lot, there is nothing wrong with users adapting themselves to a program. Or with configuration, the user adapts themselves a bit and adapts the program a bit.

      The attitude that the user is king and it is 100% correct that they can't be arsed to even learn the basics of what they're meant to be doing and are RIGHT to not be arsed reminds me of my local hackspace.

      People have the same attitude, but being a more physical place, damaged tools and occasionally damaged users result. In the computer realm, one's free from physical danger, but otherwise the same problems abound.

      Many high end, professional programs are in fact rather hard to learn and pick up. They are designed so that full time professionals can be as efficient as possible. If you, for example, throw your toys out and move on from circuit layout programs as soon as it doesn't work perfectly out of the box, you'll find yourself stuck with the weedy free/educational ones that simply aren't up to doing more than the basics.

      Turns out the world is quite complicated and you cannot represent it adequately with arbitrarily simple software.

      But it never ceases to amaze me how much sheer time and effort people are prepared to put in to avoid learning proper tools.

      --
      SJW n. One who posts facts.
    41. Re:"weak" UX often found w/ the most powerful SW by Anonymuous+Coward · · Score: 1

      Interestingly, just reading the preferred environments of winning competition coders, few list a command line editor.

      I think this retro movement is a knee-jerk to "user-friendly" or "simplicity", as if that means "not expert".

      You're projecting your own snobbery. Not everybody is obsessing about following trends and movements, emulating the elite and continuously assessing his own level of expertise. Some people just think that machines were invented to do the repetitive, mind-numbing tasks instead of them and absolutely hate having to repeat selecting, filling forms, moving windows and clicking menus instead of just issuing some fucking one-line command. Even the most stupid and inconsistent /scriptable/ user interface is worth more than the best designed inextensible gui.

      P.S. hat are all these tedious actions? Spend all my time thinking, architecting, then writing... mostly once.

      You're a freaking genius -- you conceive everything in your head, and then it just works: no debugging, no refactoring, no revision control is ever needed. More curiously, the interfaces and external libraries you're using are just as perfect and immutable as your code.

    42. Re:"weak" UX often found w/ the most powerful SW by umafuckit · · Score: 1

      No, that's not what I meant. The AC (I just realised he was AC, so he won't see the question I asked) stated that he had nifty editing tricks. I was after screen casts of those with explanations. e.g. like the SublimeText site.

    43. Re:"weak" UX often found w/ the most powerful SW by Anonymous Coward · · Score: 0

      Amen to that, brother!

      Case in point, IOS losing nice edges for buttons, suddenly how do you tell if that odd square is a button?
      And if you push it hoping to see it 'depress' nothing changes. Ugh.
      It went from THE most obvious UI to the least, instantly.

      I thought 'broken as designed' was the IBM way, not Apple. Guess I was wrong.

      And then the damn fools sent Android the same way, ouch.

    44. Re:"weak" UX often found w/ the most powerful SW by chipschap · · Score: 1

      Oh, I see ... there are screencasts of various Emacs tricks/packages on youtube.

    45. Re:"weak" UX often found w/ the most powerful SW by bidule · · Score: 1

      Many high end, professional programs are in fact rather hard to learn and pick up.

      Well of course, if you spend 20 hours a week using a single software. There are 2-3 that I use enough to master them.

      Not every piece of software is a "special snowflake" that deserves its own non-standard UX, no matter what its developper believes. The problem is not "the user is king", it's "the developper is king" who wears his emperor's new clothes by thinking users have 30 hours to waste in 30 programs to be functional.

      I've spent many years in an IDE that mapped "close" to ctrl-cmd-W to keep the important emacs shortcut free, amongst many key shifts. I had no problem adapting since I spent most of my time in it, but you should have seen those who dabbled in it... That completely cured me of any fantasy that users will pick the bestest over the easiest.

      No, you make the interface as standard as you can and you only deviate if there's a marked gain in efficiency. And even then, it's the same as the master rule of optimisation: don't.

      --
      ID: the nose did not occur naturally, how would we wear glasses otherwise? (apologies to Voltaire)
    46. Re:"weak" UX often found w/ the most powerful SW by taharvey · · Score: 1

        Even the most stupid and inconsistent /scriptable/ user interface is worth more than the best designed inextensible gui.

      Use a different OS, or learn more about the one you use. Nearly every element of every application I use on the Mac OS is extendable or scriptable through OSA scripting. It doesn't just stop at piping together textfiles, but can do any type of inter-applicaiton scripting. You are limiting yourself.

      You're a freaking genius -- you conceive everything in your head, and then it just works: no debugging, no refactoring, no revision control is ever needed. More curiously, the interfaces and external libraries you're using are just as perfect and immutable as your code.

      No, i'm not. But to prove the point, last year I had my best programmer program in C what it took another programmer in python 10x as long. Is C more expressive than python? Not a chance. The difference isn't usually in how much or how fast you type, it is how fast you think through the problem.

  9. Ban UI/UX experts by Anonymous Coward · · Score: 1

    Dear GOD almighty, UX and UI designers should be banned from ever touching a keyboard/mouse. They're the pariahs of software development. The first sign a software project is going downhill is always, always a shitty UI. When UI "experts" start calling the shots you know you're in deep shit.

    1. Re:Ban UI/UX experts by Anonymous+Brave+Guy · · Score: 5, Insightful

      UI is really no different to programming itself. A few people are really good at it. Many more people doing it are OK, but won't produce great results without some degree of leadership or guidance from the first group. There's a long tail of people who do more harm than good, and unless you can somehow get them up to the standards of at least the middle group, you're better off without them contributing at all.

      Also like programming, it's quite difficult to know someone really good from someone just OK unless you're already pretty good yourself. Otherwise you lack enough of a frame of reference to make informed decisions or, often, to collaborate effectively with someone from a different field.

      One thing that is a big difference is that at least there is some degree of objectivity with programming, in that up to a point everyone can see whether a program actually does its job when you run it, regardless of how it looks internally. With UI, there is much less hard data about general principles for what works well and what doesn't, and it usually requires significant effort and resources to collect hard data about the UI effectiveness in some specific area of a program under development.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    2. Re:Ban UI/UX experts by squiggleslash · · Score: 1

      I think we're at a point where UI and UX people are like architects after several years of buildings people built that have no doors, or are upside down, or just keep falling down for some reason, and the entire country is wondering why we continue to have architects.

      We do need UI and UX experts. The problem is that the people we currently employ as UI/UX people are spectacularly ill-qualified for the job.

      --
      You are not alone. This is not normal. None of this is normal.
    3. Re:Ban UI/UX experts by KGIII · · Score: 1

      A point, you have one! And it's a good one, thanks. I'd not thought of that but it makes me think it's also far more likely that a bad UI will make it into the public than a bad program. We also don't see the kludge under the hood that may be the programming but we do see the UI. That may also impact our views on the subject.

      Hell, I'm kind of grouchy that Opera beta changed the menu button from Opera to Menu. *sighs* They did it to improve the UX. It's trivial, I know, and it's in the same exact spot where it has been for ages but I still look and expect to see Opera and not Menu. They'll probably change it back in six months and it will bug me again. They seem to be in a flounder stage and have been for a couple of months now.

      --
      "So long and thanks for all the fish."
    4. Re:Ban UI/UX experts by Anonymous Coward · · Score: 0

      Not just that. Where there are people who are good at UX, they're often given no resources, no time and no consideration. It's better to push out a feature, incrementing on the GUI until there are 50 checkboxes of options each of which people need to read a chapter in the manual to understand. It's happened to me before.

      UX is often the last, if any thought in software design. And sad to say, a lot of engineers who neither see value in UI or UX are the ones who prevent it.

      "Oh, you just have to go to the command line, type ert, remember to type -i and then the line number, then all you have to do is type in the entire path and file name, remember to specify /r or /w." This is NOT a made up example. Every one of those switches and arguments could've been auto-defaulted in code instead but the first and only design people considered was to offload the responsibility onto the user. Once the problem was solved, then that was the end. "Why couldn't you just..." "C'mon, if someone can't be bothered to type an -i on the command line then the shouldn't even be using this tool!" Sigh.

    5. Re:Ban UI/UX experts by Anonymous Coward · · Score: 0

      Architecture is not a bad analogy, because it went through a similar period of mindless "innovation" and oversimplification to the detriment of functionality. James Kunstler wrote about "the damage of Modernism" in his book The Geography of Nowhere.

      Check out his TED talk How bad architecture wrecked cities. I particularly like his comparison at 8:20 of the Civic Center comparing its design to a DVD player. <g>

    6. Re:Ban UI/UX experts by Kjella · · Score: 1

      Actually, there is one big difference. With software development, the more you understand how it works the better. With UI/UX design you often know too much and think complex concepts, behaviors or interactions are obvious or see relations that aren't obvious from the user perspective. That said, I'd much rather have a domain expert like a photographer telling me how to make a photo editing software, an accountant how to make accounting software and so on. A generic UI/UX designer that doesn't know the actual workflows is likely to make something pretty and bad instead of ugly and bad.

      --
      Live today, because you never know what tomorrow brings
    7. Re:Ban UI/UX experts by Anonymous+Brave+Guy · · Score: 3, Interesting

      If you're building a UI without knowing your audience, it's almost impossible to do a good job. Building substantial, customised UIs has been a large part of my work in recent years. I think much of the value I bring to these projects is that I make a big effort to get inside the heads of real world users, see things from their perspective, and give them the UI they need to get things done. That means knowing the target audience, ideally through things like direct conversations with users and solid data about how the systems are being used. Some of the most important code I write is the code that converts between a simple presentation and interaction design that fits the user's mental model and the sometimes horribly complicated internal model used by whatever system they're talking to.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  10. Pot, meet kettle. Ketle, meet pot. by kevmeister · · Score: 4, Interesting
    I'd say it's an all out war for worst design between GIMP and Photoshop. I really, really hate the design of both.

    Many people complain about the GIMP, but I started there and then had to learn Photoshop. The only reason people complain about GIMP is that they learned to use Photoshop first.

    Then again, Apple, who used to be king of very functional design has thrown that all away in the search for "clean" appearance... whether or not it is consistent or usable and Google (Android) seems determined to follow.

    --
    Kevin Oberman, Network Engineer, Retired
    1. Re:Pot, meet kettle. Ketle, meet pot. by melted · · Score: 2

      I'd even extrapolate further: in the vast majority of cases paople complain about X because they learned Y first. Except when it comes to Windows, which is a pile of garbage in absolute terms. :-)

    2. Re:Pot, meet kettle. Ketle, meet pot. by brantondaveperson · · Score: 1

      What's wrong with Photoshop's interface? Please be specific, because personally I find it excellent to use.

    3. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      It's OK, but there are some oddities. For example how undo works. It's really annoying when you switch between multiple piece of software and one has a non-standard undo.

    4. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      I was amazed at how iOS uninstalls apps. Hold your finger on the display until the icons shake, then click the "X" icon to delete. That's not intuitive at all!

      Word verification: disgust

    5. Re:Pot, meet kettle. Ketle, meet pot. by dog77 · · Score: 1

      I have used an Adobe Photoshop lite version in the past and I don't have a recollection of it being bad, but recently I tried using Gimp to create some simple textures for a game and struggled with this simple task. I had trouble finding how to do really fundamental things like change the size of the paint brush or pencil, or where you can easily select a different color. After searching, I found out how to change the size, but then after encountering next challenge color, and even asking a friend, in case I was just being completely oblivious, he could not figure it out either. Maybe I closed one of the many pop up windows that I needed, and could not figure out how to get back. Overall my experience was very bad with Gimp. I gave up based on a recommendation by others to just use paint.net. Paint.net was very straight forward and intutitve. So at least from a non expert user viewpoint, Gimp is a very difficult to use UI.

    6. Re:Pot, meet kettle. Ketle, meet pot. by JoeMerchant · · Score: 1

      Agreed about Photoshop and GIMP - if either was an Apple product, it would have one button that did the most common thing that their research says people do with the software, and anybody who needs to do something with more control would be directed to the Adobe download in the Apple store.

    7. Re:Pot, meet kettle. Ketle, meet pot. by kevmeister · · Score: 2
      You learned Photoshop first with no pre-suppositions of how to do things. You moved to GIMP and nothing was where you expected to find it. Exactly the problem I experiences with Photoshop. But I won't defend the GIMP design as it is really terrible. But that does not make Photoshop good.

      I do find it interesting that you mention brush and pencil characteristics. I have to say that I had a terrible time with these when I first used Photoshop.

      As a matter of clarification, I am NOT a graphics expert in any way. I use mostly Photoshop (four year old version) these days and I know how to do the things I need to do. I don't use large portions of its capabilities and this may have produced a different reaction than pros or serious graphics amateurs might have.

      --
      Kevin Oberman, Network Engineer, Retired
    8. Re:Pot, meet kettle. Ketle, meet pot. by AmiMoJo · · Score: 1

      You have it backwards. Google stated flat design for web pages, because it's easy to do without images so pages load quickly and look clean. Then they extended it into material design for mobile.

      Apple copied Google, as did several others including Microsoft.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    9. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      The comment "It's horrible!" by users referring to a CAD product often turns out to be "It doesn't work exactly like AutoCAD."

    10. Re:Pot, meet kettle. Ketle, meet pot. by thegarbz · · Score: 1

      The only reason people complain about GIMP is that they learned to use Photoshop first.

      Oh hell no. I started with GIMP and then learned to use Photoshop. I was enlightened. A usability veil was lifted. I went from a clusterfuck of windows all over the screen to actually running what appeared to be a coherent program (This was before GIMP introduced a single window mode which we had been asking for for many bloody years).

      It wasn't that GIMP was different that Photoshop, it was that it was nonsensical. Everything took more clicks, everything took longer. Photoshop wasn't different, Photoshop was consistent with the interfaces of the many photo editing tools on the market which all started converging to a common interface. Photoshop, Corel Draw, heck even MS Paint had interface elements and usability in common. The difference between GIMP and the rest of the industry was about the same as using a GUI vs using a CLI.

      I changed from GIMP due to limitations in its capabilities at the time. But it wasn't until I changed that I realised we don't know how much better things are on the other side of the fence until we've been there and rubbed our faces in the lush green grass. To date it is the single happiest switch away from a piece of software I have made. I can't state enough how absolutely crap I found GIMP as a program. And while this is just one man's opinion it is the opinion of a user, a lost user. Lost like many other users who got sick of using it and finally jumped ship.

    11. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      And I learned darkroom photography first, and Photoshop's layout makes more sense than GIMP. Even Corel Draw makes better sense than GIMP, and I actually use it before Photoshop.

    12. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      I've never used Photoshop, but still find GIMP is extremely unintuitive. Anytime I need to try something new, I need to go watch a video to learn how to do what I want with the UI.

    13. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      I just converted a bunch of PNGs to JPEGs. I couldn't automate it because the JPEGs need varying quality settings that I had to assess by eye.

      Every time I used "Save for Web" to export a JPEG then closed the PNG, Photoshop asked me if I wanted to save the "changes" to the PNG. There were none - exporting is not a change to the original!

      One of Jef Raskin's laws from The Humane Interface is: "A computer shall not waste your time or require you to do more work than is strictly necessary."

      I wanted to kick Photoshop in the nuts halfway through.

    14. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      Buttons that you push and hold to get more buttons?

      At least they eventually got around to putting a little mark in the corner to let you know which buttons you hold down to get more buttons.

    15. Re:Pot, meet kettle. Ketle, meet pot. by Anonymous Coward · · Score: 0

      Working on multiple screens can be a pain, too.

      I just did a selection in a PS window I have on screen 2. Inverted the selection and hit shift-F5 to fill the selected area.

      Fill dialog comes up on screen 1, where I'm not looking and none of the tools are.

  11. Braindead commenters on Slashdot... by Anonymous Coward · · Score: 3, Funny

    ...will ironically continue to wonder why the "Year of Linux on the Desktop" hasn't happened while simultaneously misunderstanding and dismissing UI/UX.

    1. Re:Braindead commenters on Slashdot... by west · · Score: 2

      Very apt.

      But they're also the people that feel that making a better product at a lower price should bring commercial success.

      And to be honest, it took me watching products I loved and could make a case were objectively better fail against products that had better "curb appeal" and marketing smarts to realize that assuming consumers were logical was utterly illogical, given the evidence.

      The real challenge is to make a product that appeals to people who know nothing about the product (but will be making purchasing decisions) that also doesn't alienate too many of the people who actually have to use the thing. Most of the UI/UX people I've worked with were more marketing than anything else. And *that* was what made them valuable to the product as a whole.

    2. Re:Braindead commenters on Slashdot... by Anonymous Coward · · Score: 1

      Perhaps, but what's being talked about here isn't the real problem anyway. People don't use Windows because Linux is too ugly. They use Windows because they can't figure out how to use Linux.

      It might even be forgivable that one so often has to resort to command-line solutions to Linux problems if only it were possible to find those command line solutions without first coming across several solutions for different versions of Linux which no longer work, turning what could have been only 15 minutes of pain into 90 minutes of pain as one attempts various solutions and is left to only wonder why the solution doesn't work.

      For example, I once had Linux on a Macbook. Since the Macbook uses the function keys as special-purpose keys by default (controlling screen brightness and volume) and require pressing the Fn key in order to make them work as function keys, whomever wrote the linux driver for the Macbook's keyboard decided that things should work the same way in Linux, despite the fact that Linux isn't like Mac OS which has been dumbed down to the point that there's simply no functions for the function keys to perform. So to make the experience tolerable, you have to reconfigure the keyboard so that the function keys work as function keys by default. So do you open the control panel and find this stupid setting and turn it off? Of course not. In Linux, nothing you actually want to configure is in the control panel. So you fire up a web browser and find that you need to change this particular kernel setting, and they even give you the exact line of text and tell you exactly which file to put it in. So you do that, but it doesn't work. So you continue searching, and find a similar solution, but in this one the variable you're changing has a different name. So you try that. Still, it doesn't work. So you continue looking and find, holy fuck, they renamed that variable a third time. Finally it fucking works.

      The fact that using a text editor on a system file is required to resolve that problem is enough of a user experience fail in itself, but that 2/3 of the information on the internet about how to solve the problem is incorrect just makes it an absolute nightmare. How many problems like that is a user going to solve before they decide "fuck this shit" and go back to Windows? Will they manage to solve even one?

      That's the user experience that Linux needs to solve, and it has fuck all to do with any change that any UX expert would suggest. We don't need new icons and checkboxes, people know how to use icons and checkboxes well enough that they'll figure it out no matter what those things look like. Indeed, the fact that these new user interfaces are usable at all is evidence of that. The real problem is that Linux is no more useful than OSX: If it does what you want by default, you're good to go, but if it doesn't, you're completely fucked because getting it to do anything else is a nightmare. The only difference between Linux and OSX in that regard is that, at least in Linux, if you dick with it long enough you can eventually get it to do what you want. In OSX, if it doesn't already do what you want, just forget about it because it never will. What keeps people on windows (at least older Windows like XP and 7) is that it is easy to reconfigure so that everyone can have an OS that actually behaves the way they want it to behave, and without having to be a computer programmer in order to understand how to reconfigure it.

    3. Re:Braindead commenters on Slashdot... by Anonymous Coward · · Score: 0

      While UI/UX experts will continue to claim that a pretty UI will magically make all the 3rd party apps (which is what people actually want) get ported to Linux. Making the desktop "prettier" or "easier to use" will not get me games or apps on the shelf at Wal-Mart (not that I personally need them, but then again, I still use apps from the 90s and am fine with that). Especially considering that most of these apps invent their own UI anyway, regardless of the OS.

    4. Re:Braindead commenters on Slashdot... by Anonymous Coward · · Score: 0

      Perhaps, but what's being talked about here isn't the real problem anyway. People don't use Windows because Linux is too ugly. They use Windows because they can't figure out how to use Linux.

      Ha, you wish. I use Windows because Linux's core APIs are frozen in the 70s where its UNIX roots originate and the UI for most programs are frozen in the 80s. OS X at least puts a glossy patina over the old UNIX cruft. Windows is crap in its own ways as well but at least it's not fossilized crap.

    5. Re:Braindead commenters on Slashdot... by Anonymous Coward · · Score: 0

      Ha, you wish.

      Why is it that every time someone misinterprets one of my posts, they also have this snarky attitude in their response?

    6. Re: Braindead commenters on Slashdot... by Anonymous Coward · · Score: 0

      Turns out you're both wrong: People use Windows because MS threatened/bribed OEMs to include Windows by default. Hah! I win!!

    7. Re: Braindead commenters on Slashdot... by Anonymous Coward · · Score: 0

      Well, let's just agree there are a lot of reasons. However, if Linux could just fix some of them, I think it could gain some ground. I'm sure there are a lot of "power users" who could use Linux even in its present state, but it offers them nothing other than the headache of learning a new system. If it could just remove that headache by having *all* of the settings modified via the GUI, so that they're discoverable rather than being something one has to search the web for solutions for, encountering several old solutions that no longer work along the way, then these people would probably at least run Linux on one of their many computers.

      I mean, if Linux just had its shit together, then when Microsoft did shit like Windows 8, Linux could have come in and been like "OK, we're a modern OS with a GUI you'll love," and won over some new users at that point, but unfortunately Linux won the race towards creating a GUI no one wants and so it was far from being in the position to do that. Honestly, I'm still convinced that Gnome 3 is the result of Microsoft secret agents determined to make sure that Linux never becomes a viable alternative. It's the only way I can make sense of what happened. No one can be so stupid as to think anyone wants Unity.

      Fucking with something basic like that is as if someone came into your house and said "well, I see you're quite familiar with these 'floors,' but I think you'd be impressed if you just took the time to get used to our new 'inclined planes.' So we've gone ahead and replaced your floors." If you have some new design that you think is wonderful, then why can't it survive as a new project? Why must you find an existing project, throw away all of the existing work, and replace it with something entirely different? The only reason I can think of is that destruction of that existing project was the goal all along.

  12. mystery meat navigation by Anonymous Coward · · Score: 0

    The smartphone era has seen the resurgence of Mystery Meat Navigation thanks to Apple and Google. UI/UX is currently racing to the bottom.

    1. Re:mystery meat navigation by Anonymous Coward · · Score: 0

      Every year is the year of Linux on the desktop. At least for the 3-5% of people using it.

  13. Adobe? by Anonymous Coward · · Score: 0

    What? Adobe...open source?

  14. "Professional" does not imply "good". by Anonymous Coward · · Score: 1

    One of the largest contributing factors is the lack of professional designers contributing to open source projects.

    No, it's the lack of good designers.

    Whether the designers are professional has nothing to do with it.

    Professional designers can be terrible, as demonstrated by Windows 8, where the professional designers were utterly unable to see that forcing a mobile UI paradigm on the desktop was a total disaster.

  15. Shoot the messenger by frnic · · Score: 3, Informative

    It's nice to see slashdot hasn't lost it's ability to shoot the messenger. Instead addressing his comments, which are pretty much right on, everyone takes the opportunity to point out the designs they feel are worst ever.

    Fact is, Open Source will remain counter culture until it has full teams to meet the designs that the public wants, instead of designing to geeks desires.

    1. Re:Shoot the messenger by Anonymous Coward · · Score: 5, Insightful

      full teams to meet the designs that the public wants, instead of designing to geeks desires.

      Why should it ever "meet the designs that the public wants?" Seriously, why would anyone consider that as a goal?

      What the public wants is well represented by Android, iOS, Windows, and the like. The public already has this. Please, let us technical people have one last bastion that doesn't suck for the technically literate. "The public" has its playgrounds, complete with malware, spyware, adware, bloatware, and all the rest. They got the "designs they wanted", and that's what they did with them.

      Leave the rest of us alone. We're quite happy here with our technically oriented, non-handholding, niche OS. Don't try to ruin what we have, after you already ruined what YOU had.

    2. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      Fact is, Open Source will remain counter culture until it has full teams to meet the designs that the public wants, instead of designing to geeks desires.

      I'm sensing a disturbance in the internet. Its like thousands of geeks suddenly cried out "this is how we like it, now get off our lawns".

    3. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      Sorry, but getting a lecture from someone at Adobe about UI/UX is about as hypocritical as getting a lecture from Mugabe about human rights.

      Case in point: Adobe Flash update manager.
        Why the flying fuck can't it simply keep the users original setting of how to recieve updates?
        Every fucking time there's an update, it resets it to "Allow Adobe to install updates automatically".

        Seriously, why bother with user preferences if you're not going to respect them ?

    4. Re:Shoot the messenger by west · · Score: 4, Insightful

      An insightful point. The trouble is that many of the open source products also covet what the mainstream has - market share.

    5. Re:Shoot the messenger by Ralph+Spoilsport · · Score: 0
      "Why should it ever "meet the designs that the public wants?" Seriously, why would anyone consider that as a goal?"

      Are you making software for the public to use or not? If no, then fine - go back to text based interfaces. If you're making software for others to use, and these others may not be as smart and savvy as you, then fuck off - grow up and design what the public wants and needs.

      --
      Shoes for Industry. Shoes for the Dead.
    6. Re:Shoot the messenger by JoeMerchant · · Score: 1

      One could say that they are serving their target market quite well. What "feeds" an open source project? Users? No, developer-users.

    7. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      You sound mad? Did the geeks here offend your delicate hipster goatee and unsettle your fake glasses?

      I guess you should have more confidence in the value of your own profession.

    8. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      Case in point: Adobe Flash update manager.

      Don't forget the latest fuckery. https://www.adobe.com/products/flashplayer/distribution3.html is going away. No more installers to update it, just a universe of shitty little stub executables whose only purpose is to download the real installer, forever. Fuck Adobe and fuck Flash.

    9. Re:Shoot the messenger by demented_hedgehog · · Score: 2

      Henry Ford said:

      "If I had asked people what they wanted, they would have said faster horses."

      Most people want what they're used to and aren't in a position to judge the merits of other approaches.

      It's not an entirely invalid position they want to minimize the time they spend learning this stuff, or to put that another way: maximize the return on the time they've sunk learning to do things the way they currently do.

      However, I don't believe I should have to do things inefficiently because they're lazy or disinterested. For a lot of tasks GUI's are for noobs (but not all tasks, e.g. creating images). I find Macs really painful to work with because they hide the underlying functionality (caveat I haven't used one in years). The new tablet/phone friendly window managers on PCs are really really painful to use. Just because the plebs want McDonalds doesn't mean I have to eat it (though it's ok now and again)

    10. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      Why should it ever "meet the designs that the public wants?" Seriously, why would anyone consider that as a goal?

      You could ask Linus Torvalds:

      Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect.

      --"The Way We Live Now: Questions for Linus Torvalds". New York Times. 2003-09-28.

      A lott of OSS people seem to have thinly veiled closed source penis envy.

    11. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      What the public wants is well represented by Android, iOS, Windows, and the like.

      Not hardly. Some of the worst examples of UI/UX can be found in commercial software: change done for the sake of change rather than done for the benefit of the users.

      Windows 8/10, OS X, iOS and Android have all shifted to a horrible flat UI where buttons and picklists are indistinguishable from the surroundings. I'm not sure which variant is worse: iOS & Android with their shades-of-grey or Windows with its big, gaudy boxes. The touch-based UIs have made things completely non-intuitive/non-discoverable by hiding functionality behind seemingly-random swipes. And let's not get started about Microsoft idiotically trying to force the random-swipe touch UI onto the mouse-and-keyboard desktop with Window 8.

      Microsoft led the charge backward with the introduction of ever-changing "personalised menus" and then made things worse with Office when they replaced menus entirely with continually-changing ribbons. I waste far more time trying to find things on the ribbons than I ever did with menus.

      With open source, at least there are some options available for those who find the ever-flattening commercial UIs and jiggly, over-animated glossy UIs like KDE's annoying to try to work around.

    12. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      > Henry Ford said: "If I had asked people what they wanted, they would have said faster horses."

      Not likely.

    13. Re:Shoot the messenger by gl4ss · · Score: 1

      have you used any adobe products? the company that has seemingly invented their own drop down menus for sake of usability. well, it's really more for user lock in.

      and then ubuntu & etc trying to copy just that.

      it's shite I tell you and it originates from adobe & their "professional tools".

      --
      world was created 5 seconds before this post as it is.
    14. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      It's nice to see slashdot hasn't lost it's ability to shoot the messenger. Instead addressing his comments, which are pretty much right on, everyone takes the opportunity to point out the designs they feel are worst ever.

      What comments are you referring to, specifically? TFA was pretty much content-free.

    15. Re:Shoot the messenger by AmiMoJo · · Score: 3, Insightful

      I know RMS is unpopular here, but how about because freedom? If the UI is the thing driving people to closed software and non free data formats, I see value in changing that.

      Imagine if you never had to deal with another PSD file, because the most common layered graphics format was the GIMP's.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    16. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      Never make anything simple and functional, when it can instead be gorgeous and useless...

      One of the grand fallacies, I think, of "UI design" is that there is a universally-good approach to the problem. Different people have different cognitive models of their workflow. There are, undeniably, truly-horrible UI designs that most folks would agree are horrible. But once you move beyond those basic levels of mistakes, you're left arguing about things that emerge from the differences in the way different people model their personal work-flow. What is truly-wonderful for one person may be donkey-sweat horrible for another. UI designs generally don't address this. They address the visual appearance, and where the menus pop up. The "window dressing". So when I hear "experts" ramble on about "UI designs that real people can use", I'm left wondering if they've ever worked with any "real people", or just some cog-sci-PhD-thesis model of "real people".

      I find that many of these "experts" in "user experience" tend to view the work that people do with computers as fairly simplistic--they send e-mail, browse the web, play games, watch porn, and occasionally author a document. But there are thousands of other, deeply-technical, tasks that are undertaken with computers where none of those simplistic views apply, and yet the cog-sci-PhD folks seem to think that those views apply.

      I've been involved with Gnu Radio for many years. One of the big complaints I hear about it is "it's too hard to use". What *actually* is going on is that users approach it as if it's some kind of glorified MS Word. They view the fact that actually having to *understand the field of discourse* as a horrible imposition. It's not about where the icons are, or what they look like, or whether the menus are in "obvious" places. It's about the work itself. To use a metaphor: "This NeuroTron 5000 is really hard to use--you actually, as it turns out, have to understand a whole bunch of stuff to use it. Like neurophysiology, and anatomy, and like, pathology, and all kinds of other stuff. Who has time for that? Why can't the tool do that for me?"

      I find that the UI/UX people mostly don't understand that it isn't a "sin" to require that the user have some relevant background to use the tool. Not everything one does with a computer can be neatly pigeon-holed into the e-mail/web-surfing/view-porn triumvirate.

    17. Re:Shoot the messenger by Anonymous Coward · · Score: 0

      Agree on the point - please don't bring (any more) patent-driven crap design to Linux please!

      One nit - "The public" didn't pollute its playgrounds with malware, spyware, adware, or bloatware. Hate to admit it, but geeks like us did that. Grandma can't write viruses.

    18. Re:Shoot the messenger by thegarbz · · Score: 1

      Why should it ever "meet the designs that the public wants?" Seriously, why would anyone consider that as a goal?

      The desire for the year of the Linux on desktop?

      Followup question: What's the design goal of a piece of software you want no one to use? I understand that some open source projects are hobby projects that serve the programmers interest but at the same time there's a lot of projects out there trying to become popular and in general use. In which case meet the design that the public wants should be the number one goal.

      Or do you actually like Gnome 3 and Firefox's interface, it's not like the public want those.

    19. Re:Shoot the messenger by drinkypoo · · Score: 1

      Imagine if you never had to deal with another PSD file, because the most common layered graphics format was the GIMP's.

      Imagine that GIMP could just read a PSD, and do things with it. Can't it? I'd think the problem would be that layer effects in PS don't exist in GIMP.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    20. Re:Shoot the messenger by angel'o'sphere · · Score: 0

      I find Macs really painful to work with because they hide the underlying functionality
      It is really not that hard to open a terminal window on a mac and run a Bash or your favourite shell.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    21. Re:Shoot the messenger by demented_hedgehog · · Score: 1

      Perhaps I'm being a trifle unfair on Macs. It's been quite a while since I used one (e.g. before the shift to BSD libs over Mach OS).

  16. Hang some tinsel from the menu... by Anonymous Coward · · Score: 0

    The "user experience" is inadequate, but that is not related to colorful themes, ribbon interfaces or new animations. Spray paint that old double-wide and it's still just a double-wide.

    It's the lack of consistency across platforms that makes even Windows users puke. Basic functionality is still in the last millennium. You can't even assemble a suite of portable Linux apps without rewriting most of the code.

    Mr. Garth Braithwaite should get his head out of his butt and pay more attention to some serious deficiencies. No, we don't need a better Flash Player for Linux, thank you.

  17. Why do they keep changing the UI then? by Anonymous Coward · · Score: 0

    The older I get, the less I adapt easily to change.
    This is particularly problematic with commercial OS / applications.
    I like Open Source products because when I upgrade them, I am not always faced with a new learning curve (exceptions of course, Gnome 3 I'm looking at you) and best of all, if I don't like it I can roll back to a prior version.

    I think it's the 'professionals' who can't nail down a good, consistent design that has longevity.

  18. Frequently a pointless goal by Anonymous Coward · · Score: 0

    Since too many times the complaint about design is basically "This doesn't operate or look exactly like another product I use!". Given that this is a pointless goal to achieve (unless there is only one such product in the world), and given that such designs can easily be locked up by "Look and feel" design patents, but only those with potloads of cash, therefore will be financially and legally untenable, the entire process is frequently pointless and really should be considered nothing more than an excuse, rather than an explanation or problem.

    GIMP will NEVER get spot colours because Kodak won't let them out. Complaining about it won't be fixable, by no decision anyone can make.

    Unless the just ignore the law and go ahead anyway.

    Please let us know who would take on, say, GIMP and support it in breaking the law on Pantone patents.

    1. Re:Frequently a pointless goal by Anonymous Coward · · Score: 0

      >> Please let us know who would take on, say, GIMP and support it in breaking the law on Pantone patents.
      Software patents are only valid in the USA.
      That's a very small portion of the world's population.

    2. Re:Frequently a pointless goal by Anonymous Coward · · Score: 0

      GIMP will NEVER get spot colours because Kodak won't let them out. Unless the just ignore the law and go ahead anyway.

      And how exactly do they keep them from leaking? Patents?
      (NB. emphasis was not added by me...)

  19. I disagree with the premise by QuietLagoon · · Score: 4, Insightful
    The UI/UX experience is weak in many software projects, not just open source software projects.

    .
    The premise looks at the worst of the open source software projects and compares it to the best of the proprietary software projects. That's typically how these types of comparisons are done, with a huge anti-open source bias.

    If you ask the wrong questions, you're going to get the wrong answers.

    1. Re:I disagree with the premise by frnic · · Score: 3, Interesting

      You make an excellent point, however, I would suggest that there are many more examples of "successful" open source projects that have poorly designed interfaces than successful commercial closed source projects.

      The issue I think is it is hard to get motivated to put the effort into UI design if your expected market is mostly geeks and maybe at best a few thousand users. If you are on a budget with a target audience of millions then it is easier to find the "time" or "motivation".

    2. Re:I disagree with the premise by QuietLagoon · · Score: 1

      ... I would suggest that there are many more examples of "successful" open source projects that have poorly designed interfaces than successful commercial closed source projects. ...

      Maybe because there are fewer open source than proprietary projects.

      .
      Once again, the premise is wrong.

    3. Re:I disagree with the premise by Oligonicella · · Score: 1

      I would suggest that there are many more examples of "successful" open source projects that have poorly designed interfaces than successful commercial closed source projects.

      The is true if and only if you put successful in quotes.

    4. Re:I disagree with the premise by Anonymous Coward · · Score: 0

      I think you are forgetting something here. Open source projects are all public, pretty much every single one is out there for anyone to use and criticize. But closed source... let me ask you, how many "internal/in-house" tools/projects does your employer have? Does any of them have a decent UI? There are lots and lots of programs out there with very small user base. Sometimes you just need some tool to do a very specific task and make life easier for yourself and maybe less than 10 colleagues. Heck i made one such tool just last week. Can't say i bothered to put much of an UI on it.
      Meanwhile, when a proprietary piece of software is made for public use, the eye candy matters. How it looks is part of how it sells after all and if it won't sell there is little point in making it in the first place. Thus the UI gets lots of attention and an effort is made to get it right.

    5. Re:I disagree with the premise by Roger+Wilcox · · Score: 1

      The article fails to discuss what it thinks "bad UI/UX design" is or to mention any specific open source projects that incorporate it.

      I, too, disagree with the premise. However, I will go further and suggest that there is more than merely "anti-open source bias" at work here. The article is so shallow and so baseless that it seems designed to trick as many hapless Slashdotters as it can into accepting the premise without reading TFA--and little else.

      This article propagates the idea that open-source UI is bad, despite presenting zero evidence to that effect. It has a cute and catchy title "Open Source Is Ugly" and then fails to address the basic points of that claim: what an ugly UI is and how open source fits that definition. Thus, the article is seemingly nothing more than astroturf. In this forum I am surprised more haven't called this out.

  20. Change All Names, Redefine All Terms by Pseudonymous+Powers · · Score: 4, Insightful

    In my experience, when a UI expert says you need to fix your interface, he is almost certainly right.

    When a "UX" "guru" says you need to "update" your "experience", he is almost certainly wrong.

  21. good UI is hard, more designers isn't the problem by danomatika · · Score: 4, Insightful

    A good UI is hard and takes *a lot* of time. I don't think the problem is a lack of designers but a lack of designers who can really put in the *time* with developers to actually polish things.

    Sure, you can get things working to 90% but that last 10% that actually makes something quick and easy to use if HARD. Most open source projects just don't have enough people with enough time to devote to that last 10%.

    The "open source is ugly" premise is sometimes right but for the reason that we're used to closed source software companies actually having enough staff and devoting enough time to that last 10% ... some of the time ;)

  22. It's not that open source is ugly by presidenteloco · · Score: 1

    Ok so there's a small problem about lack of aesthetics in open source user interfaces.

    But that problem pales in comparison to the poor usability of many FOSS applications.

    I think the usability problem there is a lot to do with an Aspergers-like (focussed on own knowledge and context, non-empathetic) trait among developers.
    A developer often makes the mistake of developing a UI that they themselves find easy and fast to use.
    They can't or won't empathize with another, non-technical user. They can't or won't think "As that person(a), what do I know and not know? In general, and specifically as I approach and go through the UI) What are my goals? What is my vocabulary and set of concepts?"
    They can't or won't even put themselves in the place of a user who is another technical expert but doesn't have the particular same technical knowledge, goals, assumptions, or focus of attention that the developer does.

    Non-FOSS software products often benefit because the company can afford to bring in UX specialists to work alongside the pure software developers, whereas many FOSS projects are pretty much software developers only.

    --

    Where are we going and why are we in a handbasket?
  23. Lack of "professional designers" is a good thing by mfearby · · Score: 1

    I remember when I used to use Linux: Ubuntu 10.04 with good ol' GNOME 2.32 or whatever it was. Then Shuttleworth had the great idea to throw it all out and bring in the professional designers. I'm now a Mac user, which may seem ironic because Apple has plenty of professional designers, but the ones Shuttleworth hired must have been complete UI Nazis because what they came up with was an abomination. I don't know whether Linux can afford or attract decent designers; the only ones they seem to find are people with some very strange ideas, and who don't actually use computers.

  24. Telemetry by Anonymous Coward · · Score: 0

    Frankly, I don't give a flyin' fuck about the UX/UI of ANY OS/platform/app I use. What I DO give a flyin' fuck about is all the goddamn telemetry/phone-home bullshit that's finding its way into everything that runs on a CPU. For example: http://news.softpedia.com/news/the-document-foundation-wants-to-overhaul-the-libreoffice-interface-497839.shtml. Last I checked, LibreOffice already collects usage data & sends it somewhere; supposedly it's opt-in. Mozilla supposedly uses telemetry in Firefox. What's their marketshare again? How well-liked is Firefox's UX/UI? And Microsoft, backporting their telemetry bullshit to windows 7/8/8.1; WTF for? Next time I plop my big ass down on the crapper, I'm gonna have to think about the ginormous epidemic of jackassery that seems to be spreading, and electing a minority, Barack Obama, into the whitehouse, was THE catalyst that got the turdball rolling. In the city I live in, the city council was recently usurped by four females through a rigged election. Look here: https://www.yakimawa.gov/media/points-of-interest/new-yakima-city-council/ and here: https://www.aclu.org/news/federal-court-rules-yakimas-voting-system-violates-voting-rights-act. Yakima is owned by a drug cartel, & Barack Obama likes it that way; nothing like equal rights & equal opportunities for the poor minorities.

  25. Copying other ugly UIs by OrangeTide · · Score: 2

    Open Source is ugly when they copy Apple and Microsoft. Almost all of the big projects do it, and claim it as some kind of central feature or revelation in design.

    --
    “Common sense is not so common.” — Voltaire
  26. It's the tools by The+Nipponese · · Score: 1

    It's pretty simple, and I'm always surprised software engineers have such a hard time understanding this: Specialize for the user.

    Does the vi UX suck? No, it's perfect for people who are great are memorizing esoteric commands for efficient text editing.

    Does GIMP UX suck? Almost all professional designers have been brought up using either OS X or Windows. Yet the GIMP UI still looks like it's running under X11. That's a non-starter for 99% of the user base, unless you're going to tell me GIMP was never meant to enter the mainstream.

    In summary, don't cheap out on the UI because you want to use some open source UI library. Understand end-user expectations (i.e., not just YOUR expectations) and fill them.

    1. Re:It's the tools by brantondaveperson · · Score: 1

      Does the vi UX suck? No,

      Yes. It does suck. It's possible to learn it, just as it's possible to learn to ride one of those funny bikes that has the handlebars connected to the front wheel via a pair of cogs, so that turning left makes you turn right. It's possible to learn it, and even become proficient, and possibly even to make an argument that it's better for some definition of the word. But it still sucks.

      Does GIMP UX suck?

      Yes. It sucks too. Its use of space is inefficient, and the underlying implementation of it is exposed too much (I have to resize layers, rather than this being taken care of by the implementation automatically). That it happens to be ugly isn't really much more important than its dreadful name. They managed to rename Ethereal (wtf is that??) to Wireshark (good name, makes sense, lets you make jokes about frickn' lasers...). Why can't they manage it with the GIMP?. Yes, I know why they re-named Ethereal, that's beside the point.

      In summary, don't cheap out on the UI because you want to use some open source UI library. Understand end-user expectations (i.e., not just YOUR expectations) and fill them.

      Good advice. Trouble is, that's really expensive.

    2. Re:It's the tools by The+Nipponese · · Score: 1

      Good advice. Trouble is, that's really expensive.

      In the case of GIMP, I think it's pretty simple: If you are porting OS X, have the professional pride to learn the native UI libraries. XCode is free and placement of UI elements doesn't really require reading documentation, just use the industry leader and make improvements where you see fit.

    3. Re:It's the tools by Anonymous Coward · · Score: 0

      His opinion reflects the opinion of 99% of people you could expose to GIMP. That should tell you something. If you refuse to believe it, try to verify it yourself then.

      I've used GIMP before to print thousands of professional-grade CMYK posters. However, in time I've forgotten the arcane workings of the tool. I tried now just for the heck of it, and luckily managed to draw something until suddenly the tool changed to moving the entire picture without my input. Had to spend a couple of minutes to be able to draw something again, but then the pencil was different for some reason. It just doesn't make any sense. I'm sure you can train to do everything you need, like I did once, but it really shouldn't be necessary for such a simple kind of tool. There's just a lack of intuitive logic behind the actions that the tool exposes.

    4. Re:It's the tools by dbIII · · Score: 1

      unless you're going to tell me GIMP was never meant to enter the mainstream

      If by the mainstream you mean a single window on a single desktop, then yes, it was not until a few years ago. Now it has the optional photoshop style UI - the stupid thing of everything in one window where the application has to act as a window manager as well as the window manager that's already there. Despite the extra pointless busywork to do that sort of UI it was done, yet you are bitching about it as if it was not!

    5. Re:It's the tools by Anonymous Coward · · Score: 0

      What you just described was functional. What the other guy described was aesthetic.

    6. Re:It's the tools by Anonymous Coward · · Score: 0

      ahhh, I understand now. By 99% you meant 99% of Mac users.
      The other 95% of the _real world_ don't give up on an application before they start just because it's the wrong shade of grey.

    7. Re:It's the tools by Anonymous Coward · · Score: 0

      I've always liked the idea of spliting up the interface so I could manage what was visible and where it was placed. Unfortunately, X window managers never seemed to handle all those myriad little windows well.

    8. Re:It's the tools by mattventura · · Score: 1

      Yes. It does suck. It's possible to learn it, just as it's possible to learn to ride one of those funny bikes that has the handlebars connected to the front wheel via a pair of cogs, so that turning left makes you turn right. It's possible to learn it, and even become proficient, and possibly even to make an argument that it's better for some definition of the word. But it still sucks.

      Not a good comparison at all, because such a bike offers zero advantage even if you become proficient at it. Whereas someone proficient in vim or emacs is far more efficient than someone using a "better UX" editor.

    9. Re:It's the tools by angel'o'sphere · · Score: 1

      Either you had a bad teacher or you use bad documentation.

      Vi is amoung the 'power full editors' the easiest to learn. Most people learn it in half an hour, as soon as you have the basics done, the rest reveals itself. Exceptions are obviously advanced buffer management ... and perhaps regular expressions.

      It is always funny if you e.g. see a german 'vi cheat sheet' ... often handed out as mouse pads by consulting companies.

      Every keyboard short cut is explained in german, without giving the actual mnemonic of what the code means, so it is realy impossible to learn them.
      y (yank), is explained in german as 'copies the text, word w, line y etc. into the clipboard', the english word 'yank' is not given ... so how to remember that y is copying (simplified)?
      o (open) and O, is explained in german 'make a new line below the current one 'o' or above 'O' ' ... again 'open' is not mentioned, hence again the o does not connect to its function.

      I actually would love to have an Vi Editor Kit glued into every text field in my Java Swing UIs. I know there is a kit for that, perhaps I can glue it with some aop into Swing ...

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    10. Re:It's the tools by brantondaveperson · · Score: 1

      Well, perhaps not. But I honestly fail to see how someone proficient in vim is more efficient than someone proficient in something that isn't deliberately as strange as possible. Maybe, in the past, when we didn't have arrow keys on our keyboards, and a mouse was just a rodent, vim made sense.

      The bike does offer the advantage of being able to run that stall at the fair, and probably make a bit of money too. There's always an advantage somewhere. Also, if you're being chased, and only have the weird bike to hand, then boom, you're away laughing. I'd suggest learning both, just to be on the safe side.

    11. Re:It's the tools by brantondaveperson · · Score: 1

      Either you had a bad teacher or you use bad documentation.

      Neither. I'm just lazy. I expect the arrow keys to move the cursor. I expect other well-known and common paradigms to be present. I expect the interface to be non-modal - modal UIs are probably unavoidable in general, but should be avoided as much as possible. Vi breaks these expectations, and causes me to instantly give up and go back to something that isn't different to everything else for no reason.

    12. Re:It's the tools by angel'o'sphere · · Score: 1

      Well, actually we use in our days "vim", vi improved.
      So the arrow keys do move the cursor (they do that in vi, too -- as this is only a question of the configuration file)

      The modes of VI are -- hm ... an issue -- however as you phrased it, somehow you have to have them.

      to something that isn't different to everything else for no reason
      But here you lost: vi is different for compelling reasons, e.g. being the first visual editor (hence its name, vi stands for 'visual'). So basically all the others are "different" for no compelling reason ;D

      I for my part rather have vi than Emacs where all the short cuts make no sense, and are hence for me completely immemoryable.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    13. Re:It's the tools by Rakarra · · Score: 1

      Well, perhaps not. But I honestly fail to see how someone proficient in vim is more efficient than someone proficient in something that isn't deliberately as strange as possible. Maybe, in the past, when we didn't have arrow keys on our keyboards, and a mouse was just a rodent, vim made sense.

      Fortunately, I learned vi well after arrow key support was added.

      The mouse is an ergonomic nightmare. And under some cases it can speed things up, but if you become familiar over a long period of time with keyboard shortcuts, they'll usually be faster than just about anything you're doing with a mouse, with the added bonus of less wrist pain.

  27. UI and UX are not equivalents. by jddj · · Score: 1

    Using "UI" and "UX" in the same sentence (or worse, as "UI/UX", as in some of the comments) showcases ignorance of the problems, solutions, and disciplines involved in making satisfying software.

    Most Linux projects could use a Costco-size box of UX helper, regardless of whether the UI works well or not.

    They're not orthogonal to each other, but fixing one doesn't necessarily fix the other.

    What's more, just like coders and EEs, UXers come in all shades of good, bad, heroic and abominable.

    Find a good one and work together. Her job is not to fuck up your favorite program.

  28. The real problem is Millennials. by Anonymous Coward · · Score: 5, Insightful

    In the end, the actual problem is that the people doing most UI/UX design these days are Millennials (aka Hipsters).

    An integral part of these people's identity is that they're always right about everything, even when they're absolutely 100% wrong.

    They've been raised by Baby Boomers (who we long thought to be the worst generation; Millennials have proven otherwise) to have a total inability to handle criticism. Legitimate criticism is typically mislabeled as "bullying" by Millennials. Perversely, because "bullying" is now allegedly involved, this allows Millennials to treat the wrongly-labeled "bully" far worse than the mislabeled "bully" ever treated anyone else!

    This is why it's not unusual to see Millennials ban people from online discussion, for example. Millennials tend to be petty tyrants, hypocritically claiming to support freedom and justice, while simultaneously showing extreme contempt for both by engaging in censorship.

    When you combine Millennials and their rotten philosophy with something like software UI design, the result is a complete disaster. Millennials automatically assume that their awful work is correct, even when users very plainly explain what the problems are. Millennials, being sure that they're correct, either deny or ignore the very valid complaints that users bring up. In the end the users typically move to an alternative piece of software, if one is available.

    Now before you start with the "get off my lawn" crap, this isn't about age. If whatever generation comes after the Millennials can undo all of the damage that the Millennials have done, then I welcome their effort!

    1. Re:The real problem is Millennials. by Anonymous Coward · · Score: 0, Insightful

      Wow now millenials are hipsters? Haha I didn't think the hipster term could be expanded to include any more people after it defaulted to "people who do things I don't like".

    2. Re:The real problem is Millennials. by JoeMerchant · · Score: 0, Troll

      Sorry, you could replace "Millennials" with people of that age from any generation and your rant still works.

      Wheel keeps a turnin' . . .

    3. Re:The real problem is Millennials. by Anonymous Coward · · Score: 4, Insightful

      Maybe if you established logical arguments, people would actually listen to your point? Your whole tirade seems to be about some group of people whom you either dislike or don't properly understand. Now, are you able to discuss the matter rationally, or do you try to undermine other people's efforts by complaining about them behind their backs?

      From your post, I suspect the latter, and indeed, such office politics could be labeled "bullying" as it's a rather underhanded way of sabotaging other people.

      Just because you believe in "a correct implementation", doesn't mean other people have your exact priorities to work on! I've heard countless tirades from "experts" and "specialists" who simply are stuck in their ways and refuse that there are more than their way to do things, or that their precious system is just one of many better and more efficient ways to do the same things.

      Of course, new employees will repeat old mistakes. It's because your culture is ass-backwards . Not to worry: In a few years, it'll become theirs. It'll be built on the foundation that you have laid out.

    4. Re:The real problem is Millennials. by Anonymous Coward · · Score: 3, Informative

      I'm pretty sure that Firefox 4 and later, GNOME 3, Windows 8, Chrome, and Slashdot Beta support what the GP is saying, and disprove what you're saying! There were lots of good software UIs developed by Greatest Generation'ers, by Boomer Generation'ers, and by Generation X'ers. I mean, these are the people who took the craft from not even existing and turned it into one with sensible and standardized idioms that worked wonderfully. Then around 2005 the Millennial Generation started getting involved, and things took a nosedive from there. We ended up with the debacles that I listed earlier. When three generations manage to do things right, and then the fourth royally fucks up everything, let's place the blame where it deserves to be placed: with that four generation! Despite being able to build on the knowledge of their predecessors, the Millennial Generation totally ignored it and have made nothing but one mistake after another. Let's face the facts: the Millennial Generation has done absolutely everything wrong. It's not just one project they've ruined. That would be understandable. They've ruined every single software UI they've had any influence over. Like I listed before, we're talking about Firefox, GNOME, Windows, Chrome, Slashdot, and even OS X to some degree. These disasters aren't random one-offs. The Millennial Generation systematically fucks things up. It's an inherent trait of theirs, and no other generation is anywhere near as awful, including the Boomer Generation.

    5. Re:The real problem is Millennials. by phantomfive · · Score: 2

      An integral part of these people's identity is that they're always right about everything, even when they're absolutely 100% wrong.

      "These people?" Are you talking about 90% of the programmers I've met in my life? Also, 90% of the lawyers, and 90% of the teachers, and 90% of the hippies, and 90% of the rednecks......let's face it, people just don't like to be wrong.

      --
      "First they came for the slanderers and i said nothing."
    6. Re: The real problem is Millennials. by slazzy · · Score: 1

      I think you're off by a generation when it comes to who millenials parents are for the most part. Baby boomers are approaching their 70's, some of their grandkids might be millenials.

      --
      Website Just Down For Me? Find out
    7. Re:The real problem is Millennials. by Anonymous Coward · · Score: 5, Insightful

      How did the dumb parent comment get modded up? Does anyone here even work in the software industry any longer?!

      Millennials make up the 18 to 35 demographic these days. As such, they're also the bulk of the employees working in the various branches of web and UI design.

      If you're working on software, and there are designers involved, in almost all cases they are Millennials. This is especially true in Silicon Valley, which heavily favors younger workers.

      Furthermore, most of the Millennials working in design are hipsters, without any doubt. "Hipster" isn't some vague term. It's a culture with its own specific styles of fashion, its own attitudes, its own beliefs, and its own aspirations.

      When it comes to software UI design, whether we're talking about web apps, mobile apps or desktop apps, the work is being done by Millennials, and it's almost guaranteed that they will be part of the hipster culture.

      It's exceedingly rare to find non-hipster/non-Millennial designers because most of them get ran out of the industry by the hipster Millennials, or they leave after getting fed up with having to deal with such awful people on a regular basis.

      If you actually worked in the software industry, you'd have known this, and wouldn't have posted as dumb of a comment as you just did.

    8. Re: The real problem is Millennials. by Anonymous Coward · · Score: 0

      From my experience about 10% of members of any group are good at what they do. This goes for programmers, doctors etc. The rest are average or really bad. They either five very little help or even damage the work of others.

    9. Re: The real problem is Millennials. by Anonymous Coward · · Score: 0

      Root cause is mathematic reality, that 50% is doomed to be below median. Now, who makes the decisions? Not "millenials", yet. Blame your own gen still..

    10. Re: The real problem is Millennials. by GLMDesigns · · Score: 1

      The term baby boomer keeps expanding. First it applied to the birth spike from 1946-1950; then 1946-1960 and now I've seen it go up 1964!!! Checking wiki it appears that some have expanded the boomer generation to before the end of the war (1943-1964).

      It's a ridiculous term as it applies to too broad a time span; you have the scenario where boomers were children of other boomers. How f*king retarded is that?

      I'm sure there are millions of baby boomers (defined as up to 1964) who have children who are millenials (or much younger). A baby boomer born in 1964 who has a child at age 40 (2004) would have a child in 5th or 6th grade.

      --
      If you're scared of your govt then you need to further restrict its powers
      Vote 3rd Party in 2016 and beyond
    11. Re: The real problem is Millennials. by Anonymous Coward · · Score: 0

      If everybody is equal, nobody is higher or lower than the median, though!

    12. Re: The real problem is Millennials. by Anonymous Coward · · Score: 0

      > It's a ridiculous term as it applies to too broad a time span; you have the scenario where boomers were children of other boomers. How f*king retarded is that?

      There's nothing wrong with that, as long as they were both born in a time when birth rates were still high.

      Can you think of a reason why "baby boomers" must refer to a single generation?

    13. Re: The real problem is Millennials. by Anonymous Coward · · Score: 0

      All of the generational definitions keep expanding. I was born in 77 and yet now I'm supposed to be part of Generation X? When I was about 15 years old, I remember seeing television programs on Generation Xers and they were all in their mid to late 20s.

      Baby boomers are people who were born from the late 40s to the late 50s. Generation Xers are from around 1960 to 1970. Generation Y is my generation, from about 1970 to 1980. Millennials are from around 1980 to 1990. Generation Z is 1990 to 2000.

      I'd just call the generation from 2000 to current "screwed".

    14. Re:The real problem is Millennials. by billcopc · · Score: 1

      I wish I had mod points, because this AC is +1 Insightful.

      Yes, it's a big hate-rant for millenials, and the tone sucks, but the facts remain. This is the "me" generation, entitled, spoiled rotten, and more interested in pseudointellectual mimicry than actual progress. The problem is that it is their parents fault. They are the ones who yelled at the teachers when their kid got anything less than top grades. When I was in school, if I got a bad grade, it was my own goddamned fault and there was no coddling about it. It taught me the value of criticism and hard work, and also to recognize my strengths and weaknesses, and work around them or enlist help. Sure, as a teenager I thought I knew everything, but it seems the bulk of today's young adults aren't growing out of that arrogant phase.

      I would say that the key piece missing these days is analytical skills. There's a lot of mimicry/repetition, and no actual thought invested. I'm no UX designer, but give me two minutes with anything, and I'll tell you what I think is wrong with it. I might not always know how to fix it, but I will identify it and explain my rationale for singling it out. Now, I am an analytical guy by nature and profession, so these things come naturally to me, regardless of field or medium. I'll look at who the target audience is, and how they might interact with the product. I'll intersect that with the goal(s) of the product, and how it flows from problem to solution. It's even better if I'm not an expert at whatever it is they client is doing, because I can then inject the outsider's perspective. The more I'm confused by something, there more opportunities there are to improve it.

      --
      -Billco, Fnarg.com
    15. Re:The real problem is Millennials. by Rakarra · · Score: 1

      Wow now millenials are hipsters? Haha I didn't think the hipster term could be expanded to include any more people after it defaulted to "people who do things I don't like".

      The "hipster" is one who rejects something that was popular for little reason other than it was popular and liked. The UX disasters we've seen over the last decade show an utter rejection of the usability and aesthetic standards of before. Because, uhhh.. they were cool, but people liked them, so they suck.

    16. Re: The real problem is Millennials. by Anonymous Coward · · Score: 0

      I'm genX - identify with them in almost every way. Born in 1971.

    17. Re:The real problem is Millennials. by Anonymous Coward · · Score: 0

      Can you name these "millenials" that were the designers on these products?

    18. Re:The real problem is Millennials. by theArtificial · · Score: 1

      Then around 2005 the Millennial Generation started getting involved, and things took a nosedive from there. We ended up with the debacles that I listed earlier. When three generations manage to do things right, and then the fourth royally fucks up everything, let's place the blame where it deserves to be placed: with that four generation!

      Windows 8 Metro designer is Julie Larson-Green born in 1962. She's a 22 year Microsoft veteran headed to Office next. The Gnome 3 design history shows William Jon McCann (whom I cannot find a DOB for. I don't think it's strictly a generational thing, and if anything you're barking at GenX.

      --
      Man blir trött av att gå och göra ingenting.
    19. Re:The real problem is Millennials. by Anonymous Coward · · Score: 0

      No, I'm sorry but the expansion of the meaning of the word "bullying" is really getting on my nerves. "Bullying" is when somebody physically threatens to do you harm because they want to force you to do what they say or want. "Hurting your feelings" is so far from the physical threats and punishment that real bullies use that it makes me gasp to think that this world is full of people who consider getting their feelings hurt to be pain that equals and replaces actually getting the shit beaten out of them.

      Bullying has nothing to do with UI or UX design. It has nothing to do with how Linus runs the kernel, it has nothing to do with your precious little feelings. Bullies are people who threaten or make good on threats to beat the hell out of you and leave you crying on the sidewalk. Is this clear?

    20. Re:The real problem is Millennials. by Anonymous Coward · · Score: 0

      Did you actually look up the definition of "bully" (verb) before posting that?

      Physical intimidation is not necessary.

  29. Linux is not fat! It just has a lot of packages. by Anonymous Coward · · Score: 0

    Why don't all you people just leave FOSS alone!!!!

  30. Less Fun by Luthair · · Score: 1

    I think there are two categories of projects, paid developer open source (e.g. Linux, Eclipse, etc.) and spare time open source. In the latter developers are largely scratching their own itch and generally won't be interested in spending a large chunk of their time effectively pushing pixels around, particularly when they could be adding a new feature.

    We need less back-seat coders in open source (people with an opinion but aren't actually writing code, e.g. all the anti-systemd whiners) and more people willing to jump in and write code if they are having issues.

    1. Re:Less Fun by Anonymous Coward · · Score: 0

      Personally I love SystemD's UI/UX. It's the sloppy functionality, amateurish coding and brain-dead design that needs work.

  31. UI designers are like feminists by Anonymous Coward · · Score: 0, Insightful

    and user experience design is like feminism: They look like good ideas, until you understand that they're just power grabs. UX people, like many architects, value form over function, and clarity over flexibility. Programmers gave us the Linux kernel. User interface people gave us Gnome.

  32. Are you kidding? by epyT-R · · Score: 4, Insightful

    The whole 'UX' campaign is what destroyed usability in today's software. It traded graduated learning and functionality with fisher price level capabilities. Large fonts, wasted whitespace, and condescending status messages (think google, facebook, or the 'new' microsoft) rule the day. Search boxes are tacked on after the fact to make up for the useless interface. Of course, when one of these users wants to do more or have a problem fixed, it's technical people who have to get around the total lack of flexibility and technical feedback to fix the problem.

    Lack of 'professional' designers is not the issue. There are plenty of paid designers turning out crap designs, too.

    The argument made about developers vs users is also bullshit. In earlier times, the applications were developed by developers for use by ANYONE who wanted to do whatever it was the application was designed for. This forced anyone who wanted to do these things to learn how the application works. If it was designed well, the result was an educated, productive user who understands at least some of the underpinnings of the required workflow. Today's 'designing' assumes the user is an idiot and actively prevents any real mastery of the process. This results in garbage output.

    VLC has a good design? Did they even look at the options panel? It has to be one of the worst. My favorites are the textboxes that give no clue as to the datatype or format expected. Firefox hasn't had a good interface since they wiped out the menu system. The fact that classic theme restorer is one of the more popular addons for the program speaks volumes about 'UX'.

    Naturally, the guy being interviewed pointed out mostly pointless web 'apps', each with typical hipster names that have no relevance to their actual functionality. About what I'd expect from 'UX designers.'

    1. Re:Are you kidding? by Anonymous Coward · · Score: 0

      "Large fonts, wasted whitespace"

      Just look at any bootstrap/foundation webpage etc. They fit about 3 sentences on the main page before you have to scroll. My monitor is 1080p. WTF

    2. Re:Are you kidding? by adiposity · · Score: 1

      I was dumbstruck when I saw VLC was on his list. I will do anything to avoid using VLC, in spite of its good support for so many codecs, simply because it has such an annoying interface. Media Player Classic is far superior, and it mostly just tries to act like a 15 year old version of Windows Media Player.

    3. Re:Are you kidding? by Anonymous Coward · · Score: 0

      Best recent status message from Microsquish in Windows 10: "Something Happened" - followed by crash of anything from an application to the whole system without error codes or anything else that might point you in the direction of a cause. If you're very very lucky, you might find something in an event log later, but don't count on it. At least Blue Screens gave you some hex to write down and look up later, and often logged details.

    4. Re:Are you kidding? by thegarbz · · Score: 1

      Search boxes are tacked on after the fact to make up for the useless interface

      You failed to understand the modern usability. Search boxes aren't tacked on after the fact to make up for the interface. UX designers have for the past 10 years been not hinting but flat out telling you the direction they are going is that the Search box IS the interface. This goes back to Vista and its "hit the windows button and start typing". No it goes back to Windows XP and the WinFS file system they were trying to roll out, no folders, just a search box and all your files are in a database.

      I only partially agree with you. Some UX stuff has gone full retard when it comes to software taking away usable functionality and replacing it with happy gestures or some crap like that. But as is typical the ideal world lies somewhere between the UIs of past, and the UX arts students who's never used a computer's ideal view.

    5. Re:Are you kidding? by epyT-R · · Score: 1

      Oh I perfectly understand where they're going. It's just fucking idiotic and those search boxes are indeed tacked on. Needed workflows are removed to benefit the race-to-the-bottom simplification campaign, and replaced with search. Gone are the easy to memorize control panels, sensible file managers, and menus that don't try to be built-in mobile devices. Now, everything's hidden behind a myriad number of large windows with lots of white space and generalized 'fuzzy' terms that could mean anything. The user has to guess where things are hidden (eg win10 settings panel). I suppose there are several reasons for this, but the big one is probably money. Getting idiots used to searching for everything can be monetized while people with established workflows and who actually have complex work to do cannot be.

      The problem is that the latter is hobbled having to search for everything all the time. The UIs of the past were spartan, but functional. There were few distractions. They prettied them up a bit with drop shadows, and animations, which was fine. They gave intuitive cues as to what was happening and they could be disabled. Today, it's a disaster, and I hate being the one who has to help users navigate these interfaces on OSs that used to provide flexible configuration and useful error messages. Sure, users hated the BSOD, but they're useful to people who are expected to fix the problem.

  33. "If you build it, they will come..." by Anonymous Coward · · Score: 0

    ...argue about what license it is and push you to change to another, rather than...contributing.

  34. He is Wasting His Time ... by gordguide · · Score: 2, Interesting

    Considering that the majority of Linux contributors are openly hostile to User Interface and Application "Look and Feel" considerations, and there is a general apathy to writing documentation to the "Hand Holding" level the average consumer demands, you only need to think about it for a moment to grasp the answer to "Is Linux ready for the Desktop" question.

    It isn't, and never will be; a Geek has to be there somehow or Grandma isn't buying, regardless of how useful it would be to her.

    1. Re:He is Wasting His Time ... by Anonymous Coward · · Score: 0

      I had to install some Linux this week for a project I'm working on, oh god, so horrible. After you get used to OSX using Linux is just ... bad. I can't seriously recommend that someone use this shit for mission critical production.

    2. Re:He is Wasting His Time ... by epyT-R · · Score: 1

      I could say the same for modern 'appified' applications on osx and windows...and modern website design as well.

  35. You can fix programming problems with good design by Dr+Herbert+West · · Score: 2

    From TFA:
    "What should developers who can't attract designers do? They shouldn't wait around. If they can hire a designer, great, but .... developers should look to improve their own design skills"

    As a dev, I want every possible option and every possible option to be exposed to the user, 'cause that's how I think as I'm programming.

    As a designer, I know better-- a good interface HIDES options and choices from a user (and the less technical your expected audience, the more should be hidden) until necessary.

    There's been many times where I've found that design choices can eliminate many programming problems and bottlenecks.

  36. What Constitutes Good UI and Good UX? by sk999 · · Score: 1

    The author recommends three projects as having good UI and UX:

    SASS: http://sass-lang.com/
    Bower: http://bower.io/
    Ember: http://emberjs.com/

    These projects have two things in common: their websites suck, and I've never heard of them before. (Well, Bower's website is OK).

    1. Re:What Constitutes Good UI and Good UX? by El_Muerte_TDS · · Score: 1

      But SASS and Bower are command line applications, and ember is a framework. How do these have a good user interface? Or is a product/project website now the UI of an application?

  37. Same to you by Anonymous Coward · · Score: 0

    It's true that poor but trendy UX/UI gumpf has ruined mainstream computing from the point of view of the nerdy minority.

    GP wants to retain an enclave of technical quality within a world of dreck. I support this.

    But with the garbage that passes for quality software these days, all moving elements and meaningless icons, we won't keep any quality software unless we fight for it.

    And who ever said we'd left "text based interfaces"? Just because they are difficult for newbies doesn't stop experts from using them as fast as thought can travel.

  38. UX is massivley more than graphics by drolli · · Score: 1

    and, in my experience people get used to all kind of shitty or non-shitty icons, but if UX fails in central points (like clearly conveying importan messages to the user or providing fluctuating support for basic features like copy&paste) it frustrates users much more.

  39. Re:good UI is hard, more designers isn't the probl by Anonymous Coward · · Score: 0

    This. Good UI is harder than developing program code since it requires both designing the stuff, programming it and then convincing the programmer X number of times to change it again until it "gets right"!

    Few people appreciate and respect that, which makes them irrelevant to such discussions.

    Damn! Captcha: lexicon ;-)

  40. Re:good UI is hard, more designers isn't the probl by TheDarkMaster · · Score: 1

    This one. Polishing is boring and takes lots of time, and the new developers have horror to "boring code".

    --
    Religion: The greatest weapon of mass destruction of all time
  41. speed!! by Anonymous Coward · · Score: 0

    frickin' SPEED!!!! Very high on my list of any UI design. BUG FREE would be second.

    1. Re:speed!! by Anonymous Coward · · Score: 0

      Amen. I'm still waiting for a new version of Firefox that can keep up with my FRIGGIN' KEYSTROKES as I type in a URL!

      Seriously, if you're going to look up my typed text in the history or Google or whatever, WAIT until I'm finished typing!!

  42. Ug, that's not what happened by rsilvergun · · Score: 1

    google pulled $100 million dollars in funding and _that_ destroyed the project. A few (easily undone if you're so inclined) UI tweaks didn't do that. It's just the part that gets the most nerd rage because it's the most visible.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Ug, that's not what happened by Anonymous Coward · · Score: 0

      I didn't dump Firefox because of nerd rage. I dumped it because most of the functionality was stripped out of the interface in the name of minimalist hipsterism.

      Ug indeed.

    2. Re:Ug, that's not what happened by Zontar+The+Mindless · · Score: 1

      google pulled $100 million dollars in funding and _that_ destroyed the project.

      So you're saying the UX-tards had to remove all those options from Firefox because they could no longer afford the rent for the space those options occupied?

      Somehow I'm not convinced.

      --
      Il n'y a pas de Planet B.
    3. Re:Ug, that's not what happened by Anonymous Coward · · Score: 0

      Rubbish. If they had left it as it was, it would not have been a problem.

      Designers: Please stop removing options while an interface is usable. Beyond a certain point it is less usable, not more.

  43. gasping at emacs? by mveloso · · Score: 1

    I gasp every time I see someone who bothered to learn emacs.

    Actually a good UX person recognizes the audience for a given piece of software and designs for that audience. That was well known back in the stoplight book. The problem is that product people don't realize that grandma is not the appropriate target audience for everything.

    1. Re:gasping at emacs? by spauldo · · Score: 1

      Emacs isn't hard to learn. It's certainly no harder than vi. It helps to ignore all the parts in the tutorial about being compatible with old terminals - in other words, if you like using PgUp/PgDown and the arrow keys, use them - they work just fine.

      If you do a lot of text editing, you just switch to it. In a couple weeks you'll be up to your old speed or faster than you were in whatever you used to use (unless what you used to use was just a simple editor, in which case you'll be up to speed in much less time). Learning to customize it involves learning some LISP, but LISP syntax is simple and you can pick it up pretty quick (probably quicker than vimscript, anyway). I came from vim so I use evil mode, which gives Emacs vi keybindings.

      --
      Those who can't do, teach. Those who can't teach either, do tech support.
  44. Not much of a story here, eh? by Anonymous Coward · · Score: 0

    I'm just sayin'..

    Not much of a think piece either

  45. No man is an island. by westlake · · Score: 1

    What the public wants is well represented by Android, iOS, Windows, and the like. The public already has this. Please, let us technical people have one last bastion that doesn't suck for the technically literate.

    The thing is that, in the real world, the function of the tech guy is to facilitate communication among those do not share his particular skill set. He isn't being paid the big bucks to retreat into his bunker, never again to see the light of day.

  46. Frankly that's a plus by Anonymous Coward · · Score: 0

    Most 'modern' UI's are hellishly disfunctional. Fashion over function everywhere.

  47. Re:No thanks [MS Ribbon] by Tablizer · · Score: 1

    Both the old style and ribbons did that. The biggest problem with the ribbon is that it's a screen real-estate hog.

    Other than that, the ribbon hasn't improved anything I've noticed. The UI was rather arbitrary before the ribbon and it was arbitrary afterward also. In that case, don't move stuff. You get used to the arbitrary positions and memorize them. When the ribbon came along, I had to relearn it all.

    All those options should be "googlized" so that one can search options based on key-words and synonyms. There's too many for hierarchical menus to be effective.

  48. No. by Anonymous Coward · · Score: 0

    No, you shouldn't use it just because it's free. You should use it because it's Free.

  49. Tools by darkain · · Score: 3, Interesting

    The problem is that open source developer tools are suited for source code over all other aspects of projects. This isn't just a problem with UX/UI design, it is also a problem with technical writing for documentation, marketing, user interaction, the whole nine yards.

    Right now, please, tell me the best way to submit a conceptual UI design for an application into a git repository? Do you just create a PSD file and submit it? Then when someone else edits the PSD, how do you diff it? How do you easily track revision changes of visual assets?

    In the closed source world, we have asset management systems that work in parallel with our source code management systems. But this is something that isn't common within the open source world. On top of this, great design is quite possibly much harder than great code. With code, it is easy to run new changes against unit tests to ensure that things do not break. But with layout changes, small or overhauls, how do you test them? They are subject highly to opinion more so than pure fact.

    On top of this, take the general nature of open source projects in general. There are often many hoops to jump through to even push a fix for a confirmed bug after discovering it. Just one example (but this has been par for the course all along), I discovered a simple but critical bug in the MariaDB database server returning incorrect results on a SELECT statement. The test case was extremely simple and verified within an hour or two of the bug report being submitted. A couple weeks went by, no work happened on it. I decided to pull down the MariaDB code, hunt down the bug, fix it, and push the change to their git repo. The entire change was only modifying a single if statement condition. The approval process missed several releases of their software and took months, and countless chats in their IRC channel as well. If this is what it takes to get a single simple bug fixed, just imagine what someone would have to do for a serious change like UI cleanup and overhaul of a major application?

    On top of that, just read the comments throughout here on Slashdot on this article. The main opinion is that UX/UI design is just "change for the sake of change" - which is apparently inherently bad. But take a step back and think about this: We're about to hit the year 2016. When are we finally going to have "The year of Linux on the Desktop?" We've been trying to push that concept for over a decade. But what is preventing it? Absolutely horrible UX/UI design, that is it. Linux itself may have almost every feature of Windows/OSX, but the elegance of being able to access and use those features is absolutely horrible from someone that doesn't already know Linux. Now look at Android, Google took Linux and re-imagined the UI from scratch, and now it is widely used and successful. It is intuitive and easy for novice users. They don't even need to know it is Linux at the core, it shouldn't matter. The interface is sleek, clean, and simple (save for some bastardizations that some of the handset makers and carriers screw up)

    If you want the ultimate test of good vs bad UX/UI design, it is actually quite simple: have people sit down that have absolutely no idea how your program functions. They've never seen it or used it before. And have them attempt to use it with zero supervision. Watch how far they can get. See what all they can do. Look for trends and patterns in their usage. Find where people are getting frustrated, and try to make it simpler. This is what Microsoft did back in the '90s to create the start menu and start button. Check out the history of Windows Chicago: http://oyvind.servehttp.com/wi...

    1. Re:Tools by snooo53 · · Score: 1

      Agree about the issues with updating software and UI. However, UI isn't holding Linux back, or at least hasn't for a long time since the days before KDE and Gnome. What's holding back the popularity of Linux on the desktop is that even technical people get tired of dealing with the same problems that we've had for years. Hardware compatibility and ease of software installation/upgrades are easily the #1 and #2 reasons for the failure of Linux to reach even a fraction of desktop marketshare. Combine that with lack of general intuitiveness for solving problems (no standard control panel, dependencies, lack of documentation) and this is where it falls flat. Even technical people get tired, and just want something that works!

      With the disaster Windows OS has become since Win7, Linux should have a shot, but until there is a serious effort to fix these issues (or even try to standardize across the most popular distros) this is a pipe dream. Standard hardware like the RasPI has helped in a few niche applications to solve the hardware issue, but something like this desperately needs to happen on the higher end. As for software, I'm not sure what can be done without a huge overhaul which will likely get bogged down for the same reasons you mention for UI changes! It's a mess all around, but maybe someone will figure it out...

      --
      The sending of this message pretty much inconveniences everyone involved.
    2. Re:Tools by gustygolf · · Score: 1

      I discovered a simple but critical bug in the MariaDB database server returning incorrect results on a SELECT statement. The test case was extremely simple and verified within an hour or two of the bug report being submitted. A couple weeks went by, no work happened on it.

      I've found that a large amount of open source projects are run by developers who don't actually use their bug tracker. They don't read the bugs. They don't act on them. Every twelve months you get someone commenting "does this still apply to version xyz? if not, we can close this" in batches, trying to clean the bug tracker. It bloody well applies to version xyz -- the developer hasn't actually touched any of the relevant code in the past two years, has he?

      A couple of years later you get "sorry, the tool abc has been replaced by tool def and we're closing all bugs filed against abc..." (I'm looking at you, GNOME...)

      --
      "Slow Down Cowboy! It's been 58 minutes since you last successfully posted a comment" -- slashdot, driving users away.
  50. Re:You can fix programming problems with good desi by Anonymous Coward · · Score: 0

    As a dev, I want every possible option and every possible option to be exposed to the user, 'cause that's how I think as I'm programming.

    That's a load of crap. There's nothing inherent in being a developer that makes you want to do that.

    You could just as well say:

    As a dev, I want every possible option, and to have them configurable through a file on the filesystem, 'cause that's how I think as I'm programming.

    or:

    As a dev, I want no options whatsoever, because I've already made the correct decisions while I'm programming

    In reality, if you're adding anything to a program, whether it be an option or functionality, you need to understand why you're adding it, when it will be used, and whether or not it's optional or necessary.

    There's no magic to user interface stuff, it's just another problem domain to understand and address - at least on the functional side. You may not necessarily have the artistic ability to make it look shiny, but you should be able to make it _work_.

  51. Redit of last sentence by dbIII · · Score: 1

    there's still very little similarity between even that use and a text editor.

  52. Adobe? by U2xhc2hkb3QgU3Vja3M · · Score: 1

    You mean the same Adobe that can't even follow the keyboard shortcuts standards of the OS itself? THAT Adobe?

  53. Re: No thanks [MS Ribbon] by AvitarX · · Score: 1

    If memory serves, double clicking the ribbon title where the menu items used to be collapses the ribbon.

    I like some of the ribbon (context sensitive tool bar part), but don't like the difficulty to find infrequently used things (eg, setting print area in excel).

    I wish they just did a context sensitive tool bar and a traditional menu.

    --
    Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  54. Re:You can fix programming problems with good desi by Anonymous Coward · · Score: 0

    The interface should be as simple as is necessary, but no simpler. Hiding things is fine, but they have to be discoverable without going snipe hunting.

  55. Re: No thanks [MS Ribbon] by Tablizer · · Score: 1

    It's annoying to keep collapsing and uncollapsing the ribbon. Also, the old-style tool bars were ALSO context sensitive (in some software). That's not something new to ribbons.

  56. UI/UX meets the hammer by istartedi · · Score: 3, Interesting

    Designer: We've designed a new hammer. We've moved beyond the traditional "head and handle" paradigm. Meet: EggHammer. A simple egg-shaped piece of iron that you hold in your hand with a small flat area on one end. No handle. No join to wear out. Simple. Elegant. The egg shape fits in the palm. The flat end hits the nail. Best of all, you can put it on the shelf and it will stand there as an objet d'art resting on the flat surface. $199.00.

    Carpenter: Dafuq? All the force from pounding goes right into my wrist like this. It's like pounding nails with a rock. What the hell are you babbling about? When I'm done with my hammers I hang them on nails I pounded into this board... with a hammer that doesn't suck rocks, which is what you're trying to sell me for TEN TIMES THE PRICE OF A REGULAR HAMMER.

    Designer: you don't understand design.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  57. Customizable by Tablizer · · Score: 1

    How about allowing the user to customize the interface to some extent. Here's some notes that use web browsers as examples:

    http://c2.com/cgi/wiki?UserDef...

  58. Re:You can fix programming problems with good desi by thegarbz · · Score: 1

    What ever happened to the "Advanced Options" checkbox?

  59. For example - software installers on MS by dbIII · · Score: 1

    they inject their own ideas and follow what's popular

    Such as recyling the classics into a pointless roadtrip of a GUI.

    Do you want to install?
    Do you want to accept the licence?
    Do you want to click on a box?
    And another box?
    Burma Shave

  60. Perspective by jandersen · · Score: 1

    Beauty is in the eye of the beholder - to me, the UI of cat and vi (the old vi, not vim) are far more attractive than any GUI. GUIs have so much more scope for getting it wrong; they so often end up feeling like an overstuffed, Victorian living room with arsenic in the wallpaper (see https://en.wikipedia.org/wiki/...). To make a good GUI, concentrate on simplicity, extensibility and convenience; an interface that is good to use will be naturally beautiful.

  61. Start by adhering to "standard" by aepervius · · Score: 1

    Like it or not but people coming from the main OS, windows, expect the system button (minimize, close etc...) on the right side. So why the heck shift it in the left side in ubuntu ? You rise the difficulty of somebody switching or tying to. That is one example among others. And don't tell me "you can switch". Yes I know that after googling. But somebody trying ubuntu will not. Interface similar to what is the user standard should be the default.

    --
    C. Sagan : A demon haunted world:
    http://www.amazon.com/gp/product/0345409469/
    visit randi.org
    1. Re:Start by adhering to "standard" by Shados · · Score: 1

      Can blame MacOSX for that one.

  62. Out of date. by jellomizer · · Score: 1

    The problem we have is the change in behavior in computing.
    For the stuff we use to have desktops and laptops for had been moved down to tablets and smart phones.
    Why? The performance on these devices are getting very decent, the price is affordable, they have long battery life, and are very portable.
    The Bill gates vision of a PC for every home, is obsolete, today most people don't need what we call a PC, A small computing device is what they need and want for daily usage. Now what we call PCs now are less of a personal device but more of workstation to get real computing work done (also playing high end games).

    This means that good 1990's and 2000's UI rules are now in flux. A lot of things are still in experimental phase now.

    However in my opinion, they should really separate Workstation UI with Personal UI.

    Work Station UI means we should take advantage of larger screens, make it easy for a person to work on one project while at a quick glance monitor others that are going on, the ability to reference other material, and roll back and merge changes over time.

    The personal device market, we are normally working on a single app, however with notifications and alerts to let us know something may ask us for distraction. Make it easy to organize clutter as we collect more apps, and find and use them quickly.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  63. GUI Design can be done Right by golodh · · Score: 0
    The problem is that you don't want GUI design, you want *good* GUI design.

    Just compare the look and feel of an iPhone with that of a standard Android phone. It's better.

    Unfortunately GUI design is hard to get right. It takes both talent and effort, and lots of it. It's easy to get it wrong.

    For better or worse, many FOSS projects have neither. Interfaces are put together by coders. I would like to point to the Gnome desktop as an example of a lot of design effort gone wrong, and to the KDE desktop as an example of where coders have run amuck with the GUI.

    As a browser I way prefer an "old" look (Seamonkey) over Firefox, so in that sense I'd say you're right.

    The problem is: where to get good design? It's rare to find an enthusiastic FOSS coder who can do a decent GUI job, and even rarer to find a decent GUI designer who'll go through the pain of trying to take charge of a GUI design of a FOSS project. It's more frustrating than herding cats.

    For better or worse, this is the one area where corporate software development may have an edge of FOSS: design standards can be (and usually are) imposed across a product or a product range. Not a guarantee for success of course, but often better than FOSS offerings.

  64. Re: No thanks [MS Ribbon] by Half-pint+HAL · · Score: 1

    If memory serves, double clicking the ribbon title where the menu items used to be collapses the ribbon.

    I like some of the ribbon (context sensitive tool bar part), but don't like the difficulty to find infrequently used things (eg, setting print area in excel).

    I wish they just did a context sensitive tool bar and a traditional menu.

    The big problem with the ribbon is that it's not quite as context-sensitive as it claims to be. The section of the ribbon that's open is often simply the last one you used, unless it's no longer applicable to the context you're in. If it's a global option (home, page layout or similar) then it's available in all contexts. There were times I'd been working away in Word or Excel for over quarter of an hour without need of the ribbon (using keyboard shortcuts and the context-menu key for all my edits), and then when I needed to go to the ribbon for something, my flow would be broken by the fact that I had to re-orient my mental context to the currently open ribbon. I couldn't work on auto-pilot like I used to. Context-sensitivity should mean that my first available action is defined by the context, but with ribbons, that ain't so.

    --
    Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
  65. The real custerfuck by sad_ · · Score: 1

    the real clusterfuck of UX design can be found in so called 'enterprise' software or in-house developed applications.
    my god, calling those horrible is still giving them too much credit.

    --
    On a long enough timeline, the survival rate for everyone drops to zero.
  66. most people don't see it as a tool by Anonymous Coward · · Score: 0

    Most people use computers as an appliance. They don't use fridges to freeze genetic samples at a certain consistent sub-zero temperature, but instead use them to keep ice cream cold enough. Those same people just want to surf the web and open some apps without having to struggle with it, and seek familiarity in design - the visual vocabulary if you will - to access information. The GUI as a "grammar" for language is ever-evolving as text-speak, and the issue is the perception of open source being ugly because it follows the need of engineers, the same ones who over-engineer remote controls with 20+ unnecessary buttons (most of the time people use power, volume up/down, channel up/down).

    Either way, /.'s inability to see beyond themselves is not surprising, especially on the topic of UX.

  67. Re:You can fix programming problems with good desi by Anonymous Coward · · Score: 0

    Then why do the silly buggers REMOVE items rather than hide them?

    Oh yes, they don't use them so if they take them out they don't have to maintain them.

    Thanks, GNOME morons!

  68. Was about to say the same thing by HalAtWork · · Score: 1

    Here comes a new idiot on a crusade to change all our UIs just for change's sake. The reason why I went with Mint Linux was specifically because they are striving to keep the UI *the same.* All the apps I use have had the same UI forever and it's great! I can get work done.

  69. Of course it's poor... by Anonymous Coward · · Score: 0

    ... because open source devs care about getting more devs, not about users. Every single time I've been in an open source project and make a suggestion that would be useful to users, it's the same line. 'We don't care about users, we care about devs."

  70. Narcissistic language by Anonymous Coward · · Score: 0

    I cringe when I hear anyone claim they can design an experience. The designer designs a human-machine interface, the user produces his or her own experience when interacting with it. A good interface will generally result in a good experience, but people aren't identical and their experiences aren't either. I enjoy some interfaces the majority of people have trouble with and I dislike some interfaces the majority seems to love. Can I complain to the designers of the last category because they annoyed me on purpose with a bad experience? Or was what I experienced not part of what they designed? If it wasn't, they shouldn't call themselves user experience designers.

    The language that claims that a designer actually designs what the user experiences sounds arrogant, self-centered, narcissistic. It doesn't sound like the kind of designer I would actually want to hire.

  71. What are UX designers smoking? by Locke2005 · · Score: 1

    Our UX designer decided that a "disabled" button isn't a button that does nothing, but rather means a button that, when you click on it, tells you why you shouldn't click on it. Not a bad idea, but it flies in the face of the last 30 years of GUI design. And of course, the UX team is always right, and you have to implement everything exactly the way they said... even when they reverse themselves and tell you to implement the exact opposite of the way they told you before.

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
  72. Re:good UI is hard, more designers isn't the probl by NormalVisual · · Score: 1

    Most open source projects just don't have enough people with enough time to devote to that last 10%.

    Then on top of that, you'll sometimes find that the project leader isn't interested in fixing blatant usability issues. Hell, with some projects it's hard enough getting legitimate bug fixes accepted, much less a UI change that someone will take as a personal affront to their self-esteem.

    --
    Please stand clear of the doors, por favor mantenganse alejado de las puertas