Books

why's (poignant) Guide to Ruby? Learn You a Haskell for Great Good!? Learn Python the Hard Way?

Remember when books had titles like ``The C Programming Language'' or ``Structure and Interpretation of Computer Programs''? Informative titles that described the book's contents, without any ironic punctuation?

It's as if anyone under the age of 30 is incapable of reading a book unless it has some zany novelty, like poorly-drawn comics or a hip new twist.

The world has always been full of shit books.

>>2
Name one shit book released before 300 BC.

>>3
how the fuck would i know? i'm sure there were many.

300 BCE shitposts on rocks

>>5
I.2.20 (Bar/Brothel of Innulus and Papilio); 3932: Weep, you girls.  My penis has given you up.  Now it penetrates men’s behinds.  Goodbye, wondrous femininity!

I.2.23 (peristyle of the Tavern of Verecundus); 3951: Restitutus says: “Restituta, take off your tunic, please, and show us your hairy privates”.

I.4.5 (House of the Citharist; below a drawing of a man with a large nose); 2375: Amplicatus, I know that Icarus is buggering you.  Salvius wrote this.

going back to /BC/

I tried to read the ``le poignant ruby'' book, but got frustrated after six chapters didn't even explain anything about the language or runtime. They don't have to try to make this shit interesting; it's a naturally dry topic and we all know this going in.

it's a naturally dry topic and we all know this going in.
You have to get it more excited, then it should be more moist.

Why's poignant guide is a sad attempt to get more stoner art school dropouts to write "poetry in code" aka complete shit like why. Don't pay attention to books written by autistic savants

dubs

I like this thread

>>3
The Old Testament, Talmud, Quran, the list could go on.

>>13
Quaran wasn't before 300 BC moron.

>>14
Assalalasalami!

Programming Perl was a lot of fun, without needing to be stupid.