3 ms·
In browser land, all open sites share the memory of the browser heap, and there’s no crosstalk at all. I think the way out of that particular issue is creating
by dclowd9901 3y ago
In browser land, all open sites share the memory of the browser heap, and there’s no crosstalk at all. I think the way out of that particular issue is creating a closure around the function (application) that effectively acts like the application’s own context. What if an app could open an app? Or put another way, what if an app could be an OS to another app?
- josephg 3y agoThere’s no cross talk because you can’t peek / poke arbitrary pointers in javascript. But you can in Rust. And even then, I think modern browsers still isolate each tab in a separate process just to be safe. I don’t think they share memory.
- Symmetry 3y agoHave you seen the "Birth and Death of Javascript" talk? https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript https://www.destroyallsoftware.com/talks/the-birth-and-death... But the basic idea of using a managed language like Java or something to eliminate the need for hardware process security goes way back. Microsoft's Singularity project is I think the best developed effort at this.