Hacker News Reader

Comment by zamalek | Hacker News Reader

The point of my rather facetious comment is that IPC a well known thing (I struggle to even call it "tech") that has been around for 30-40 years. I don't understand why Apple needs people to make excuses for them, but this excuse would render Apple vastly more incompetent than neglecting to separate browser tabs in 2025.

View on HN

Browsers are incredibly complex, and moving them to an IPC model is not easy. Essentially, you need to ensure "same process like", performant JavaScript interoperability in some cases, often (but not always) due to backwards compatibility.

Firefox has shared a lot about their efforts in moving there. If you're curious, there are a lot of blog posts and internal design docs under their project name "Project Fission".

But yeah, the fact that both Chrome and Firefox have managed to do so does leave Apple looking slightly bad here.

How often do tabs really need to communicate, and when they do, does it really need to be as fast as possible. I would say slower and secure would be a better design philosophy, especially as tab interaction is generally rare, and low bandwidth

We already have this with (iirc) postMessage API.

That API is exactly one of the reasons Safari still runs some distinct origin sites in the same process together.

Performantly implementing that API across processes is possible, but not quite trivial.

popup-based authentication does not actually need high performance.

It's not used only for authentication, and figuring out what a website is trying to do heuristically doesn't sound easy either (although I believe Chrome on Android does just that, and enforces a site-locked process when they deem it important for security reasons).

Reply on news.ycombinator.com