Hacker News .hnnew | past | comments | ask | show | jobs | submitlogin

Chrome did this since the beginning but didn't use that much memory back then. So clearly processes aren't the only answer.


Chrome's codebase also got more complex so now every new process consumes a lot more memory. It's a way of achieving concurrency, but it's not necessarily the best way in terms of memory footprint.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: