Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Parzi8669280doh wow, not being able to be on the App Store for using non-Apple libraries?
Who saw this coming?
@Parzi has nothing to do with using “non-Apple” libraries.
Has to do with third party libraries that use private Mac OS and iOS API’s. This is banned by Apple as they are subject to change at any time, can be used to violate privacy, can lead to malicious software etc.
Apple is preventing shitty or dangerous apps getting into the store. I think that’s ok.
@Parzi so again, that’s not the case. A bit ridiculous to think that Apple would build something like directX and then block you from using it.
Apple creates certain API’s that are private, because they manipulate system configs, or touch sensitive user data that otherwise you’d have to ask permission for etc. They are only intended to be used by system processes.
These are undocumented API’s, that can only be found through getting class dumps and similar techniques and can only invoked through reflection using strings.
This is nothing like using directX that’s there for developers to use. These API’s can pose security issues, will change at the drop of a hat (breaking anything depending on it) and were never intended to be used by non system processes.
Stopping people from using these is actually a good thing
0100011112090279dyou know sometimes I hate apple, but this comment section makes me feel like Apple was right all along
And this time that‘s not apple‘s fault
@Parzi I’m pretty sure a lot of that would get identical backlash to what you’ve posted, from people saying Apple is too closed box even if you arent going through the App Store.
Is the current way of doing it the best technical solution? I have no clue.
Regardless if is or isn’t the rant still stands. Apple imposes restrictions on getting into the App Store that are, based on past examples, appropriate in at least some cases. Chromium doesn’t follow those rules. Electron is aware of this and doesn’t emphasis this risk anywhere. Electron is also not doing enough as it should be possible to automate this to, at a minimum, identify the issue so it can be addressed before a new release goes out to its developers