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
291–300 of 398 posts
Re: Make macOS consistently bad unironically
#292I feel like the only dude on the planet who uses fullscreen workspaces on Mac. The number of times I have noticed the corner of my windows is precisely zero because each important application gets its own workspace, so the window frame doesn't get rendered. Sometimes I'll tile two windows side by side on my external monitor but even then this is a complete non issue for me. Are you guys just running everything on the…
That means there are exactly two of us.
Re: Make macOS consistently bad unironically
#293Earlier quoted context omitted.
I’ve been using Macs for development for 20 years, and even on a small laptop screen I don’t expand windows to fill the screen. So I guess, yes, there are a few weirdos out there at least?
Consider me another weirdo. I don’t know why anyone would use full screen. Even games I want in a window…
Re: Make macOS consistently bad unironically
#294Not 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…
kernel_task using 100% is the system thermally throttling and the OS spamming NOPs to cool the CPU down
Re: Make macOS consistently bad unironically
#295Between 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…
Personally I try and work with that as much as possible, though it’s not always ideal.
Re: Make macOS consistently bad unironically
#296Earlier quoted context omitted.
> Not to mention that WindowServer seems to take 100+% cpu since the upgrade That's because some app is spamming window updates. It's been an ongoing problem for many releases. AFAICT, WindowServer 100% CPU is a symptom, not a cause.
But apps shouldn't be able to hammer WindowServer in the first place. If your app is misbehaving, your app should hang, not the OS window compositor! FWIU there's really no backpressure mechanism for apps delegating compositing (via CoreAnimation / CALayers) to WindowServer which is the real problem IMO.
Re: Make macOS consistently bad unironically
#297Not 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…
kernel_task using 100% is the system thermally throttling and the OS spamming NOPs to cool the CPU down
Re: Make macOS consistently bad unironically
#298Earlier quoted context omitted.
kernel_task using 100% is the system thermally throttling and the OS spamming NOPs to cool the CPU down
I don't know much about CPU internals, but this sounds like bullshit to me. A NOP is still an instruction that uses a cycle - why should that cool the CPU down? The CPU frequency should get reduced to lower the power consumption and hence the temperature.
Re: Make macOS consistently bad unironically
#299Not 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…
QubesOS seems a great migration target: it runs Apps/OS in secure sandboxes - and even with that overhead doesn't seem worse than the terrible MacOS 26 performance.
Re: Make macOS consistently bad unironically
#300People obsess about SIP but just remember that SIP does nothing to prevent the most common type of malware (ransomware). If you use SIP and use package managers (npm, cargo, pip, etc) outside of a VM you are substantially more vulnerable to attack than someone who doesn't use SIP and doesn't use package managers. So if you want to fix your corners, you can do it guilt-free by adopting some better security practices a…
SIP protects the OS, not you nor your files. If you run third party software that can run `rm` of course you're vulnerable to data loss. Apples and oranges. SIP guarantees that you will be able to turn on your computer in safe mode and remove the malware, whereas without it your OS is toast.