Look at Valve's Proton project, which was intended to support MacOS just as well as Linux for near-perfect translation of DirectX games. By chasing such a radical paradigm shift with their new computers, there are inevitably going to be developers who get thrown under the bus without chance for recourse. Apple can lead a horse to water, but they ultimately can't make them drink. The simple fact is that, unsurprisingly, a lot of devs don't care. Is maintaining their kernel extension still feasible on macOS? Interestingly, Apple did something similar on Windows : They are now using Microsoft's OneDrive implementation for their iCloud file sync client. Still, I wonder whether the deprecation of 3rd party kernel extensions might also be a reason to switch to such a "thin client". Their motive might be less development effort, and the official API might be good enough. OneDrive and Box are moving away from their implementations and switching to Apple's File Provider API. They were one of the first who offered these 0-byte placeholders, and they rely on a kernel driver, which is only available on both Windows and macOS (but not Linux). My guess: Porting their kernel extension to ARM is not that trivial.
0 kommentar(er)
