logoalt Hacker News

LoganDark • today at 7:18 PM • 0 replies • view on HN

Here are some reasons I don't use Safari in place of Chrome for certain things:

- it doesn't like to serialize the state of tabs. Chrome is pretty good at somehow snapshotting the entire state of tabs to the point where it can be reconstructed after relaunch, even offline.

- webpage loading is sort of janky. Chrome will show the webpage streaming in live, but Safari will simply freeze in place until it's done. Maybe this is due to an Apple philosophy decision, but I don't prefer it.

- similarly to how Safari doesn't seem to serialize tab states, navigating forward or back usually needs to load the page from scratch, including resubmitting forms or whatever.

- speaking of forward and back navigation, I'm kinda annoyed that each time I use the trackpad to navigate history, I have to wait for the swipe animation to finish before I can interact with the webpage. I try to always use cmd+brackets instead now, because it's much faster.

- IIRC, it seems the newer macOS 27 betas caused Safari to develop an issue where after it's been open for long enough, certain types of videos will stop being able to play at all until the browser is quit and restarted. kind of annoying, combined with the lack of tab snapshotting, because I have to manually visit each tab to load it on each launch.

I still daily drive Safari and use it as my main browser. But I keep an instance of Chrome open for tabs that I never really close. And then I have an instance of Orion for spreadsheets. (I use spreadsheets to keep track of medication usage, sleep times and finances)