Not to mention that WindowServer seems to take 100+% cpu since the upgrade. Also I can't paste filenames in the save file dialog in some apps. And the URL field in Safari is just weird. My computer was running so slowly that I had to minimize transparency in system preferences somewhere. I think I also turned off opening every app in its own space. And I hid the icons on the Desktop in Finder settings somehow, which…
Make macOS consistently bad unironically
161–170 of 398 posts
Re: Make macOS consistently bad unironically
#162Earlier quoted context omitted.
The biggest flaw is that the system is opinionated, so you cannot change anything you dislike.
It’s not only that it’s opinionated, it’s that it’s idiosyncratically opinionated. It would be different if it had a boring, middle-of-the-road opinion.
Re: Make macOS consistently bad unironically
#163This isn’t a part of macOS 26 that bothers me, honestly. I don’t spend a lot of time stacking windows and measuring their corners.
Re: Make macOS consistently bad unironically
#164Earlier quoted context omitted.
> compared to Windows I never said that
Well sure we can compare it to niche OS like Linux or vaporware. But without comparison then we probably aren’t taking into account the real life complexity of a desktop OS. As a related anecdote, my friend said my car was ugly. I asked him what cars he thought looked good. He said “I don’t like cars”. As a result I realized his opinion was worthless
Re: Make macOS consistently bad unironically
#165Earlier quoted context omitted.
Yeah, anything that has an MDI metaphor going on should be ran fullscreen. Otherwise, what's the point? If the idea is to use the OS desktop space as the application window organizational space, then don't let people make apps that have different document panes. This goes towards something that I've felt for a little while: at some point in time around the early 2000s, operating system vendors abdicated their respons…
Opera had tabs. Tabbed under Unix had tabs. Dillo had tabs. TCL/TK had damn tabs in 1997.
Re: Make macOS consistently bad unironically
#166Earlier quoted context omitted.
Yeah, anything that has an MDI metaphor going on should be ran fullscreen. Otherwise, what's the point? If the idea is to use the OS desktop space as the application window organizational space, then don't let people make apps that have different document panes. This goes towards something that I've felt for a little while: at some point in time around the early 2000s, operating system vendors abdicated their respons…
Opera had tabs. Tabbed under Unix had tabs. Dillo had tabs. TCL/TK had damn tabs in 1997.
Re: Make macOS consistently bad unironically
#167Between the rounded corners that don't reach the edges of the viewport, and the behavior when opening a new app for the first time, it feels like Mac's UI is optimized around the assumption most users won't expand windows to fill the whole screen, but rather leave them half-sized somewhere in the middle. Does anyone actually do this? Especially for heavy-duty applications like my web browser and IDE, this has always…
> it feels like Mac's UI is optimized around the assumption most users won't expand windows to fill the whole screen, but rather leave them half-sized somewhere in the middle IMO, this has been their assumption for years, and it actually turned me off when I tried getting used to Mac circa 2006-2007. Coming from Windows at the time, I just couldn't get over a weird anxiety that my application window wasn't maximized,…
Re: Make macOS consistently bad unironically
#168Between the rounded corners that don't reach the edges of the viewport, and the behavior when opening a new app for the first time, it feels like Mac's UI is optimized around the assumption most users won't expand windows to fill the whole screen, but rather leave them half-sized somewhere in the middle. Does anyone actually do this? Especially for heavy-duty applications like my web browser and IDE, this has always…
Re: Make macOS consistently bad unironically
#169Earlier quoted context omitted.
It did, but those were static tabs. It was pretty easy to create tabs as a form of sub-organization. But the treatment of tabs as documents was new-ish to Chrome/Firefox. Other applications treated multiple, concurrent document views as whole, resizable, sub windows inside of an "MDI" panel. Look at how older versions of Word, Excel, and Visual Studio worked. The tool trays stay consistant as you move between documen…
Virtual desktops in Unix predate Visual Studio. I'm pretty sure there was a concept of tabbed interfaces somewhere in the Amiga or BeOS or any other OS. https://en.wikipedia.org/wiki/Tab_(interface) Don Hopkins himself can enlighten us about it (NeWS) better than me literally anyone in this thread, jut wait.
Re: Make macOS consistently bad unironically
#170Between the rounded corners that don't reach the edges of the viewport, and the behavior when opening a new app for the first time, it feels like Mac's UI is optimized around the assumption most users won't expand windows to fill the whole screen, but rather leave them half-sized somewhere in the middle. Does anyone actually do this? Especially for heavy-duty applications like my web browser and IDE, this has always…
I would in fact say that the culture of not maximizing windows was a small reason why I switched to Mac OS X in the early 2000s.