3 ms·
I'm just speculating here, but since macOS/iOS have native APIs that automatically enable state restoration, Safari might be using those instead of reinventing
by kalleboo 10y ago
I'm just speculating here, but since macOS/iOS have native APIs that automatically enable state restoration, Safari might be using those instead of reinventing the wheel for cross-platform compatibility like Chrome and Firefox need to.
Leveraging native APIs means less code (fewer bugs), less disk usage, less RAM usage, etc.