He worked on: Go, the Sawzall language for processing logs, and distributed systems. Go and Sawzall are usable and used outside Google.

Are those distributed systems valuable primarily to Google, or are they related to Kubernetes et cetera ?

He was paid by Google with money made through Google’s shady practices.

It’s like saying that it’s cool because you worked on some non-evil parts of a terrible company.

I don’t think it’s right to work for an unethical company and then complain about others being unethical. I mean, of course you can, but words are hollow.

How much time does it add when running e.g. "shittp user@lan-host uname" ?

Thank God for lucrative work higher up the stack. Maybe programmers will stop being the only scapegoats for rising home prices and the high cost of living.

I wonder if Visopsys, Windows 3.11 and others could work as a daily driver running in qemu, started from a Linux initrd that has just a browser and qemu. "Opening" the browser in Visopsys actually switches to the browser running on the host, and Alt-Tab switches back to Visopsys.

Why don't they just transport the blades standing up ?

This is actually the current practice: https://www.windpowermonthly.com/article/1371626/gallery-bla...

On the ground? Well, you're welcome to count the number of overpasses you'd have to clear or circumvent somehow.

They tip over from inertia or a small wind gust.

too dangerous - they might get struck by lightning

This can trace all processes on the host while strace traces one PID and its descendants. And bpf tracing does not stop processes at each syscall, so they run without slowdowns.

I think auditd can trace all syscalls system wide and let you filter as well. But it is a daemon whereas this is a tool you can run and interact with.

Were you the ghost writer for the Headhunters (2011) film ?

Is there a tool that records the timestamp of each executed command during a build, and when you rebuild, it tells you how much time is left instead of "building obj 35 out of 1023" ?

Or (for cmake or ninja) use a CSV that says how long each object takes to build and use it to estimate how much is left ?

OP Here. Thats an interesting idea. What The Fork knows all the commands run, and every path they read/write, so I should be able to make it estimate build time just by looking at what files were touched.