4 ms·
> Some of the difference is due to Safari being a bad browser (probably intentional), but a bigger part is that only having one thread makes it really difficult
by nicoburns 5y ago
> Some of the difference is due to Safari being a bad browser (probably intentional), but a bigger part is that only having one thread makes it really difficult to have a responsive UI
Interestingly Safari is actually generally better than other browsers for running a responsive smooth UI. Not sure how much of that is the Safari engine and how much of it is better CPU on iPhones. But even on a first generation iPad or an iPhone 4 it was possible to get 60fps rendering fairly easily. The same could not be said for even higher end android phones of the time.
- kitsunesoba 5y agoAnecdotally, the only time I’ve had issues with unresponsiveness for pages in Safari is with sites that were written with Chrome specifically in mind.
- themerone 5y agoSo, basically everything.
- kitsunesoba 5y agoThe impact is minimal to nonexistent on a light-to-moderate-JS “site” and only really shows up in heavy “apps”, like YouTube or GDocs.
- halpert 5y agoReally? Even something simple like Wordle feels janky with the way Safari’s chrome overlaps the keyboard.
- acdha 5y agoDo you have some kind of extensions or something like text zooming enabled? On a clean install it doesn't overlap at all.