I’ll let Randall Munroe decide that himself, considering the fact that he provides URLs for hotlinking below the comics

I raise you this: https://imgs.xkcd.com/comics/lisp_cycles.png

So much this. Chainshot was highly effective at taking down masts and sails, effectively immobilizing the target. If you fired a chainshot towards the mast, chances were really high that each ball would hit 9n each side of the mast, with the chain tearing off the mast itself. And even if you missed and hit only sail, the chain would rip out a huge chunk of sail and any rigging it hit as well.

Source: I used to play Cutthroats a lot back in the day.

I assume the revolver cylinder matches the amount of barrels, and they spin in unison during fire.

The forest can’t be harmed
when its inhabitants are armed.

Not very practical, but good for understanding the OS: Everything is a file. Even your filesystem and harddrive is represented by a file (devicenode).

Back in the day, before things such as pulseaudio and equivalents became the norm, there was also such a file (it might still exist, idk) for your soundcard. By shoving the contents of a wav file directly into /dev/dsp, you could hear it as if it was played normally.

Unrelates to the above, in a terminal context it’s very handy to learn the concepts of STDIN, STDOUT, and STDERR, and how to manipulate these. I won’t go into it here, but whenever you see a bunch of commands strung together with redirects, < > | >>, that’s usually for sending the output (STDOUT) of one command somewhere else, such as to the input STDIN to another command.

I’ve always been intrigued by that one. I want to test it out, but finding an image has proven difficult.