4 ms·
The proposals put forth in the article are lacking any affordances common place in the nineties and obliterated from "modern" and "beautiful" "design systems" o
by cosmotic 7y ago
The proposals put forth in the article are lacking any affordances common place in the nineties and obliterated from "modern" and "beautiful" "design systems" of the future. Why has so much work been put into "moving forward" to a dystopian unusable future instead of backpedaling back to a past where everything was empirically more usable?
I would prefer specific descriptions of changes in articles like this. Being "modern" or "beautiful" mean thing to me except "probably work poorly and look worse compared to the same thing twenty years ago".
For example, "The new theme is more consistent with Windows 10 and iOS than the previous look and feel. However, it still doesn't perfectly align with native controls so users will still have trouble learning an adapting."
I don't see how 100% native control implementations isn't the target here. Developers and designers wanting to steer the look of a control toward their application or website will still have the same amount of work cut out for them and will still have to fight an uphill battle to keep their applications looking the way they want. Developers and designers wanting an as-native-looking-and-feeling control will now have to augment the new designs to steer them toward native, something the user agent should be doing.
- jimrandomh 7y agoUsing native control implementations in a browser isn't really an option. They make a lot of assumptions about how rendering works and how input events are routed which don't hold up inside a browser.
- jfkebwjsbx 7y agoI guess the parent was referring to re-implementing them within the browser. In other words, not using the actual native one but creating a fake one that looks and behaves like the native one.
- saagarjha 7y agoWebKit uses native controls on macOS. I think it does when GTK is available, too.
- userbinator 7y agoI'm pretty sure browsers in the 90s used native UI, or at least IE did.
- ygra 7y agoOnly for the select element. And that's a major reason why it was so broken amidst all the browser-rendered content.
- userbinator 7y agoWhy has so much work been put into "moving forward" to a dystopian unusable future instead of backpedaling back to a past where everything was empirically more usable? My personal theory is that it is exactly what it says it is: they are slowly making things unusable, because they want to take control away from you. Like all the other UI dark patterns and such, they don't want you to think. They don't want you to be able to make your own choices (remember when UIs were actually customisable? Now there's disturbing amounts of praise for only "now we have a dark theme!") They want to extract as much "value" as they can out of you. They want you to be the used.