Hacker News new | past | comments | ask | show | jobs | submit login

> 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.




Anecdotally, the only time I’ve had issues with unresponsiveness for pages in Safari is with sites that were written with Chrome specifically in mind.


So, basically everything.


The impact is minimal to nonexistent on a light-to-moderate-JS “site” and only really shows up in heavy “apps”, like YouTube or GDocs.


Really? Even something simple like Wordle feels janky with the way Safari’s chrome overlaps the keyboard.


Do you have some kind of extensions or something like text zooming enabled? On a clean install it doesn't overlap at all.


Hmm the layout is working for me now, but the tile animation is broken. They flicker instead of smoothly flipping over.


Any chance you have reduced motion enabled? They flip for me but are obviously on a short timer.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: