macOS 15.8.2 Breaks OpenGL

AI was a side argument rather than the thread’s main subject, but it exposed a sharp divide over what cheap code-generating models should change. One camp treated an OpenGL regression as less threatening because a developer can now use an AI assistant to translate legacy rendering code toward newer graphics APIs for a trivial token bill. That view frames AI as a practical escape hatch: old platform-specific code no longer has to trap teams indefinitely. Most of the AI-focused pushback rejected that premise. Commenters argued that inexpensive automated porting does not make broken backward compatibility acceptable, especially when Apple chose to deprecate a widely used cross-platform interface without offering a universally portable successor. They saw the suggestion as a familiar move from fixing a vendor failure to making customers spend time, money, and engineering attention working around it. One reader also distrusted the apparently formulaic bug-triage response, suspecting automation had replaced meaningful engineering engagement, though that claim was speculative. A more aspirational aside imagined AI eventually enabling a better operating-system ecosystem, but it attracted no substantive defense. The AI discussion therefore landed less on model capability than on accountability: automation can lower migration costs, but it cannot excuse a platform owner from maintaining software it has broken.