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'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?
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.
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.
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.
Point is, the reasons we didn't get any even minimally portable native graphics API this cycle are more legal than technical.
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.
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...
That’s how release candidates work.
The headline could have included RC to make it accurate. As submitted it’s pretty misleading.
- 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.
- 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)
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.
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.
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.
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.
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.
A minimal reproduction is great in a bug report but it's still not a complete in-situ snapshot of the machine.
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.
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.
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.