The OP, in fact. $10 isn’t much for a interesting little side project or help page like this if it gets any traction.
What about other compression algos like bzip2 or xz? Learning this stuff by rote will leave you in a pickle when you get an uncompressed archive, or something more exotic than gzip.
Yeah. A simpler and more versatile method frequently available is tar -xf thefile and it’ll just figure it out.
There’s also the -a option to automatically determine the compressor to use based on the output filename. For example, tar caf myarchive.tar.bz2 ..
Supported by GNU tar and FreeBSD’s tar at least, but not OpenBSD’s tar for one.
I disagree. I think cheat sheets are a great way to bootstrap yourself into productivity. You can always take the formula you’ve learned and RTFM to gain more depth.
Hmm, I’m generally opposed to rote learning of any kind because while it might give you enough to ‘get along’ you’ll never master anything without understanding.
Particularly with computing, understanding (more-or-less) what you’re doing takes a little more effort but yields great rewards.
That’s not to say all cheat sheets are evil, there are some things which must be learned — I just don’t think this one is very good.
Are man pages dead?
Using the shell to extract files should mean it’s faster to rtfm than dig online. With a case as simple as this, learning through man or --help should be so fast there’s no need for a page like this.
Cheat sheets should come with “See also” references anyway.
So this drives me nuts because if your Node project depends on dependency A, but dependency A lists a version range for dependency B, npm will update B to the latest version available when you rerun “npm install”, even if you have an exact version listed for A. You can solve this with shrinkwrap but in some cases you want to check you can blow away your shrinkwrap and reinstall and get the same file back out.
We usually worked around this by forking A and locking down its dependencies.
My understanding is that yarn and its lock file do a better job with this than npm shrinkwrap.
How long ago did you put this up?
right before posting here