Why We Replaced Firecracker with QEMU | Hocus Blog
At CodeSandbox we use Firecracker for hosting development environments, and I agree with the points. Though I don't think that means you should not use Firecracker for running long-lived workloads.
We reclaim memory with a memory balloon device, for the disk trimming we discard (& compress) the disk, and for i/o speed we use io_uring (which we only... See more
We reclaim memory with a memory balloon device, for the disk trimming we discard (& compress) the disk, and for i/o speed we use io_uring (which we only... See more
Article
Me and the team at @lovable_dev just spent two months rewriting 42,000 lines of code from Python to Go.
Technical deep dive of why we did it +what this means:
// 1
Viktor Erikssonx.com
Here is a technical blog about why we switched from Playwright to CDP 🔗↓ https://t.co/DJDMPA7Cex