> Perhaps trains beat road transport efficiency to a similar degree.
Not just efficiency but you can use electric trains if your tracks are electrified. Add into that electricity production system that is mostly renewable+nuclear (the Nordics for example) and you get very very low emissions.
They do, trains are BAFFLINGLY fuel efficient in terms of pounds of cargo. Once they get up to speed, trains can move one ton of cargo about 480 mile per gallon, vs 130 with trucks
also, fuel is a huge cost (maybe even the main cost), and drag has a >linear relationship with speed- so the ships will slow down based on fuel prices.
DoorDash finds a way to consistently screw up orders.
Order A,B,C - receive only A+B, or A,B,D. No explanation. Tipped generously.
For a long time, I myself drove and picked up my orders. The same restaurants rarely made mistakes. I never had to ask for missing item to be included. They always had everything in the bag.
It’s happened so often, it has to be malice from one of the parties involved.
While I would love to agree with you, in America restaurants of all sizes (and personal transportation companies) seemingly often rely on tips from customers to supplement the wages of their workers instead of just paying them fairly.
It's a collective action problem: it can't be solved by individuals like this. All you'll achieve is complicity in wage theft. A viable approach might be to prefer doing business with companies who promise their workers a good wage, but this requires that your local businesses actually make that commitment. To get that, you'll have to go outside the abstraction of the market, and actually talk to decisionmakers within the businesses. (This is sometimes called "activism".)
No, I disagree that other peoples ethical failures spread to you if you don't participate in the ethical failure. If you disagree on ethical grounds with something, just don't do it. To the extent that you could simply not frequent those places.
The army of faceless delivery gig workers can’t exactly pick and choose. They deliver the food or they get banned from the platform and replaced by the next guy.
With Intel VMX virtualization, instruction execution is handled by the CPU but (a lot) of software still has to deal with HW peripheral emulation .
QEMU uses KVM (Intel VMX, etc) but implements HW peripherals (display, network, disk, etc) faithfully matching really HW and provides a full BIOS (SeaBios) or UEFI firmware (EDK) to deal with with boot process.
Over time, Linux (and Windows) were extended to support novel “peripherals” designed for high emulation performance (not a real HW product).
Firecracker basically skips all the “real” peripheral emulation and skips the full BIOS/UEFI firmware. Instead, it implements just enough to boot modern Linux directly. Also written in Rust instead of C. It will never support DOS, Windows 95 or probably anything else.
The “microVM” BIOS allows it to start booting Linux very quickly (sub-second). A traditional QEMU VM might take 2-5 seconds. Some people are emboldened to effectively move back from containers to running applications in a VM…
Instead of the VM being long lived, it is really just for running a single app.
I think Kata containers had this idea for much longer but Firecracker provides a more efficient implementation for such a thing.
thank you very much for the detail there. I assume you would also know very well how a docker container would compare to firecracker in terms of boot time. I understand that a container and a VM are not the same thing but just curious
Good questions — yes, Containarium relies heavily on *user namespaces*. Here’s how it works:
- We enable `security.nesting=true` on unprivileged LXC containers, so Docker can run inside (rootless).
- *User namespace isolation* ensures that even if a user is “root” inside the container, they are mapped to an unprivileged UID on the host (e.g., UID 100000), preventing access to host files or devices.
This setup allows developers to run Docker and do almost anything inside their sandbox, while keeping the host safe.
I’ve seen too many embedded drivers written by well known companies not use spinlocks for data shared with an ISR.
At one point, I found serious bugs (crashing our product) that had existed for over 15 years. (And that was 10 years ago).
Rust may not be perfect but it gives me hope that some classes of stupidity will be either be avoided or made visible (like every function being unsafe because the author was a complete idiot).
reply