Re:The journey to controlling external monitors on M1 Macs
by smoldesu on Friday July 30, 2021 @11:12PM
(#28014933)
Why didn't they abstract it, or create a stripped/safe userland option to replace it? If I'm relying on a Mac for work, I can't have them removing essential features from my computer in a simple upgrade. Maybe MacOS needs semantic versioning, or at least some level of communication with the end user about compatibility.
[ Parent
| on HN ]
Re:The journey to controlling external monitors on M1 Macs
by slrz on Saturday July 31, 2021 @07:42PM
(#28022418)
This was never an intended feature. If I understand the article correctly, they were using an undocumented ("private") API which happened to stop working.
Re:The journey to controlling external monitors on M1 Macs
by smoldesu on Saturday July 31, 2021 @11:04PM
(#28023475)
Every API is undocumented on MacOS, what do you want them to do? How are you supposed to discern between zombie XNU code and Good LTS Apple Compliant code?
Re:The journey to controlling external monitors on M1 Macs
by brokenmachine on Tuesday August 03, 2021 @01:16AM
(#28045910)
Rule of thumb: if you paid for an official Apple dongle, all related code is LTS (*until said dongle is deprecated on a whim, of course).