I found it funny that random decisions from 60s, 70s, 80s still have repercussions on how we use computers today, because backwards compatibility beats cleanliness every time.
Be right back, solving some Windows backslash and CRLF issues.
Be right back, solving some Windows backslash and CRLF issues.
> What's False: That similarity is based much more on coincidence and inherent physical limitations than a direct line of imitation.
The width of chariots/wagons/car/trains doesn't vary all that much, not compared to stuff like sailing ships.
But the Space Shuttle SRBs have a considerably larger diameter (3.7m compared to 1.435m rails) so it's more likely due to civil engineering standards: you can only transport something so big until you need to take down power lines and cut down trees.
The Falcon 9 has the same diameter and it was explicitly chosen because it's the maximum transportable by road.
Gauge is, most of all, a tradeoff between construction costs (tunnels, bridges, cuttings, oh my! Every additional inch of the gauge gets real expensive in Actual Terrain; ditto for train stations: narrow gauge can fit many more tracks next to each other), and between operating costs (wider gauge cars can be wider _and_ higher, as they're inherently more stable; thus, more cargo on same number of cars).
( ObXkcd: https://xkcd.com/927/ )
See https://fedoraproject.org/wiki/Features/UsrMove#Why_don.E2.8...
> Fact: This would make the separation between vendor-supplied OS resources and machine-specific even worse, thus making OS snapshots and network/container sharing of it much harder and non-atomic, and clutter the root file system with a multitude of new directories.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseFor...
% find /bin /usr
/bin
/bin/sh
/usr
/usr/bin
/usr/bin/env
% which cp
/run/current-system/sw/bin/cp
% readlink $(which cp)
/nix/store/l96gc2qb8ysnf5hcq1hp5a3r6x905rf4-coreutils-8.31/bin/cp
https://nixos.org/nixos/nix-pills/why-you-should-give-it-a-t...
This is the OS where each binary runs with a different path and library path, with only the programs it needs (on the versions it needs) linked there.
... Also check out those ^Zs at EOF, will ya.
The whole "move fast and break things" is a big lie, because you know that in that way, the system works, newer changes will break countless systems/scripts/etc
There is a risk of change.
There is a risk of stasis.