What tradeoff? Both chrome and Firefox treat private browsing data differently, and if they crash, will not be able to just restore it. Even if they did, its still bad design. The point of private browsing is to make it so when that window exits, that data doesn't exist anymore. You can still pull it up in new tabs in Firefox, but not if the window itself closes.

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.

>> Both chrome and Firefox treat private browsing data differently

>> The point of private browsing is to make it so when that window exits, that data doesn't exist anymore.

When defining what private browsing is supposed to do we should keep in mind Safari was the first major browser to introduce the feature.

Sure, but it also didn't save/restore any window or tab state at that time. All those features came later, so this represents a change in how things act between Safari versions.

> The point of private browsing is to make it so when that window exits, that data doesn't exist anymore

Who defined it that way? And how do you define 'exit', 'data' and 'exist'?

What is reality anyway?

Typically in macos, closing windows doesn't quit applications and quitting applications doesn't close windows.