If you’re talking about applications that can be made to act how their namesake predecessors did 30 years ago, sure. The Unix mindset is all about that.
But don’t be fooled into thinking that anything on a modern Unix-like system hasn’t been modified, patched or rewritten from scratch at some point in the last 30 years. More than once. Even /bin/false has a changelog.
Slightly pedantic, but according to core-utils GitHub, false.c has not been changed in 21 years. But true.c, which is what false.c is based on, has been changed as recent as 4 months ago.
~I couldn’t resist looking it up, and found the results mildly interesting.~
Most changes are updating the copyright year.
After that, it’s pretty much (or maybe completely, I haven’t checked exhaustively) for the --help and --version flags, not for the core part of exiting with a certain exit code.
If you’re talking about applications that can be made to act how their namesake predecessors did 30 years ago, sure. The Unix mindset is all about that.
But don’t be fooled into thinking that anything on a modern Unix-like system hasn’t been modified, patched or rewritten from scratch at some point in the last 30 years. More than once. Even /bin/false has a changelog.
It is committed long-term maintenance that separates a road from a desire pathway.
It is committed long-term maintenance that eventually makes software solid enough to be someone else’s substrate.
/bombast
Slightly pedantic, but according to core-utils GitHub, false.c has not been changed in 21 years. But true.c, which is what false.c is based on, has been changed as recent as 4 months ago.
~I couldn’t resist looking it up, and found the results mildly interesting.~
Most changes are updating the copyright year.
After that, it’s pretty much (or maybe completely, I haven’t checked exhaustively) for the --help and --version flags, not for the core part of exiting with a certain exit code.
The true author, so to speak.
you mispelled super interesting
You misspelled misspell 🤪