Apple’s lock on iPhone browser engines gets a December deadline
Apple’s lock on iPhone browser engines gets a December deadline
www.theverge.com
Apple’s lock on iPhone browser engines gets a December deadline
In Japan at least.
26 comments
26 comments
Great, let lazy developers ship lots of React/Electron/whatever apps each coming with their own Chrome engines and each being 100MB+ in size. Websites won't be tested properly on Safari anymore because "please install Chrome from the App Store for maximum compatibility". And Google's domination of the browser market will be completely unstoppable.
Well the alternative is what we have now: everyone is forced to use Safari.
Imagine being upset that people have a choice now.
Mobile apps are all already written without a care in the world about the user. I doubt Jimmy, who uses exclusively TikTok, Instagram, and Facebook and maybe plays a few ad-infested mobile games, is going to notice a difference, but now people can use Firefox and Chrome if they want instead of being locked to Safari in all its "glory".
More competition is always better.
We all thought that when Google came along, too.
Hopefully you are incorrect. Buttt I wouldn't be surprised if you were correct.
A lot iPhone apps already use React. There's a sample of a few on the React Native site: https://reactnative.dev/showcase. It's almost certain that you have at least one React Native app installed on your phone :)
I'm not sure what being able to run different browsers has to do with Electron, as Electron doesn't run on mobile at all.
Sites already misbehave in Safari because there's so many Safari-specific bugs. It's similar to IE6 in that sites often need Safari-specific hacks to make them work properly.
It’s only React now. But misguided developers WILL also package Chrome if given the chance.
And maybe it’s not Safari making the sites misbehave, maybe it’s Google pushing arbitrary features via their Chromium/Chrome ownership and developers optimising for them instead of adhering to actual standards?
this is the biggest fucking cope I ahve seen
you know you're the one choosing to run those apps, right?
They only have to be tested on Safari specifically, because it's doing some things differently from Mozilla and Chrome. I guess Apple will finally have to use their money to actually fix those issues with their own engine, so people will prefer using it. Oh no, all of that hard-earned cash! /s
(As a web developer, I despise Safari, sometimes with passion. At least we finally got rid of IE and that non-Chrome Edge shitshow by now.)
Not only is Safari miserable to test on without a Mac, whenever I see an exception to something in caniuse, it's almost always Safari.