4 ms·
This is all a bunch of BS. Apple didn’t ban the apps because they were using “web technologies” or even because they wanted “everything to be in the Mac App Sto
by scarface74 7y ago
This is all a bunch of BS. Apple didn’t ban the apps because they were using “web technologies” or even because they wanted “everything to be in the Mac App Store” but because they use private APIs. He even admitted that.
Seeing that “thousands” of developers are depending on a framework that uses private APIs that will take a long time to fix, kind of proves Apple’s point. If Apple releases an update that changes the behavior of the private APIs in unexpected ways - which they have every technical right to do since it is not a vendor’s responsibility not to change the behavior of non published APIs without warning, all of those apps will break.
- erichocean 7y agoRight–Apple will make an update that breaks Chrome accidentally, and no one at Apple will notice that it happened.
- dwaite 7y agoSo, are you saying that Apple should have to maintain any internal OS functions that Chrome uses as if they were stable API forever, because its Chrome?
- austhrow743 7y agoYes, many Apple critics just want it to be Microsoft.
- scarface74 7y agoSo now we are back to having to do things like Microsoft where you have twenty different app specific hacks because developers wanted to use private methods.
- saagarjha 7y agoThere are hundreds of people at Apple that use Chrome as their browser of choice. Any obvious changes that break Chrome will be caught and dealt with quickly.
- scarface74 7y agoAnd that might be “caught” by letting Google know. If Apple was willing to piss Adobe off by cancelling Carbon64, and drop all support for 32 bit apps, do you think they are going to let Chrome stop them from making breaking changes to their OS?