I think the author’s use of a 500Hz display covers up or minimizes a lot of issues. It’s really easy to look at this data and say 8ms click to flash is fabulous even though he has an config that does 4ms.
A better way to interpret this data is to normalize by the vsync interval or the swap chain depth. The slowest config is 2 frames slower than the fastest. At 500Hz this is 4ms extra which is likely imperceptible to everyone but elite pro gamers. At 60Hz this is 34ms extra which is pretty noticeable to even casual gamers.
At one point you could have said the same thing about Blizzard, that everything they did was gold. It’s hard to pinpoint where they went wrong, but it’s not clear to me that it was business model or game format related. Like, WoW was a fabulous success from day 1 and it was a live service game.
No, this scenario works fine. Car audio (and UI) can interleave with CarPlay. I can put podcasts on my center screen, my car manufacturer's navigation in the driver's screen, and the navigation prompts will duck the podcast and interrupt as appropriate. This isn't hypothetical or hard, my car does exactly this today.
Right, this is why video parse / decode ought to be sandboxed. Writing secure code for these formats, especially in C, is really hard. I just sort of glanced at the bug in the repo, but it sounds plausible. It certainly wouldn’t be the first of its kind.
I’m not sure what the bug is, but this is a terrible fix. What this is doing is forcing the WindowServer to composite the cursor rather than treat it as a hardware overlay. I suppose the issue must be pretty bad for OP if this helps, but … ugh.
The number is as low as 2. Hell, it may even be 1! I have had a subscription for years, I do not share it, and I read on 2 devices, and they've been hassling me with this nonsense for the past week or so. I'm holding out hope it's just a bug and they'll stop, but if it goes on much longer I will cancel too.
I can tell you that inside Apple, they have something called the standard question, and it goes something like this: “What are you really trying to do?”
If you haven’t personally filed a bug report at feedbackassistant.apple.com, I recommend that you do so. Title it something like “Poor text quality on LoDPI display”, file it in the Displays component, and in the description explain what you’re seeing. Here’s the critical part: you want to attach images showing what looks bad and what looks better, and why the current behavior is a regression and since when (earlier macOS versions for subpixel AA, earlier GPUs for 2x 1x mode). If possible, use the same display, but get an image of historical macOS when it had subpixel AA, macOS with this 2x 1x mode, Windows 11, and then current macOS at the standard 1x mode. I’m not sure screenshots will capture it, you’ll probably need to use a camera.
I know how they think at Apple. If you come at them with a bug written like OP’s blog, they are going to say it behaves as designed. To get them to fix something, you have to be descriptive about what the real problem actually is: the text rendering looks bad. Then you have to explain what used to work and what you’ve tried and bring receipts (the images). Don’t write a novel; write the shortest bug that fully describes the real problem, includes all of the relevant information including macOS versions, hardware info, and display model, and the evidence of the problem, but don’t include a bunch of emotional text or extraneous information (like SkyLight framework reverse engineering stuff).
Now you might say, “I’m not Apple’s free QA”, and you’ll be right. But, consider that you’re spending this time complaining about a problem online and you’ve spent good money on a display you’d like to use and it’s not working the way you want. Fair or not, you care about the outcome, and at this point you might as well take my advice and file a strong bug to make your case. Dupes help, OP should file one too, but be descriptive about the real problem, not proscriptive about bringing back the crazy workaround that they likely intentionally disabled because on the face of it, it makes no sense.
I do know that they read user bugs in the Displays component, because I have filed a few in there recently and they got fixed and they followed up with me about where they were fixed.
Then complain about that. That would make a much more sensible blog post and discussion. Asking for a crazy workaround to a sane problem isn't a great way to get good results, especially with Apple. Beyond the obvious performance pitfall, this scale up to scale down approach will also destroy the appearance of some controls. There is some UI that aims for 1px lines on hidpi modes that will get lost if you do this. It's hardly a perfect mode.
Yes, I would actually be surprised to learn that mode is available on any system. I’ve never seen that anywhere, though I only have a M1 Pro and an M4 Pro (and various Intel Macs).
You’re rendering to a framebuffer exactly 2x the size of your display and then scaling it down by exactly half to the physical display? Why not just use a 1x mode then!? The 1.75x limit of framebuffer to physical screen size makes perfect sense. Any more than that and you should just use the 1x mode, it will look better and perform way better!
Exactly. Their holy war on the App Stores blunted Fortnite’s momentum at its apogee.
On one hand, I admire their chutzpah. The App Store model has weighed down the entire software industry and has prevented entire categories of new products from growing out of infancy due to anticompetitive practices. Everyone, Apple and Google included, would actually be better off without the App Stores in their present form, and I’d love to see them weakened or eliminated.
But on the other hand, Epic actually accomplished very little in their war, and nowhere near what being unavailable on mobile platforms for years cost them.
Additionally, their refusal to go after Xbox, PlayStation, and Switch never made any sense to anyone except for those with a financial interest in those arrangements. The rest of us were just confused — the console App Stores are the exact same model as the mobile App Stores.
I suspect Epic’s actual reason for not going after the consoles was a bit of realpolitik or cowardice depending on how you look at it. They couldn’t afford to be locked out of the mobile and console stores at the same time, so they invented some tortured rationale for why they could pay the console vendors their 30% but not the mobile vendors. But, this muddied their message and they came up mostly empty handed in the end, and here we are today.
You could apply this same reasoning to any feature or technology. Yes there could be a zero day nobody knows about. We could say that about ssh or WebKit or Chrome too.
I hear what you're saying about the deprecation status, but as I and others mentioned, the fact that the underlying functionality is heavily used throughout the OS by non deprecated features puts it on more solid footing than a technology that's an island unto itself.
On the other hand, the underlying functionality for sandboxing is used heavily throughout the OS, both for App Sandboxes and for Apple’s own system processes. My guess is sandbox-exec is deprecated more because it never was adequately documented rather than because it’s flawed in some way.
I admit I started reading with some skepticism. It didn't read like PR, so I assumed I was reading fanfic. By the midpoint, she managed to convince me otherwise.
I think the author is walking a tightrope between convincing the reader that she wrote this herself and that there's more depth to her than what we see on stage or in pop media. Writing this blog is definitely a tougher assignment than doing podcast interviews or behind the scenes videos.
You are right, of course, a good editor could make this better, but I think she's deliberately avoiding that here. A pop star is unwise to fire a good producer without a better replacement, but sometimes they have to bring out the piano and do an acoustic performance live.
Yeah I have tried it for myself. I am limited to 4K60 when using the HDMI 2.0 port on either my M1 Mac mini or M1 Pro MacBook Pro and LG B2 TV. I do get 4K120 with VRR with newer Macs with HDMI 2.1 as well as my Xbox Series X. It has been my understanding that 4K120 with HDR and VRR requires HDMI 2.1, which is why those HDMI 2.0 limited systems don’t work. Not having a Steam Machine myself, I would assume its HDMI 2.0 port would be similarly limited.
Edit: I should add, I do get 4K120 VRR and HDR on the M1 Macs when connected to a monitor via Thunderbolt or Thunderbolt to DisplayPort adapter, and I would expect a Steam Machine to be similar using DisplayPort, but my TV only has HDMI input and so can’t work in this mode (and a Thunderbolt to HDMI adapter doesn’t work either).
There isn’t a single one way to be a dedicated gamer.
Inevitably everyone has finite time and access to games and has to make choices about what to play.
As a Mac guy, I always found the game platform wars weird because even on the weakest gaming platform there are still more good games than anyone can individually play. And even on Windows, probably the strongest gaming platform, you’re still missing out on many significant games.
I totally understand buying a system because it has some game that you absolutely must play. I bought an OG Xbox back in the day because I thought I desperately needed to play Deus Ex: Invisible War when it didn’t come to Mac. Got burned on that one, but at least I had Halo before it came to Mac (and was in the end much better there than on Xbox due to expanded online multiplayer).
What I actually don’t get is folks who have to play the hot game of the week every week. Just seems expensive in terms of money, time, and space for different systems, and you only scratch the surface of the games.
This is a big miss for me. I can’t use my TVs 120Hz VRR mode without HDMI 2.1.
I realize the Xbox Series X is beleaguered at this point, but apart from playing games that are on Steam but not Xbox, I can’t see why I would prefer the Steam Machine.
As a kid, I was marginally decent at competitive math. Not good like you think of kids who dominate those type of competitions at a high level, but like I could qualify for the state competition type good.
What I was actually good, or at least fast at, was TI-Basic, which was allowed in a lot of cases (though not all). Usually the problems were set up so you couldn’t find the solution using just the calculator, but if you had a couple of ideas and needed to choose between them you could sometimes cross off the wrong ones with a program.
The script the author gives isn’t a proof itself, unless the proposition is false, in which case a counter example always makes a great proof :p
A better way to interpret this data is to normalize by the vsync interval or the swap chain depth. The slowest config is 2 frames slower than the fastest. At 500Hz this is 4ms extra which is likely imperceptible to everyone but elite pro gamers. At 60Hz this is 34ms extra which is pretty noticeable to even casual gamers.