…are Turing Complete, so what you can do with them is exactly equal.
But they’re only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.
…are Turing Complete, so what you can do with them is exactly equal.
But they’re only equal in the Turing complete sense, which (iirc) says nothing about performance or timing.
I’d say it gets a little different with command line utilities — maybe “utility” is the appropriate term here, but I’d call something like grep
a program, not an application (again — “utility” also works).
To be sure, grep
is extremely powerful, but its scope is limited.
from stdlib.h import cout
Wait this looks wrong, shit…
Anything can use it, but I think by convention it’s used for http on a non-privileged port.
It is “backwards” from some other commands — usually you run copy/rsync/link from source to destination, but with tar the destination (tarball) is specified before the source (directory/files).
That, and the flags not needing dashes always just throws me for a loop.
And the icing on the cake is that I don’t use tar for tarring that often, so I lose all muscle memory (untaring a tgz or tar.bz2 is frequent enough that I can usually get that right at least…).
Did the developer use any version control though? SCCS has been around since the early 70s, RCS and CVS since the 80s. The tools definitely existed.
Also, it was a single dev, which makes SCM significantly simpler!