- 4 Posts
- 9 Comments
0·1 year agoPlus the fact that it was reasonably practical to haul that bed around speaks to spacious passage ways
I’m too scandinavian to understand. Please explain.
EDIT: Looming shutdown due to McCarthy thinking he could toilet train the more disgusting segment of his menagerie. Thanks.
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
0·1 year agoI have an unhealthy fascination with far right shit heads, chief among them Alex Jones. And as an avid listener of Knowledge Fight I can tell you that the predictions once the invasion started didn’t just age like milk; Enough cheese was made to feed the entire sub-saharan subcontinent.
If windows didn’t exist, linux would dominate with the problems you describe, and we’d still see this meme, but advocating for FreeBSD instead.
That being said, I like them both. It’s been a while since I last used bsd, so I think it’s about time I give it another spin.
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.
It’s NOT just a stick. It’s a nice stick, which means its uses are many.