Re:Google Just Gave 2B Chrome Users a Reason to Switch to Fi...
by jnwkw on Sunday June 02, 2019 @07:53AM
(#20074911)
Nah I'm talking about Chrome and Firefox on Android. They are both worse than Safari on iOS.
Also I understand that Safari might've created some pain for you as a frontend developer, but frankly I don't care. I'm an end user and I only care about how fast and secure the browser is. And Safari wins there, it's not terrible by any measure for the end user.
Re:Google Just Gave 2B Chrome Users a Reason to Switch to Fi...
by seabrookmx on Sunday June 02, 2019 @09:23AM
(#20075275)
Safari being faster on iOS might be more indicative of your iDevice's performance rather than Safari's (the A-series chips are quite fast). Without being able to run both browsers on the same hardware you can't really make an apples to apples comparison.
Re:Google Just Gave 2B Chrome Users a Reason to Switch to Fi...
by AsyncAwait on Sunday June 02, 2019 @08:21AM
(#20075012)
> Chrome and Firefox on Android. They are both worse than Safari on iOS
I realize that this is subjective, but Firefox Focus has been my preferred mobile browser, regardless of if I have Safari available, (iPad), or not, (Android). In fact having desktop addons on Android has been great.
Re:Google Just Gave 2B Chrome Users a Reason to Switch to Fi...
by kekebo on Sunday June 02, 2019 @08:10AM
(#20074973)
That might be your personal impression but I don't share it.
Development wise it's not so much about our pain as about certain known bugs that went unfixed for up to 2+ years, similar goes for a range of CVEs (re:being secure).
Re:Google Just Gave 2B Chrome Users a Reason to Switch to Fi...
by jnwkw on Sunday June 02, 2019 @08:13AM
(#20074982)
Do you believe Chrome or Firefox on Android to be faster or more secure than Safari on iOS?
Re:Google Just Gave 2B Chrome Users a Reason to Switch to Fi...
by ethelward on Sunday June 02, 2019 @08:29AM
(#20075048)
Performances issues will be hard to estimate, as you can not compare safari to the others on the same phone, which means that you will not be able to correct for hardware and software stacks influences.
When I was working more frontend (~1,5 years ago) no browser would cause more work and trouble for us than Safari on iOS (we didn't have to support IE9 and lower).