If anyone’s getting into nginx look into nginxinc/crossplane. That parser is particularly good if you’re trying to analyze or do sophisticated stuff with a huge nginx.conf. I have this one installed in my playground, here’s a quick and dirty demo:

There are a collection of poems called The Rubaiyat of Omar Khayyam. I saw references to one of its four liners in a random video clip of a show. That’s unexpected.

Oh, threats of Hell and Hopes of Paradise!
One thing at least is certain–This Life flies;
One thing is certain and the rest is Lies;
The Flower that once has blown for ever dies.

The translation on the third line is especially spiffy, and the fourth, sufficiently crafty (at least in my opinion).

I’m remembering something kind of amusing. I used to be big on portable documents until I discovered the ultra hard way how cryptic everything was underneath the hood. They’re good enough, but have any of you ever heard of the cracked WWF format (not wrestling)?

It was an encrypted portable document where the defining feature was to make printing technically impossible to save the world. Good thing it was .wwf and not .wwe. This might sound fantastical, but maybe it was really true.

I think someone asked. But is it possible to classically convert a PDF into JSON? And the answer is yes, yes you can. The feats of programming know no end (it’s out of my explanatory scope, sorry).

qpdf --json-output my.pdf my.json

I’m finally realizing that in the stack link of this post, there’s actually an entry about “grepping” the device. Everything’s a file or something. It feels comical.

Amusing yet confuzzling? If you happen to have GCC installed and it actually does this, it’s probably not gcc, but perhaps clang wrapped (or symlinked) in disguise. Operating systems and environments vary in peculiar ways.

There’s truly nothing more liberating than deleting all of your work by mistake (or having it deleted). That’s why it never hurts to have multiple distribution (and backup) strategies. A newer way is invented every day:

gcc -o delete-this-file.c

I came across an interesting site publishing social media trends. There are many countries in there, but that first link is for The Bahamas.

Someone sent me a link about XSLT getting deprecated. And, that’s expected. Welcome to the real world? Browser APIs are not as reliable as you’d think.

In fact, one can sus out the “true” APIs of anything by analyzing a company’s repositories for usages (Mozilla, Google, Apple). This allows you to guess at deprecations, wrongly.

I’m not an XML person, but if XSL transformations are interesting (like to Markdown), look at Paligo/xee (Rust). I think I wrote about extensible stylesheets (and Saxonica) somewhere after being impressed by XML pros in action.

I was asked before (online). And yes, I do know (almost precisely) the bot to human ratio for my sites. My audience in the real is known and small, and online discovery limited (search engines). I don’t need to look at the metrics per se.

I’m not exactly fond of the .md but a long time ago, I added inconspicuous Markdown links to one of my blogs. I tend to get these funny hunches.

Do you really think humans are clicking the .md? My running theory is that browser agents are programmed to consume less tokens.

I run across sites where I wonder if a time travelling comedy bit is happening. Check the dates on those cards.

This article from the year 2057 was actually useful. I was messing around with Python the other day.