4 ms·
Huh? I don't get this. Mozilla is switching from a single-process model to a multi-one. Chrome was built that way from say one. I hope you see that moving from
by why-el 13y ago
Huh? I don't get this. Mozilla is switching from a single-process model to a multi-one. Chrome was built that way from say one. I hope you see that moving from different models costs more time then actually pick one and support it forever.
- sanxiyn 13y agoYou have a good point about switching cost. On the other hand, Chrome always could be run with --single-process (mainly there to measure the overhead of multiprocess), so it didn't really "pick one".
- pcwalton 13y agoChromium's --no-remote is pretty busted these days, in my experience. Basic browsing sorta works, but little else does.
- reubenmorais 13y agoOnce you have a multi-process setup in place, running in a single process is relatively simple, IPC just routes messages internally instead of across processes. Having a single-process setup and going to a multi-process one is a way, way, way larger effort.
- Crito 13y agoElectrolysis was stalled and/or deprioritized for something like two years, with no apparent progress.