Allow me to retort with an all-in-one self build script, along with pass-through args and exitcode.

#!/bin/sh
out=$(mktemp)
sed -e '0,/^#SELFBUILD$/d' "$0" | rustc --o "$out" - && "$out" "$@"
status=$?
rm -f "$out"
exit "$status"
#SELFBUILD

fn main() {
    dbg!(std::env::args());
    println!("hello rust");
    std::process::exit(2);
}

P.S. I have no idea why you’d want that, as it’s a terribly inefficient way to ship code, but it’s a fascinating glimpse at how we used to do self-extract archives decades ago.

Interestingly, we’ve got the same glitch in the Gregorian calendar, where the year 0 doesn’t exist. So the 21st century started in 2001…

The opinion of Linux desktop users (or any users really) do not count in the enterprise world. Somehow, if management bought in on the Crowdstrike rootkit bandwagon, you’ll see it on corporate hardware. It doesn’t matter if it’s a bad plan; it doesn’t matter if it gives an American company a backdoor to all you infrastructure; if the CISO decides everyone gets it, everyone get it.

The only thing you can really do as a lowly employee is keep any such device away from any personal info or network as if it’s infected by malware (which I would argue is exactly what it is).

You also can’t make star ships out of an sdcard

As a bytecode tinkerer, I’d say considering NOP to be global knowledge is a slippery slope.

just tag yourself as “early-access” and suddenly everyone will forgive your flaws.

As a developer, I really don’t like how Wayland has fractured the ecosystem. Competing immature protocols are still all over the place while the immobility of x11 has spoiled us for years. It’s getting better, but in the meantime I can still write an x11 app which will work mostly everywhere (thanks to xwayland), whereas a wayland app may not work everywhere (not on X11, and not on compositors which don’t implement the right combinations of protocols).

Consider IEEE754 arithmetic as monadic, simple!

Someone is confusing indices and cardinality.

The dude trying to push Django in 2003

not the way I would have done it

It could be a legitimate criticism. Sticking to a codebase style and to the language idioms improves clarity and thus maintainability. But then, that means the way to do it should already be clear.