...i posit that's a fair assessment of most vegans...
...ye gads man, the last time i coded was turbo pascal...
...bad actors win, and only winners are at liberty to build the future...
...you are here, today, as the living legacy of shameless exploitation, and the future belongs to the progeny of those shameless exploiters among us...
...yeah, i did fantastic in my GT classes but struggled in my regular classes due to the volume of busy-work...
...pathetic implies deserving of pity and stupid implies innocent ignorance...
"PING! The magic duck!
Using deft allegory, the authors have provided an insightful and intuitive explanation of one of Unix’s most venerable networking utilities.
Even more stunning is that they were clearly working with a very early beta of the program, as their book first appeared in 1933, years (decades!) before the operating system and network infrastructure were finalized.
The book describes networking in terms even a child could understand, choosing to anthropomorphize the underlying packet structure. The ping packet is described as a duck, who, with other packets (more ducks), spends a certain period of time on the host machine (the wise-eyed boat).
At the same time each day (I suspect this is scheduled under cron), the little packets (ducks) exit the host (boat) by way of a bridge (a bridge). From the bridge, the packets travel onto the internet (here embodied by the Yangtze River).
The title character — er, packet, is called Ping. Ping meanders around the river before being received by another host (another boat). He spends a brief time on the other boat, but eventually returns to his original host machine (the wise-eyed boat) somewhat the worse for wear.
If you need a good, high-level overview of the ping utility, this is the book. I can’t recommend it for most managers, as the technical aspects may be too overwhelming and the basic concepts too daunting.
As good as it is, The Story About Ping is not without its faults. There is no index, and though the ping(8) man pages cover the command line options well enough, some review of them seems to be in order. Likewise, in a book solely about Ping, I would have expected a more detailed overview of the ICMP packet structure.
But even with these problems, The Story About Ping has earned a place on my bookshelf, right between Stevens’ Advanced Programming in the Unix Environment, and my dog-eared copy of Dante’s seminal work on MS Windows, Inferno.
Who can read that passage on the Windows API (“Obscure, profound it was, and nebulous, So that by fixing on its depths my sight — Nothing whatever I discerned therein.”), without shaking their head with deep understanding. But I digress."
...wow, you just reminded me that i used to hear LEDs, too: i'd totally forgotten about that...anyway, i can vouch that commuting a couple of hours every day in a top-down roadster for twenty years makes the problem go away; heck, the tinnitus even drowns out a lot of electronic-feedback clicks and beeps which are supposed to be audible...
...it's driven by developer business models, the same reason lots grow narrow-and-deep: they're trying to maximise the market value of plattable land (square area) per infrastructure cost (linear streets + utilities), and narrow houses built right up to setback line means developers can squeeze the most 2500 ft^2^ mcmansions possible on their subdivided parcel...
view more: next ›
myrrh
0 post score0 comment score
joined 3 years ago
...my point is vorpal board does exactly this, and as far as i've searched it's the only VTT taking that approach toward making physical game materials accessible for remote play, provide your own rules...