Live data from Hacker News

The Decline of Usability

datagubbe.se

641–650 of 719 posts

Re: The Decline of Usability

#641
post #194

Earlier quoted context omitted.

Having rarely seen a VCR that wasn't flashing "12:00", I came to the conclusion that a clock was simply feature bloat.

One of the arguments, given in the Supreme Court, by Mr. Rogers, to permit the VCR to be legally owned (I know how crazy this is sounding but it's real) was to time shift programming ... which requires a functioning clock. Fred Rogers, 1984: "I have always felt that with the advent of all of this new technology that allows people to tape the 'Neighborhood' off-the-air ... they then become much more active in the prog…

"https://en.wikipedia.org/wiki/Sony_Corp._of_America_v._Unive.... "

Ha, reading that link now one feels a delicious sense of irony. Imagine how Sony would react today seeing that it has become one of the biggest purveyors of video/movie content. ;-)

Re: The Decline of Usability

#642

Earlier quoted context omitted.

I tried to power off an iPhone today for 5 minutes, failed, and just gave up. Why Apple, why would you make this simple action so damn obscure.

Wait, is it not press-and-hold power like on Android?

you have to press the "power" button and a volume button afaik

Re: The Decline of Usability

#643
post #607
post #517

Earlier quoted context omitted.

Care to explain how to apply that filter rule?

In ublock origin add a line in "My Filters" for: www.google.com##[id^=ed_] I only created this today so I'm unsure if the ids change over time or if people get different ids for sections but it's been solid so far.

Oh this is cool! Have been using ublock for a while and didn't know you could use it to block particularly annoying things like this. Thanks a bunch!

Re: The Decline of Usability

#644
post #224

Earlier quoted context omitted.

Not really, that's more a cliche. I set the clock on mine to tape programming when I wasn't there, and if anything it was probably easier than setting clock radios and watches now.

I was a child during the heyday of VCR, but I don't think any of my family was aware of timed recording. The whole concept just didn't exist in our lives until Tivo. Non-obvious features plus buying things second hand just meant you never learned everything your stuff did back before you could find manuals online.

"Non-obvious features plus buying things second hand just meant you never learned everything your stuff did back before you could find manuals online."

That's the outrageous point. You shouldn't need manuals for operation of ordinary domestic appliances! If you do then you automatically know its design is substandard!

(The only reason you should need a manual is for some info or maintenance function that's not normally associated with its user-operated functions.)

Re: The Decline of Usability

#645
post #516
post #500

Earlier quoted context omitted.

Linux GUIs have always been worse than Windows as far as I remember (going back to the mid 90s).

That's very subjective, and not at all related to the point I was making. It wasn't about the niceness of GUIs. Over the last decade, we have experienced a sharp loss of control and had certain entities become almost absolute dictators over how Linux systems are permitted to be run and used. Linux started out quite clunky and unpolished. It could be made polished if you wanted that. But nothing was mandatory. Now tha…

I'd be fine with an "UI dictatorship" or standardization if it gave us better UI and UX. Gnome's "dictatorship" has only brought bad experiences and inappropriate interfaces.

Re: The Decline of Usability

#646
A friend of mine nailed the problem. His theory: for most apps the user is the commodity; not the software!

This is the number one reason why usability of software is not improving and often even declining. The other is feature creep. I'll get to that later. Caveat: I will be generalizing a lot. :)

For the first point —

In the case of commercial software this is obvious. You get paid an hourly rate and the company buys software that you then use. Aka: you are not the one deciding which software to buy. How much you enjoy the experience of using it and how productive your are while doing so is thus not really important for the vendor.

In the case of open source software you commonly do not pay for the software too. The software is developed by people for various reasons. They may use it themselves or they just like working on it. Again – if you have an issue they do not really have reasons to care that much.

Feature creep —

One of the things that makes a developer very happy is adding a feature to a software and exposing it to the user. As a developer myself I know the feeling. It's wholesome, warm, fuzzy.

But when you expose a feature you need to add a user interface to this feature. This is the most difficult part. The number of parameters driving a feature is also called a 'parameter vector'. The more publicly exposed dimensions such a vector has the more difficult the feature is to use.

A feature that has ten parameters may be useful to 99% of users if only three of these ten are exposed. The rest can have magic numbers in the code. Adding another seven dimensions to the publicly exposed parameter vector of a feature to cover 100% of use cases is a bad idea.

Deciding these things requires intricate understanding of the problem space from the user's side. Most developers are not good at this. And more parameters added to a UI somehow feels better to most people. Even though they do understand that this can be counterproductive.

So my friend had this analogy: imagine if you got paid to use a mobile phone. Imagine your government bought phones from Apple, Samsung; whoever. And then you got paid for using them. Do you think we would have something like an iPhone or modern smartphones? Unlikely. We would have crazy awful phones from the pre-smartphone era. Probably with much worse UX than some Nokia or Ericsson phones had at the time just before the iPhone appeared.

This is the situation we have with most of the common closed- and lots of open source software. Again: I am generalizing here.

On the bright side: software that needs to fight for its user base – whether open or close source –, often has better usability.

And certainly: for everything I said above there are countless counter examples. But the overall trend seems obvious to me. I agree with the author of the article 100%.

Well, maybe I'm just grumpy and old too. :]

Re: The Decline of Usability

#647

Earlier quoted context omitted.

Between this and https://stopthemingmy.app/ and the various other systemd/freedesktop “anti-hacker” initiatives, I’ve been finding Linux to be more and more becoming the opposite of the operating system I’ve used for the last 20 years.

Man there is not space on this comment box or time for all the criticism that link deserves. >Icon Themes can change icon metaphors, leading to interfaces with icons that don’t express what the developer intended. Icons were never sufficient metaphors to start with which is why we have text labels. >Changing an app’s icon denies the developer the possibility to control their brand. What does this even actually mean.…

[deleted]

Re: The Decline of Usability

#648

Earlier quoted context omitted.

A cold boot means shut off all power to the device. The normal "off" button the iPhone puts it in standby mode, not off. This is so it can still listen for calls.

I tried to power off an iPhone today for 5 minutes, failed, and just gave up. Why Apple, why would you make this simple action so damn obscure.

My iPhone 10 locked up hard a few days and I couldn’t get it to turn off using the standard method.

After some digging, I found a new trick that I guess is implemented at a lower level: press and release volume up, then volume volume down, then press and hold the main button until it powers off.

Re: The Decline of Usability

#649
post #229

Earlier quoted context omitted.

If they couldn't make it easier to set I think the clock should have been less prominent. It's necessary if you're doing a scheduled recording. It's too bad time sync over power lines didn't catch on widely (or broadcast over the radio). It would still be saving everyone from changing their digital clocks during DST.

Do you not have a radio clock? They're common in Europe, on a midrange bedside clock for example, and typical office/school clocks. I remember we were foiled by one at school, when someone set the clock 15 minutes forward when the teacher wasn't looking. The hands could only move forward, so a few minutes later they started spinning 11½ hours further forward to set the correct time. https://en.wikipedia.org/wiki/Radi…

Interesting. I think I've seen those things, but I've never bought one. I was expecting this tech would be built into microwaves, ovens, and cars by now.

Re: The Decline of Usability

#650

Earlier quoted context omitted.

No one wants to take the time to learn the hard native UI development processes, so we just wind up throwing some shitty angular SPA application into electronjs and calling it a day. That's partly because the native development processes are so unnecessarily awkward, particularly on Apple platforms. It's also partly because most native development processes only give you software that runs on one platform at the end.…

> native development processes are so unnecessarily awkward, particularly on Apple platforms. Can you elaborate? For me it's launch Xcode, new project, hit run and off we go to the races.

For example, getting a simple iOS app into the App Store means not only developing (or at least building) on Apple equipment but also jumping through Apple's hoops and paying Apple in multiple ways and still running the risk of being kicked out.

Writing a web app to do the same thing has exactly none of those downsides, and with relatively little effort it supports Android devices and users with larger screens on laptops or desktops running any major OS as well.

Post reply on HN