News for hackers. Stuff that matters.
Re:macOS 15.8.2 Breaks OpenGL by Aurornis on Sunday October 18, 2026 @01:26PM (#50143212)
15.8.2 isn't released.

This is a report from the developer forums where people are supposed to report these bugs.

The second response in the thread is an Apple engineer acknowledging the bug, assigning a number, and asking the person to retest when new builds are available.

If you only read the comments here you'd come away with a completely different impression of what's happening.

Re:macOS 15.8.2 Breaks OpenGL by modeless on Sunday October 18, 2026 @02:40PM (#50144012)
That's true, but I'm sorry, telling them to test it themselves every time a new release comes out because "I can't comment on known issues or on whether or when a fix might ship" is just stupid. It's a liability-reducing strategy benefiting only Apple, not a nice way to treat customers.

Also, not having a regression test that catches OpenGL being completely broken on many common hardware configurations seems pretty bad. Yes, OpenGL on macOS is deprecated, but guess what, deprecating it was also stupid. It was a legal decision made by Apple lawyers pursuing a particular litigation strategy vs Nvidia that caused Apple's withdrawal from Khronos group. It wasn't a sound technical decision.

Both of these things make it seem like the lawyers are in charge at Apple rather than the engineers.

Re:macOS 15.8.2 Breaks OpenGL by judge2020 on Sunday October 18, 2026 @03:53PM (#50144776)
TBH, I'm not saying "DTS Engineer" isn't an actual Apple engineer, but it feels very LLM-written. For something like that, I wouldn't want it to guarantee that a fix can or will be done in any sort of timeframe.
Re:macOS 15.8.2 Breaks OpenGL by gavinsyancey on Monday October 19, 2026 @02:41AM (#50149114)
> deprecating it was also stupid. It was a legal decision made by Apple lawyers pursuing a particular litigation strategy vs Nvidia that caused Apple's withdrawal from Khronos group.

I'm not aware of the context here but that sounds like an interesting story. Could you give more details or do you know where I could read more about this?

Re:macOS 15.8.2 Breaks OpenGL by modeless on Monday October 19, 2026 @03:08AM (#50149285)
I'm not aware of any good writeups. Neither Apple nor Nvidia wanted to publicize it. Here's the story as I know it:

When Apple decided to make their own GPU, all the other GPU vendors sued them for patent infringement. Apple countersued, and the litigation went on for many, many years. In the case of Nvidia there were also previous legal disputes over liability for Macbook GPU hardware defects, which meant that Apple had cut all ties with Nvidia years prior. This probably led to Apple's legal fight with Nvidia being especially prolonged and vicious.

Khronos Group, which produces the OpenGL and Vulkan standards, has ties to Nvidia. I don't know all the details but it seems Apple's lawyers decided that they would block implementation of any new Khronos standards in Apple products due to the Nvidia connection. As a result the OpenGL implementation in macOS was frozen at 4.1 for many years (dating from 2010 and lacking compute shaders), even prior to deprecation. Of course Vulkan support for macOS was completely out of the question. They also stopped work on Safari's implementation of WebGL 2 (which was left in a half-done state for years until it was eventually pushed to completion by Google engineers including myself). Additionally, Apple successfully maneuvered the WebGPU working group out of Khronos to W3C, and vetoed SPIR-V on the web, eventually resulting in WGSL.

So the legal dispute between Apple and Nvidia had a big influence on the industry. If Apple hadn't been allergic to Khronos standards, in an optimistic scenario we might have had a significantly better Vulkan standard with contributions from Apple's Metal team, Vulkan+SPIR-V support on macOS and iOS, and even SPIR-V on the web, which would have given us a truly cross-platform modern graphics API to replace OpenGL and made writing portable graphics software significantly easier in the last decade.

Of course today all this seems a lot less relevant with the rise of coding agents that can port a codebase or even a binary executable between platforms with a few prompts. So it will soon be a forgotten historical curiosity.

Re:macOS 15.8.2 Breaks OpenGL by pjmlp on Monday October 19, 2026 @04:37AM (#50149872)
The easiness of porting is always exaggerated, first of all, all 8 and 16 bit home computers had their own ways, the game consoles for the most part ignore Khronos, and still there is a thriving market, because game devs contrary to FOSS folks, implement a middleware engine during breakfast, and move on with their lives.

Secondly, thanks to extension spaghetti from Khronos APIs, the portability across devices, OS and computing platforms is hardly much different than coding to multiple graphics backends.

There are hardly any Khronos APIs related content at game conferences, that isn't done by Khronos themselves.

So even without coding agents it has never been that industry relevant, other than on open source communities.

Re:macOS 15.8.2 Breaks OpenGL by eska on Monday October 19, 2026 @06:39AM (#50150715)
I find this pattern so funny. Khronos and Microsoft anticipate 20 graphics vendor APIs, so 2 portable standard APIs are created. The common denominator problem stifles competition and leads to unexposed functionality some vendors have or won’t bother developing because of it. It also introduces a lot of implementation problems that would not exist with vendor-specific APIs. How many vendor APIs were there really back then and now? A handful across industries, less on specific platforms.

I see this pattern again and again. For example in the manufacturing industry there’s a network standard OPC UA. It sucks. It tries to extend to absolutely everything (wtf database interfaces?). Like you say, the “integrators” just write a middle layer and move on with their days.

Re:macOS 15.8.2 Breaks OpenGL by modeless on Monday October 19, 2026 @04:42AM (#50149925)
Games are not the only users of graphics APIs. Anyway, it's true that Vulkan/SPIR-V support on mac/iOS and web would not be a portability panacea by itself. That said, it certainly wouldn't have hurt either. And if portability between all desktop and mobile devices with a single API was a realistic possibility, there would have been more interest in fixing the portability issues that remained. But why bother to care about Vulkan portability when you're going to need an abstraction layer above it anyway for iOS/Metal support.

Point is, the reasons we didn't get any even minimally portable native graphics API this cycle are more legal than technical.

Re:macOS 15.8.2 Breaks OpenGL by pjmlp on Monday October 19, 2026 @04:54AM (#50150012)
They actually are, office software isn't sending rendering command lists to the GPUs.

Anything else is just fine using the OS visualisation widgets on their UI toolkits, and if portability is that much of a concern, pick Qt, wxWidgets or whatever, already solved in the 1990s.

Re:macOS 15.8.2 Breaks OpenGL by lefty2 on Friday October 23, 2026 @09:41AM (#50208849)
interesting story, but the fact that Apple and Nvidia were sueing each other doesn't seem any reason to drop all open standards. I would say they did it because of arrogance - ie. we're Apple and everything we do is better, therefore our graphics API is superior than any other
Re:macOS 15.8.2 Breaks OpenGL by dunder_cat on Sunday October 18, 2026 @01:41PM (#50143367)
I hope it does get fixed, but Apple actually has a bad track-record with another deprecated API, AppleAL (OpenAL). They broke it in a very interesting way in Tahoe where mono-channel audio on Aarch64 (not through Rosetta) did not play and it was broken through all the betas. I believe it actually may still be broken today. The workarounds were either mono-to-faux-stereo channel duplication or switch to openal-soft.

OpenGL is an even bigger deal so I don't see a world where it doesn't get fixed, but I also thought exactly the same way with the previous issue. It seems that Apple does not have any older video games in their testing apparatus.

Some references on the issue:

1. https://github.com/luanti-org/luanti/issues/16499

2. https://support.sega.com/hc/en-us/articles/39540396560145-Ma...

Re:macOS 15.8.2 Breaks OpenGL by eska on Tuesday October 20, 2026 @05:02AM (#50163227)
OpenAL was terrible on Android as well, but audio on Android was terrible at the time anyway. Game developers had issues like explosion sounds playing half a second after the visual effect. Google made excuses for years saying it’s not their fault somehow, while it was fine on iOS, before they eventually fixed a scheduling mistake they introduced.
Re:macOS 15.8.2 Breaks OpenGL by saghm on Sunday October 18, 2026 @01:41PM (#50143368)
15.8.2 isn't released, but the 15.8.2 release candidate clearly is. I don't think think it's that crazy for people to be at least somewhat concerned that a fairly common important library got broken a bugfix release to a maintenance update that came out a month ago for a major version that came out two years ago without anyone internal testing it before publishing the RC.
Re:macOS 15.8.2 Breaks OpenGL by Aurornis on Sunday October 18, 2026 @01:50PM (#50143457)
> 15.8.2 isn't released, but the 15.8.2 release candidate clearly is

That’s how release candidates work.

The headline could have included RC to make it accurate. As submitted it’s pretty misleading.

Re:macOS 15.8.2 Breaks OpenGL by SchemaLoad on Sunday October 18, 2026 @07:11PM (#50146440)
They used to make these beta versions private so only ios/macos developers could test on them to report bugs to get them fixed before public release. They since opened it up to anyone who wants to install it which generates a lot of outrage from the peanut gallery when the beta has bugs.
Re:macOS 15.8.2 Breaks OpenGL by hedgehog on Monday October 19, 2026 @01:19PM (#50155154)
I think the reason so many people hit this in particular is enabling Sequoia beta channel is the only way to prevent the machine from wanting to upgrade to a newer major release.
Re:macOS 15.8.2 Breaks OpenGL by Reason077 on Tuesday October 20, 2026 @07:45PM (#50174246)
... and the updates that come through the beta channel aren't clearly labelled as "beta" or "release candidate".
Re:macOS 15.8.2 Breaks OpenGL by hedgehog on Tuesday October 20, 2026 @10:33PM (#50175364)
I've always found that quite strange. Clearly the information is present because they're not signed with the same keys.
Re:macOS 15.8.2 Breaks OpenGL by lynndotpy on Sunday October 18, 2026 @01:59PM (#50143564)
The problem is that this is a well established pattern with this operating system:

- A bug or regression is identified in a beta or release candidate. People quickly come to defend Apple saying it will surely get fixed.

- The bug or regression is released. People quickly come to defend Apple saying it's not a big deal, there are workarounds, and it will probably get fixed.

- The bug or regression is now the status quo. Why are you rehashing old news? Nobody cares, this impacts only 1% of people, you're imagining things, thread locked, user banned, et cetera.

The time to complain loudly and broadly is _before_ the bug or regression becomes the new status quo for the platform.

Re:macOS 15.8.2 Breaks OpenGL by LeoPanthera on Sunday October 18, 2026 @04:24PM (#50145134)
This sounds more like a story than a real issue. Do you have specific examples you can point to?
Re:macOS 15.8.2 Breaks OpenGL by ethbr1 on Sunday October 18, 2026 @09:01PM (#50147151)
Re:macOS 15.8.2 Breaks OpenGL by LeoPanthera on Sunday October 18, 2026 @09:56PM (#50147463)
But that's not a bug. It's a design choice.
Re:macOS 15.8.2 Breaks OpenGL by jjcob on Monday October 19, 2026 @08:31AM (#50151592)
I see this problem almost every year with macOS updates. Here are two examples that I recall of the top of my head. They are already a few years old but really annoyed me, because I spent the time to write detailed bug reports, kept re-testing the issue, and in the end Apple shipped the bugs and never fixed them:

- use of some custom NSTextAttachmentCells was broken when they added force touch dictionary lookup to NSTextView. As far as I know it was never fixed. The API is still documented and if you use it it will cause crashes as soon as someone uses force touch in a text view.

- fat binaries (32/64) stopped working when the 32bit binary uses Objective C garbage collection even when running on a 64bit system and the 64bit binary does not use garbage collection. This is clearly an error, Apple did not care about it. The only way to make such an app launchable again on 64bit is to remove the 32bit binary (that wouldn't run on a 64bit machine anyway)

Re:macOS 15.8.2 Breaks OpenGL by adamors on Sunday October 18, 2026 @01:35PM (#50143304)
Thanks for the context, the state of HN has been quite sad in recent years, now people (hopefully, and not bots) read the title and then go on random anecdotes, dumb generalisations and awkward tangents.
Re:macOS 15.8.2 Breaks OpenGL by bilbo0s on Sunday October 18, 2026 @01:41PM (#50143365)
>and awkward tangents

Especially on special internet forums, HN included, bots are generally paid for by professional influence campaigns so..

Yeah..

Whatever those AI's have to do to shape the conversation to get their message in, that's what they'll do. And that's going to sound pretty awkward to human ears.

Re:macOS 15.8.2 Breaks OpenGL by kccqzy on Sunday October 18, 2026 @01:55PM (#50143511)
An Apple engineer acknowledged the bug? That comment reeks strongly of Claude. I have a feeling that somebody did not use their brain and the response is an auto-response by Claude. Also things like attaching a sysdiagnose is useless and is well known to be hoops Apple requires bug reporters to jump through with no benefit to either party.

You also make it sound like the Apple engineer assigned the number but the number was auto-assigned when the bug report was filed. The same number was present in the first post so it could not have been assigned by the Apple engineer.

As far as I can see the Apple engineer did nothing at all. The attitude of that Apple engineer is worse than staying silent on this bug.

Re:macOS 15.8.2 Breaks OpenGL by Aurornis on Sunday October 18, 2026 @01:59PM (#50143574)
> The attitude of that Apple engineer is worse than staying silent on this bug.

The Apple engineer opened the ticket which is how these bugs get prioritized and fixed.

Staying silent or not responding would mean it doesn’t get fixed.

Re:macOS 15.8.2 Breaks OpenGL by kccqzy on Sunday October 18, 2026 @02:12PM (#50143727)
The Apple engineer didn’t open the ticket. The original reporter did. Perhaps actually look at the assigned number before jumping to defend Apple.
Re:macOS 15.8.2 Breaks OpenGL by trollied on Sunday October 18, 2026 @03:07PM (#50144223)
A user feedback is different to an actual radar that will be fixed by a dev.
Re:macOS 15.8.2 Breaks OpenGL by swiftcoder on Sunday October 18, 2026 @03:25PM (#50144415)
However since they didn't post a radar ID, nor did they mention filing a radar, this is all pure speculation
Re:macOS 15.8.2 Breaks OpenGL by giantrobot on Sunday October 18, 2026 @02:12PM (#50143729)
> Also things like attaching a sysdiagnose is useless and is well known to be hoops Apple requires bug reporters to jump through with no benefit to either party.

As a former Apple SWE that has read innumerable sysdiagnose reports, this statement is bullshit.

External bug reports very commonly have a variation of "THIS IS BROKEN YOU SUCK FIX THIS" as the main note. Even with a crash log attached that's not at all helpful. A sysdiagnose gives a state of the system the reporter has in front of them. You can't triage a bug with "FIX NOW" as the description.

I know I know, Apple has infinity dollars and every SWE should just magically fix bugs without needing to triage them first. Every external bug reports very is also a special snowflake that deserves concierge VIP serve and a dedicated SWE team to fix.

Re:macOS 15.8.2 Breaks OpenGL by kccqzy on Sunday October 18, 2026 @02:22PM (#50143840)
Did you read the bug report? This is not your garden variety THIS IS BROKEN YOU SUCK FIX THIS bug. It is respectful, it has a minimal reproducer, and it is communicated clearly. There’s no reason to stall it using the sysdiagnose requirement.

And yes, this is not the first time I’ve seen Apple requiring sysdiagnose for an excellently written report. Even John Siracusa would get these sysdiagnose requests; it’s a stalling tactic being applied indiscriminately.

If Apple cannot distinguish between an angry nontechnical user that SHOUTS IN UPPERCASE and a developer that communicates professionally with an equal, that’s Apple’s problem.

Re:macOS 15.8.2 Breaks OpenGL by 1over137 on Sunday October 18, 2026 @02:45PM (#50144048)
Especially since sysdiagnose contain so much info, it’s bad opsec to give that info over. Unless you repro in a fresh VM maybe.
Re:macOS 15.8.2 Breaks OpenGL by sam1714 on Sunday October 18, 2026 @04:10PM (#50144967)
Because you're testing pre-release software on a dedicated machine... right?
Re:macOS 15.8.2 Breaks OpenGL by kccqzy on Sunday October 18, 2026 @06:43PM (#50146250)
The distinction doesn’t really matter. Apple will ask for a pointless sysdiagnose even when one reports bugs in released software.
Re:macOS 15.8.2 Breaks OpenGL by simondotau on Monday October 19, 2026 @04:16AM (#50149722)
It’s not pointless when it allows an Apple developer to rapidly mimic the exact environment, in case it’s an extremely narrow bug involving a second-supplier controller chip.
Re:macOS 15.8.2 Breaks OpenGL by saagarjha on Monday October 19, 2026 @06:05AM (#50150477)
It's usually pointless. I attach very few sysdiagnoses to my bug reports.
Re:macOS 15.8.2 Breaks OpenGL by giantrobot on Sunday October 18, 2026 @08:44PM (#50147045)
You've convinced yourself that asking for a sysdiagnose is only ever used as a stalling tactic by Apple. There's not much I can say that will change your mind.

A minimal reproduction is great in a bug report but it's still not a complete in-situ snapshot of the machine.

Re:macOS 15.8.2 Breaks OpenGL by kccqzy on Sunday October 18, 2026 @10:50PM (#50147817)
I didn’t say sysdiagnose is only used as a stalling tactic. It may be useful if the reporter’s minimal reproducer doesn’t reproduce. But requiring it indiscriminately is definitely a stalling tactic.
Re:macOS 15.8.2 Breaks OpenGL by Marsymars on Sunday October 18, 2026 @04:40PM (#50145266)
“Most bug reports are bad” and “most good bug reports aren’t handled well” can both be true.

As a macOS user, my most recent datapoint is a crash in Apple Music that I’ve submitted probably a few dozen crash reports for, along with steps that trivially and consistently reproduce the crash - from my perspective, the crash was introduced in macOS 26 last year, and has received zero attention since then.

Re:macOS 15.8.2 Breaks OpenGL by egorfine on Monday October 19, 2026 @04:38AM (#50149888)
I hear you. The problem is real and I have no idea how to even start looking for a solution here.

Problem is, even when a bugreport is very well written[1] with all the details, it's either gets ignored for years or flagged as duplicate and then ignored for years or closed as wontfix and then ignored for years.

I've given up reporting bugs to Apple many years ago.

[1] https://egorfine.com/en/articles/priceless-bugreports/

Re:macOS 15.8.2 Breaks OpenGL by viraptor on Monday October 19, 2026 @08:14AM (#50151455)
Honestly I have next to 0 expectation that anything gets fixed. I've had bug numbers assigned to reliably system-crashing issues that were left in for years. Currently we've got a "libusb claiming a device will panic your kernel" issue in stable releases for half a year already. Reporting to Apple means nothing.
Re:macOS 15.8.2 Breaks OpenGL by VCFundedGenYer on Monday October 19, 2026 @09:49AM (#50152489)
macOS isn't FOSS - the devs should be testing + not asking users to do their job.
Re:macOS 15.8.2 Breaks OpenGL by hedgehog on Monday October 19, 2026 @01:15PM (#50155070)
The problem is that as far as I know the only way to pin a Mac to an older major version is to put yourself into the beta stream, so people (including me) are getting these not because they want developer access but just because they don't want to upgrade.