Live data from Hacker News

The struggle of resizing windows on macOS Tahoe

noheger.at

91–100 of 1001 posts

Re: The struggle of resizing windows on macOS Tahoe

#91

I swear, this reign of visual artists as dictators has to stop. I'm sure people noticed this issue internally and brought it up but some thing by some designer was seen as biblically sacred and overruled all reason. I've been at companies were you get severely punished... sometimes fired for subordination for fixing an obviously broken spec by a designer emperor. It's normal to be "I guess 2+2=5 here, whatever" as if…

I know enough people at Apple who are at the mercy of the overlord design teams, and it sounds exactly like what you described

Re: The struggle of resizing windows on macOS Tahoe

#92

Earlier quoted context omitted.

Windows 8 was when Microsoft tried to cater more towards Windows-on-tablet use cases. Which lead to everyone, including desktop users, having a fullscreen phone-style app menu take the place of the old start menu. This, for desktop use, is obviously quite disruptive and was hated by everyone. They addressed most issues in the 8.1 update, like a year later I think.

You know what was worse than desktop users? Server users via RDP. There was no start button. There are no screen edges to swipe in from. Hot corners are really hard to hit. I still can't believe somebody said "yes, good idea" to using that UI for Server 2012.

I RDP'd into a Windows Server VM a year or so ago and got a full-screen popup for Edge or some shit like that.

If that wasn't bad enough, the popup was a web view, meaning none of RDP's acceleration/client-side compositing was in play and I was greeted with a ~1fps slideshow.

Re: The struggle of resizing windows on macOS Tahoe

#94
post #40
post #26

Earlier quoted context omitted.

Not to beat on my own drum but as a mac convert from the days of Tiger I saw the writing on the wall from miles away. Still on iOS 18 and macOS 15 (Sequoia). I was a day one upgrader up until now, never had any regrets but this time things seemed very different. It's worrisome but all is not lost, I'll start sweating for real if next year's releases don't improve things substantially.

The Tiger to Snow Leopard era was fantastic. Things were simple and worked. There was also a great boutique apps ecosystem. Right now, it seems that macOS is going through its enshittification phase, sadly.

> Tiger to Snow Leopard era was fantastic. Things were simple and worked

Was it also great for developers? (Genuine question.)

Re: The struggle of resizing windows on macOS Tahoe

#95
post #82

Earlier quoted context omitted.

MetroUI in Windows 8 was pretty universally panned. I thought it was pretty good on tablets and such, but it left a lot to be desired on desktops and hid a lot of functionality, it went too mobile for a lot of people's tastes. Disclaimer: I was one of the dozens who used a windows phone. The Nokia Lumia 920 was great, you can fight me.

I think a lot of people liked the Windows mobile experience. Shame it didn't quite get enough market share.

Resetting the app ecosystem 3 fucking times by breaking app compatibility didn't help. Windows Phone 7 - Windows Phone 8 -> Windows (Phone?) 10.

Re: The struggle of resizing windows on macOS Tahoe

#96

This behavior is similar to Windows 11. You have to position the mouse just outside the window. It is non-intuitive and awful. These are problems humanity solved over 35 years ago (see NeXTSTEP). Why are these designers breaking basic features that worked for over 35 years?

Fun fact: NEXTSTEP went 10 years without shipping a basic design refresh, except in prereleases (4.0PR1 and traces in 4.0PR2.) This was because it was a good fucking GUI that did its fucking job, and had "usability before aesthetics" as a core design tenet in its developer documentation.

Steve's brain fell out when he got back his throne at Apple. Aqua was a mistake.

Re: The struggle of resizing windows on macOS Tahoe

#100

This behavior is similar to Windows 11. You have to position the mouse just outside the window. It is non-intuitive and awful. These are problems humanity solved over 35 years ago (see NeXTSTEP). Why are these designers breaking basic features that worked for over 35 years?

Call me cynical but I think designers need to occasionally break things that were already solved long ago to justify their continued relevance. Explains a lot of redesigns that make things only worse, reshuffling interfaces, hiding things behind menus in form over function redesigns, etc.

Non-tech people tend to think similarly about developers, breaking things that worked fine until yesterday / last week / last month, for no user-visible benefit.
Post reply on HN