3 ms·
As a total layman to developing kernel extensions, is this another example of apple limiting what you can do with their hardware, or just an effort to get devel
by cgb223 7y ago
As a total layman to developing kernel extensions, is this another example of apple limiting what you can do with their hardware, or just an effort to get developers to modernize how they make drivers for macOS?
- takeda 7y agoWell, apple makes the hardware, so they would typically make the drivers as well. From what I read and understood is that without being able to load own extensions you can only do whatever Apple allowed you to do. It could be compared to changes that Chrome plans (or already introduced?) to restrict extensions that filter sites which affect adblockers and you're at mercy of Google what you can block and what you cannot. Similarly here, you will only be able to hook to interfaces Apple provided, but if you plan to do something that wasn't thought of, or Apple does not approve, tough luck.
- Someone 7y agoThis doesn’t limit what you can do with their hardware, it limits what you can do with their software. This doesn’t change anything w.r.t. running your own software on hardware you bought from them. They want MacOS to be stable and secure. Disallowing kernel extensions is a step towards that.