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.

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

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.

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.

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.

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.