imo the metro take of windows 8 wasn’t the wrong approach for its intended market(tablets) it’s just forcing it on desktop/laptop users as well as a boneheaded decision.
They need to stop forcing windows changes for ALL users, including to the users that can’t use said features properly (as it was designed with touch screens in mind, and not everyone had touchscreens). Same idea with the more recent stuff involving Recall. not everyone has AI capable pcs, so its dumb to include the change to all users that will exist on the main branch of the OS, and would apply down the line to windows handhelds as well, who will likely not need recall as a feature as its using up resources. And im not like a person whose like fully Anti AI either, it just has its specific userbase that may need it, and there are others (like with a windows handheld case) that should not have it at all, as it is likely a detriment to battery if enabled by default.
Honestly the metro design language didn’t look particularly attractive for touch screens either. I knew someone with a Nokia Windows Phone, the interface seemed… clunky. Quirky but not in the right ways.
It has to cater to mice and fingers, and so ends up with the lowest common denominator. Can’t have information density because of the butter fingers, can’t have neat swiping gestures because of the mice and especially trackpads. So, big squares and huge buttons, repeat ad nauseum. Like a DUPLO set.
Surely the UI/UX designers and Microsoft knew this, but I guess Ballmer had his way. Meanwhile Valve didn’t have to contend with cranky executives, so they just slapped Big Picture on top of KDE and let use decide when to switch between console mode and desktop mode.
Microsoft keeps doing it, and I don’t expect they’ll do anything different this time. They’ll shove handheld UI into work laptops and piss off a ton of people, and then 5 years down the line they’ll tear out a lot of work that they did and leave behind some remnant bloat
imo the metro take of windows 8 wasn’t the wrong approach for its intended market(tablets) it’s just forcing it on desktop/laptop users as well as a boneheaded decision.
They need to stop forcing windows changes for ALL users, including to the users that can’t use said features properly (as it was designed with touch screens in mind, and not everyone had touchscreens). Same idea with the more recent stuff involving Recall. not everyone has AI capable pcs, so its dumb to include the change to all users that will exist on the main branch of the OS, and would apply down the line to windows handhelds as well, who will likely not need recall as a feature as its using up resources. And im not like a person whose like fully Anti AI either, it just has its specific userbase that may need it, and there are others (like with a windows handheld case) that should not have it at all, as it is likely a detriment to battery if enabled by default.
Honestly the metro design language didn’t look particularly attractive for touch screens either. I knew someone with a Nokia Windows Phone, the interface seemed… clunky. Quirky but not in the right ways.
It has to cater to mice and fingers, and so ends up with the lowest common denominator. Can’t have information density because of the butter fingers, can’t have neat swiping gestures because of the mice and especially trackpads. So, big squares and huge buttons, repeat ad nauseum. Like a DUPLO set.
Surely the UI/UX designers and Microsoft knew this, but I guess Ballmer had his way. Meanwhile Valve didn’t have to contend with cranky executives, so they just slapped Big Picture on top of KDE and let use decide when to switch between console mode and desktop mode.
Microsoft keeps doing it, and I don’t expect they’ll do anything different this time. They’ll shove handheld UI into work laptops and piss off a ton of people, and then 5 years down the line they’ll tear out a lot of work that they did and leave behind some remnant bloat
That’s what I was implying with the elipses, I just couldn’t be bothered writing all that 😅