News for hackers. Stuff that matters.
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/