4 ms·
They are restricting one very particular tool, not a set of tools or category of tools. I can write an iOS application using a veritable shit-ton of different t
by rubyn00bie 7y ago
They are restricting one very particular tool, not a set of tools or category of tools. I can write an iOS application using a veritable shit-ton of different toolchains. It sounds more like you're locked into a particular toolchain more than Apple has locked all the other toolchains out.
- bearcobra 7y agoI don't personally develop anything using Electron. But given it's popularity as a way to build desktop apps, it seems reasonable that people are concerned even though they haven't also blocked QT or React
- nomel 7y agoI think the concern should be on why the electron devs found it appropriate to use a private API, which is against App Store guidelines, risking/preparing rejection for any app using their framework. The rejection of private keys used, by frameworks, is in no way new (2009 [1]) or misunderstood. I find it very difficult to understand why Apple is getting any blame/concern for enforcing the violation of a very very old requirement. [1] 2009, https://stackoverflow.com/questions/1773615/apple-and-private-apis https://stackoverflow.com/questions/1773615/apple-and-privat... > The reason this has become news recently is the creator of a framework used by several apps used a private API, so when developers who included his framework updated their apps, they were rejected What’s old is new.