(no title)
Underqualified | 3 years ago
I guess they also make more sense to management since it looks like something they could do themselves, or at least understand.
Underqualified | 3 years ago
I guess they also make more sense to management since it looks like something they could do themselves, or at least understand.
mike_hearn|3 years ago
Web tech broke all that:
- UI was/still is very high latency. Keystrokes input whilst the browser is waiting do not buffer, unlike in classical mainframe/terminal designs. They're just lost or worse might randomly interrupt your current transaction.
- HTML has no concept of keyboard shortcuts, accelerator keys, menus, context menus, command lines and other power user features that allow regular users to go fast.
We adopted web tech even for productivity/crud apps, because browsers solved distribution at a time when Microsoft was badly dropping the ball on it. That solved problems for developers and allowed more rapid iteration, but ended up yielding lower productivity than older generations of apps for people who became highly skilled.
hnick|3 years ago
All of these (except logging on to the same data from all my devices, which is nice) benefit the developer at the expense of the user.
tomcam|3 years ago
HTML has had a limited concept of accelerator keys for years, but it's not pretty:
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_att...
tremon|3 years ago
Scoundreller|3 years ago
It doesn’t help that the evaluators for a new system will also approach from the perspective of a new user, even though none of them will be a new user in some months.
I’ve so wanted to create auto-hot-keys for many tasks, but end up having to use (x,y) clicks where I get boned every design touch-up (deliberate or side-effect of another change).