Yep, so named because it was a heroisch (heroic; strong) painkiller.

Okay, let’s skip the formal logic talk then and go straight to linguistics.

The question “Good to merge?” does not contain a grammatical error. It is perfectly well-formed by the grammar that native English speakers actually follow in everyday communication. A grammar that fails to parse “Good to merge?” in context cannot parse native English speakers’ actual output.

Schoolbook English is not native English, because it’s not how native English speakers actually speak. Schoolbook English contains rules that directly contradict native English speakers’ everyday usage.

(Standard examples include the rule against split infinitives and the rule against ending a sentence with a preposition. These are not grammatical rules of English as it is spoken by native speakers. To boldly assert them is silliness up with which I will not put.)

The guideline (as applied) contains a contradiction, so the principle of explosion applies.

Specifically, there is a contradiction between “native-sounding English” and “no grammatical errors”, when the latter phrase is interpreted in the manner seen here. Native speakers quite often use sentence fragments and in other ways do not follow schoolbook “proper grammar”. In fact, second-language learners often use schoolbook grammar where a native speaker would use a more relaxed register.

Since the guideline contains a contradiction, it is either impossible to follow (i.e. forbids all communication whatsoever) or impossible to violate (i.e. forbids no communication).

But if someone creates a file called HEAD, should it overwrite a file called head?

That shouldn’t matter to the “nontechnical” end-user at all. To the nontechnical user, even the abstraction of “creating a file” has largely gone away. You create a document, and changes you make to it are automatically persisted to storage, either local or cloud.

Only the technical command-line user cares about whether /usr/bin/HEAD and /usr/bin/head are the same path. And only in a specific circumstance — such as the early days of Mac OS X, where the Macintosh and Unix cultures collided — could the bug that I described emerge.

I recall a case-insensitivity bug from the early days of Mac OS X.

There are three command-line utilities that are distributed as part of the Perl HTTP library: GET, HEAD, and POST. These are for performing the HTTP operations of those names from the command line.

But there’s also a POSIX-standard utility for extracting the first few lines of a text file. It’s called head.

I think you see where I’m going with this. HEAD and head are the same name in a case-insensitive filesystem such as the classic Mac filesystem. They are different names on a Unix-style filesystem.

Installing /usr/bin/HEAD from libwww-perl onto a Mac with the classic filesystem overwrote /usr/bin/head and broke various things.

I recommend picking up Graham Hutton’s short text Programming in Haskell, Second Edition. Even if you don’t end up using Haskell in “real work” (and you might!) it will teach you a remarkable number of things about how functional programming works.

The term “open source software” was coined specifically to refer to software licensing that recognizes a particular set of freedoms. It is not a generic term for source-available software, and never was.

One of the freedoms of open source is “no discrimination against fields of endeavor.”

Calling the Hippocratic license family “open source” is inaccurate, since its entire goal is to discriminate against certain fields of endeavor.

It’s better described as a sort of source-available license.

To be clear, I mean people who praise Hitler, get swastika tattoos, blame everything on a Jewish Conspiracy, etc.

You know, Nazis.

Not really. Nazis are scum and deserve to be kicked out.

Maybe don’t use mental health to attack people you disapprove of? The point of mental health is to help people, not to attack them.

Originally a Drumpf was a drummer; i.e. one who makes their living off of hitting up skin heads.

• The compiler hates you
• The compiler sees nothing wrong with your code and is just giving error messages to look busy
• The compiler was written by a maniac with a semicolon fixation
• The compiler could optimize your code, but it’s just not feeling it today
• The compiler wonders why you can’t match braces right like your brother does
• The compiler had a torrid affair with a Perl interpreter in 2006
• The compiler likes big butts and cannot lie
• The compiler wants to grow up to be an IDE but hasn’t told its parents they need to send it to GUI school yet
• The compiler reads Nazis on Twitter but only to make fun of them
• The compiler works for the Servants of Cthulhu

A hatchback full of SD cards can beat that easily, though.

Goddamn tree jizz!

Yep. This is why online recipe sites put a whole goddamn personal essay before the actual recipe: if someone scrapes the page and copies it, they’ll scrape the (copyrightable) essay as well as the (non-copyrightable) recipe.

Gotta admit, I originally wrote “old farts” and “young shits”, and decided that was too rude.

Federated platforms don’t die to corporate-type enshittification. They die to spam or elitism.

If operators fail to collaborate on keeping spam down, the platform becomes unusable or greatly-diminished due to spam. See Usenet for example — yes, it’s still around, but it’s greatly diminished from the 1990s. New projects and organizations don’t tell participants to subscribe to a Usenet newsgroup for discussion. (Curiously, email mailing-lists have outlived Usenet in this way, at least for technical projects. While email is federated, any given mailing-list is centralized.)

If the technology isn’t developed with an eye to new users’ needs and new use cases, because it’s “good enough” for the existing established users, the platform becomes dated and gets replaced by something trendy and corporate. This is IRC vs. Discord and Slack. IRC has a higher barrier to entry and infamously doesn’t work well on mobile — but it’s good enough for the old farts who care about it, while the young farts move to Discord instead.

I’m gonna smoke me a Mary J. Wana
Y’all ain’t can stop me, I’m totally gonna
Bake me a stoned like a sunny iguana
I’m gonna smoke me a Mary J. Wana

I’m gonna hash pipe to high me my head
Mellow my jello from born until dead
Teq’ me no 'quila, no pills blue and red
I’m gonna hash pipe to high me my head

I’m gonna weed me some grassical pots
Look you my dime bag 'cause that’s what I gots
Ain’t gonna shoot me no heroin shots
Just gonna weed me some grassical pots

Pot, weed, grass, ganja, herb, trees, green, chronic, reefer, doobage, dagga, dank, tea, …

The doctors were lied to, too; specifically about how long OxyContin is effective. Doctors aren’t wizards; they’re trained workers. If they’re given bad training, they reliably generate bad work.