I can give you examples. Just the other day I was updating an API that has been deprecated for a decade and a half but still worked. I never had to update a deprecated API in macOS, though I do. Maybe I got lucky in the ones I use, but either way the point stands.
Oh, come on, that’s just bad faith arguing. “Indefinitely” does not mean “forever”. When an API stops working because the OS around it fundamentally changes, that‘s understandable. But they don’t usually break something they deprecated just because it was deprecated, those keep working.
> An example on Github compiling on Tahoe is welcomed.
Sure, buddy, I’ll get right on it. I’ve been avoiding Tahoe since it was announced but I’ll install it and create a project just for a random troll on the internet. I’ll even make a series of them, and a private YouTube channel just for you while I’m at it.
I can give you examples. Just the other day I was updating an API that has been deprecated for a decade and a half but still worked. I never had to update a deprecated API in macOS, though I do. Maybe I got lucky in the ones I use, but either way the point stands.
Try to use Quicktime, Quicktime3D, QuicktimeVR on Tahoe, with their Mac OS 9 API surface.
Or Java Bridge, Carbon, AGL for some more recent on OS X timeframe.
An example on Github compiling on Tahoe is welcomed.
Nope, "Apple does keep supporting old APIs indefinitely.". doesn't stand.
> with their Mac OS 9 API surface
Oh, come on, that’s just bad faith arguing. “Indefinitely” does not mean “forever”. When an API stops working because the OS around it fundamentally changes, that‘s understandable. But they don’t usually break something they deprecated just because it was deprecated, those keep working.
> An example on Github compiling on Tahoe is welcomed.
Sure, buddy, I’ll get right on it. I’ve been avoiding Tahoe since it was announced but I’ll install it and create a project just for a random troll on the internet. I’ll even make a series of them, and a private YouTube channel just for you while I’m at it.
1 reply →