3 ms·
“wasm boots fast, containers boot slow”: as someone who uses neither (unless you count cgroups), i assume there’s a reason that ”classic” containerization is sl
by colinsane 3y ago
“wasm boots fast, containers boot slow”: as someone who uses neither (unless you count cgroups), i assume there’s a reason that ”classic” containerization is slow? like, your container today provides a complete linux userspace with a filesystem, scheduler, user/permissions enforcement, elf loader/dynamic linker, service manager (systemd/openRC/whatever), maybe a DNS stub resolver, etc — and maybe you don’t actually need half of these? what does using a new bytecode/architecture have to do with optimizing any of this? is it just a sneaky way of swapping out libc and the abstractions beneath it (and if so, why not do just that on “plain” x86_64)?