Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Saying Google didn’t have to reinvent containers when Google invented containers is .. something (https://en.wikipedia.org/wiki/Cgroups).


And for a brief couple years Google had an offering the world could use that exposed that invention. Via the stock, well respected LXC tool.

They created something, only to never ever use it in public eye. To go keep reinventing and keep NIH'ing. The android virtualization stack is fucking wild, and hardly used, offers such a meager fraction of what ChromeOS was doing.

Not a bad callout, but this seems like a particularly glorious & vicious slam... that doesn't change the big picture on iota.


Android is reusing the ChromeOS vmm, crosvm. How is it less capable?


They invented containers on Linux kernel.

Containers on UNIX and mainframes predate Google's existence.


It's somewhat unusual for Google to open source and mainline this bit of functionality. Last time I heard, Google's internal production Linux kernel still has 9000+ patches[0] on top of vanilla Linux. And I'm still waiting for them to open source switchto[1].

[0]: https://lwn.net/Articles/871195/

[1]: https://www.youtube.com/watch?v=KXuZi9aeGTw



Cgroups is a kernel feature, parent is talking about the userspace stack for managing containers. Google uses LXC in crosvm, and didn't have to program it from scratch.


cgroups are neither necessary nor sufficient for Linux containers




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: