Different problem, but I liked djb’s UNIX take: “Many portability problems would disappear if UNIX distributors followed the rule stated by Kernighan and Pike in The Practice of Programming, Section 8.7: `Change the name if you change the specification.'” https://cr.yp.to/docs/unixport.html …
-
-
-
The problem is not "changing the specification" but "forking an ambiguous, buggy or lackluster specification with a different set of interpretations, fixes and kluges". As in Nix, any change whatsoever could lead to a new name. Great for binaries, but absurd for source code.
- 1 more reply
New conversation -
-
-
Ahh... and then you have a system where /usr/bin/env doesn’t exist. Or a system where #! only cares about the first part. Best solution is to flip the table...
-
Interestingly, /usr/bin/env exists at runtime on NixOS, but not at build-time. Meanwhile, in Nix, the full path to env is 66 chars and that to gxi is 78 chars. Add 4 for #! space null, and the fully shimmed #! line is 148 chars, or 20 too many with a regular Linux kernel.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!