Cowsay and Rewarding HTML

2019-02-17T19:43:43-0600

• english
• web
• unix

Cowsay and Rewarding HTML

date: Sun, 17 Feb 2019 19:43:43 -0600 tags: english web unix

There’s something that’s becoming more and more a relic today, thanks to “Web 2.0”: HTML that’s rewarding to read.

Tell me, if you had to read one, which of these two would you actually not mind reading?

I don’t know about you, but I’d rather slam my skull against my desk than read B in any timeline, in any context.

But isn’t it obvious why B is so much worse than A? Clearly, someone had their hand in A, manually typing up the HTML, or at least lovingly creating its template. Whereas B was almost certainly generated with entirely non-cohesive templates, randomly strung together in a syntaxically-acceptable order— but not a human-acceptable order. The entirety of the news article (sans the script-loading) is on a single line; just look at the horizontal scroll-bar! There are only 34 lines in the page! It’s completely impossible to sift through.

Rewarding HTML

There’s a reason why almost every “Learn to Code” book says to read other people’s code. People learn by example. There might be billions of courses and cheat-sheets and videos on HTML, but there really is no replacement for learning from others work. That’s how you learn the ins and outs, good practice from bad, what is acceptable and what isn't— otherwise, you’re just learning what’s syntaxically valid, the bare minimum of understanding anything. It’s like learning vocabulary without grammar itself.

If everyone’s HTML is like B, how will people learn to code HTML? The only options are “terribly” or “not at all.” When you decide to “not at all” learn HTML, what’re you going to turn to? WordPress, Wix, GoDaddy, the sort. Bloated, anti-semantic, proprietary, HTML generators that, predictably, make even more ugly HTML. Which in turn, makes it harder to learn good practice, and makes even more people turn to generators.

Even if you don’t consider “good HTML practice” important— “that’s for nerds, I hate nerds”— think about how ugly HTML discourages curiosity.

I know, it might seem like a reach, but think about why people learn to program, why people like to look at the insides of their computer, or the toaster oven they’ve promptly disassembled— they are curious. Closing off an avenue to satisfy curiosity discourages curiosity itself, no matter how slightly. It re-enforces the idea that they can’t understand “computer stuff”, that it’s out of their reach. That only “smart people” can understand it. It exacerbates what makes tech “meritocracy” so problematic in the first place.

I’d prefer to live in a world where curiosity is satisfied and encouraged, and where people can feel like technology is genuinely grokable.

Cowsay

And it's *always* rewarding to see a cute little message, or some ASCII art, or even a job-offer in an HTML comment. What better way can you reward curiosity than through cute source-code? How can technology seem more approachable than with a friendly note to readers?

Enter cowsay(1)— a really nice Perl program (that's a bloody classic and should absolutely be included in every operating system's base installation). It prints a cute little ASCII cow saying whatever message you pass onto it.

 ________________________________________ 
/ why did the cow cross the road? to get \
\ to the other side!                     /
 ———————————————————— 
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||——w |
                ||     ||

Plainly, cowsay's absolutely perfect for making friendly comments in HTML!

Oh, wait…

Apparently, since cowsay outputs more hyphens than XML 1.0 allows, you've got to get rid of them in order for the validator to, well, give you friendly validation. So you could replace them every time you print a cow in HTML… but wouldn't it be nicer to have a genuine fix?

So I spent a while trying to figure out how to replace the hyphens in the program's “cow” file format (just some Perl code with variables set), hoping that I could replace them through that. But it turns out the speech bubbles are made by the program itself— so you need both a custom “cow” file *and* a patch to the program itself, in order to print underscores instead of hyphens.

The cowsay patch itself is pretty simple:

139c139
<         " " . ("-" x $max2) . " \n"
—-
>         " \\" . ("_" x $max) . "/ \n"

And the change to the original “default.cow” is pretty minimal, too:

5,6c5
<              $tongue ||____  |
<                 ||    w||
—-
>              $tongue ||——w |

After that, the result's a little something like this:

 _________________________________________ 
/ i like to lie down and watch the stars. \
\ mainly when dumb kids tip me over...    /
 \_______________________________________/ 
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||____  |
                ||    w||
                ||     ||

Just apply those patches (with the patch(1) command) and you can easily make your milky comments, and thus encourage curiosity itself! :)