[ryandrake]

Yea, I think a lot of us old timers do notice these "little things" and it's infuriating when they are missing from the Shiny New Web Version of our desktop apps.

And, like others said, the existence of these niceties does not detract from the experience for non-power users. It's simply a bonus for more experienced users, and these bonuses are slowly going away as more and more developers choose the "give up once the thing kind of works" strategy.

[dotnet00]

I think what makes it worse is that a lot of 'UX' people seem to actively oppose these kinds of power user conveniences because they think they know better than their users.

[devmor]

It’s not that they think they know better, it’s that they know power users are the minority.

Everything is about minimizing expense to an extreme degree to drive “growth” in the current tech economy, so there’s little focus put into things that do not test as an immediate boost to marketability.

[datavirtue]

I wish this was the reason. It's just mediocrity and pure, raw ignorance. A result of throwing bodies into the technology industry in a desperate attempt to get the software out.

[mewpmewp2]

Also power users may be using ad block or opting out of tracking and therefore being left out of the success metrics.

Everything will be optimized towards the clueless.

[vladms]

Considering how much money are poured into AI development would not say that "everything is about minimizing expense". But it is true that user interfaces are not something that will sell your application to the masses.

But to be honest, trying to sell any kind of "advanced software tools" (like compilers or other very specialized tools that provide small gains compared to existing free ones) for "power users" is extremely hard. Was involved in something similar in ~2010 and many power user think they don't need it or they can do it better themselves but anyhow does not want to pay for a complex tool.

Probably the web interfaces is exactly a manifestation of that, many users trying to implement things themselves because they know better. But I prefer writing interfaces with React than with Win32 so I think there is progress.

[canucker2016]

It's also a lowest-common denominator problem.

Which advanced UX do you implement? MacOS? Windows? Gnome or KDE behaviour? CDE?

One could sniff the user-agent and adapt to a recognized OS behaviour but we all see how superficially shallow the UX on the web is. I've given up on expecting anything advanced.

[wruza]

Any UI is as good as its base layer. We wouldn’t have $subj if MS didn’t implement it. But then when you tell them that the browser UI model is just useless crap with smooth animations, you get hellvoted, yelled and thrown fragile css/$()/useX incantantions at.

Which advanced UX do you implement? MacOS? Windows? Gnome or KDE behaviour? CDE?

Browser advanced UX. Not current browser UX, but a hypothetical one which doesn’t suck.

[lodovic]

Accessibility enhancement are not just meant for power users though. Some people depend on those.

[gpderetta]

There will be no power users when you take away all the powers.

[refulgentis]

Yes, UX people do recognize it's weird to have something invisibly act a certain way that disobeys the plain inputs.

[mixmastamyk]

Desktop programmers got these things mostly for free, even if they gave up as soon as it compiled.

Also, I focused mostly on the web, but things like Apple/Gnome removing menus and titlebars are a problem as well.

[refulgentis]

I don't know if this is that clear cut that it's worth making sweeping judgement based on it. I don't think it's a great idea to have it so pressing the same letter twice selects the 2nd item in the list with the same starting letter.

From another fellow grumpy old-timer who appreciates details, this looks more like "undiscoverable alternate mode that is invisible to the user, hacked in by a too clever engineer" than power user nicety

[bigstrat2003]

This is the way I remember it working originally. It wasn't until later that I discovered you could type the letters of something to jump to that. So for me, typing the first letter multiple times was just the intuitive and obvious way to do it.

[wruza]

It is discoverable through “g windows tips and tricks”. Reading articles like that went out of fashion too though. Thing with “power” and “advanced” is that you have to learn, because otherwise that info for all features had to be on screen and there’s only so much space on it.

This whole discoverability bs is what has driven UI into intuitive uselessness for everyone, when there’s actually two groups: first (/one) time users and just users (“power” or not). For some reason modern UX designers think everyone is in the first group. Even if an app is naturally multi-time heavy-use.

[eviks]

> because otherwise that info for all features had to be on screen and there’s only so much space on it.

there's practically infinite space on screen since that space has a time dimension and can also be tied to context which also varies. Like with this feature: you can show a tip on the first few searches within a list, you don't need to permanently keep the explanation on screen. Or you can show a hint with ll by having a different style of the second l or something similar

Undiscoverability is precisely one big reason why these things get axed since they're not used, so forgotten about in other contexts (web, new UI framework etc)

And yes, needing to reading random articles like this is a major fail in discoverability as you decrease reach and increase cost for the many poor users

[ryandrake]

I hate the "discoverability" trend. I don't want discoverable UI. I want UI that is consistent with all my other apps, which I have already learned. I should not have to have an app nudge me to "discover" its oh-so-cleverly-hidden features. I'm not Dora the fucking Explorer, I'm a computer user who expects everything on the platform to behave predictably and consistently.

And while we are at it, "lack of use" is not a good reason to axe features. Some things, by their nature, just don't get used as much but when they are needed they are needed. Product designers have become slaves to their telemetry and metrics, and are letting the tail wag the dog.

[eviks]

I wasn't talking about a trend, but real discoverability, so your rant is misplaced.

> expects everything on the platform to behave predictably and consistently.

and poor discoverability makes this expectation even less likely to be met

Similarly

> "lack of use" is not a good reason to axe features.

But it is a great reason not to implement features in the new framework since you're not even aware of them because they're undiscoverable! (I know, I know, not to you, you've already wasted time doing the discovery the hard way by reading some obscure blog, but then you go teach the devs of those new frameworks!)

Also, what is this imaginary telemetry that is able to track that I want ll to land on llama instead of blindly following invisible-mode#1? It would be awesome if product designers were that competently informed, we would've gotten universally great UIs!

[wruza]

Real discoverability is as real as discoverability of subj, so we’re all misplaced. That bugs me the most, much talks, crap UIs. Empty rationalizing it to death instead of cultivating feature cultures that already work and do not require “design”.

[mixmastamyk]

Probably more historical. My recollection is that lists originally worked that way (same letter many times) for a long time. Then a decade+ later I realized it had become smarter.