Live data from Hacker News

Make macOS consistently bad unironically

lr0.org

301–310 of 398 posts

Re: Make macOS consistently bad unironically

#301
post #245
post #233

Earlier quoted context omitted.

Windows also has this kind of tiling built-in. It even comes with default keyboard shortcuts.

So does Mac: https://support.apple.com/en-us/guide/mac-help/mchl9674d0b0/... . Obnoxiously, it's part of the recent trend of overloading the Globe/Fn key, so it's hard to do with third-party keyboards.

Can you not change the shortcut?

Re: Make macOS consistently bad unironically

#302

Earlier quoted context omitted.

Vulgarity aside, I can sympathize. For years I've been told by designers that discoverability and intuitive interacting patterns are so important, yet every aspect of modern design focuses so much on minimizing "distractions" that features go undiscovered. We get forced into suboptimal workflows and usage patterns because everything gets over-fitted to the lowest common denominator. This is the biggest reason I love…

This, exactly. Every MacOS app has a menu item explicitly made for this exact thing. It's often the third item in the menu: File Edit View But they refuse to put these viewing options under the View menu item. Why? Why would you not put these really great viewing options under View?

It's under the Window menu?

Re: Make macOS consistently bad unironically

#303

Earlier 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.

It used to be the case with intel macs and their atrocious confluence of cooling system, thermals, and power supply system (the CPU actually was not really to blame).

But when RAPL and similar tools to throttle CPU are used, the CPU time gets reported as kernel_task - on linux it would show similarly as one of the kernel threads.

Re: Make macOS consistently bad unironically

#305
post #9

Between 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 use several non-fullscreen windows over desktop. Stage manager makes switching between them very convenient. But I do use full screen windows, they live in their separate spaces. I see no reason whatsoever to maximise any window without it going full screen mode

Re: Make macOS consistently bad unironically

#306

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…

> Computers have been running thousands of times slower than they should be for decades I've been hearing this complaint for decades and I'll never understand it. The suggestion seems completely at odds with my own experience. Regardless of OS, they all seem extremely fast, and feel faster and faster as time goes on. I remember a time when I could visually see the screen repaint after minimizing a window, or waiting…

> Regardless of OS, they all seem extremely fast, and feel faster and faster as time goes on.

The modern throughput is faster by far. However, what some people mean when they talk about "slower" is the latency snappiness that characterizes early microcomputer systems. That has definitely gotten way worse in an empirically measurable fashion.

Dan Luu's article explains this very well [1].

It is difficult today to go through that lived experience of that low latency today because you don't appreciate it until you lived it for years. Few people have access to an Apple ][ rig with a composite monitor for years on end any longer. The hackers that experienced that low latency never forgot it, because the responsiveness feels like a fluid extension of your thoughts in a way higher latency systems cannot match.

[1] https://danluu.com/input-lag/*

Re: Make macOS consistently bad unironically

#308

Earlier quoted context omitted.

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.

People don't really like apps that stutter.

And maybe that would get enough users to leave or complain that managers might allow some dev time to fix bad behavior.

Re: Make macOS consistently bad unironically

#310
post #153

Earlier quoted context omitted.

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.

Or at least consistent opinions

It seems it'd at least getting consistently bad opinions on it.
Post reply on HN