The cargo shorts stay ON during sex coding

A good write-up I came across 2 months ago: “Your container is not a sandbox” https://emirb.github.io/blog/microvm-2026/

Remind me of the spice harvesters from the recent Dune movies.

Forget charging “actual costs” for electricity, I think we should do like tax brackets and charge progressively more per kiloWatt-hour consumed. Let industry and corpo-sized services duke it out for who can consume the least, while protecting individual/personal use as well as small business, local-economy uses from the bigger actors throwing their weight around.

Who knows, we might even be able to ensure free electricity to keep the lights on for everyone with the right kind of bracketing.

Learned helplessness is an insidious foe, and one that market forces have tended to side with over the past 20 years (probably for far longer than that, but as I was a mere child back then I wouldn’t claim it with as much certainty).

It’s an “easy way” for those like you and me who have more or less already built up the know-how over countless small steps, but if you’ve never known “life” outside of these corporate surveillance playgrounds I imagine it seems very scary and deserted.

I would find it easier to agree with this article if it didn’t gloss over the shit quality LLM-generated code can have, nor that some of us love our craft because of how efficient and robust we are capable of making the code that we write. It’s not just about blood, sweat, and tears vs a quick prompt, it’s about knowing that the program that has been produced to go buy groceries isn’t going to make the machine run three times around the block balancing the eggs on it’s forehead before walking in the front door.

And I hate hate hate how I shudder at having written “it’s not (just) X, it’s Y”, but I refuse to strike that form of writing from my repertoire just because today’s behemoth stochastic parrots are “fond” of it.

From what I understand, it is the arch approach but with package binaries compiled to target newer hardware instead of the largest set of hardware. Their homepage claims they enable several performance-type optimizations in both the kernel and common system libraries. It’s not surprising to me that protondb, a repository of “how well can I get this game to run on Linux through proton?” reports, is studying an outsized proportion of users on CachyOS.

It’s not chatbot psychosis, it’s ‘math and engineering and neuroscience’

top-tier sneer from The Register

Your last paragraph reminds me of the following series of YouTube videos that goes over how to build a “correct” fluid simulation, starting at the quantum mechanical level (iirc): https://www.youtube.com/playlist?list=PLMoTR49uj6ld32zLVWmcGXaW7w2ey7Vh4.

Multiple scales of complexity and interaction, that’s way too computationally intensive to just directly stimulate how reality works, and so each scale has to be carefully “averaged out”, in a sense, to end up with a simulation that is cheap enough to run yet still behaves realistically and reproduces as many nuances as possible.

You can use me after free() all you want, babe

Yeah, go big or go home with this kind of stuff. Give me some Linux kernel source code, maybe even some well-known RFC!

Yup! YAML is defined as a “strict superset” of JSON (or at least, it was the last time I checked).

It’s a lot like markdown and HTML; when you want to write something deeply structured and somewhat complex you can always drop back/down to the format with explicit closing delimiters and it just works™.

Now you’re thinking with portals primes!

I recently read a lovely short story about this: https://sightlessscribbles.com/the-colonization-of-confidence/

tinfoil hat on: discord is a company based in the USA, the USA administration saw those teenagers in Nepal supposedly organise a revolt/revolution over discord, sees the inhabitants of Minneapolis organizing against ICE on Signal, and wants to preemptively know which of their citizens are using discord with which accounts in case any of them start organizing on discord.

I think this part references it, though it’s kinda solely in passing:

Production evaluations can elicit entirely new forms of misalignment before deployment. More importantly, despite being entirely derived from GPT-5 traffic, our evaluation shows the rise of a novel form of model misalignment in GPT-5.1 – dubbed “Calculator Hacking” internally. This behavior arose from a training-time bug that inadvertently rewarded superficial web-tool use, leading the model to use the browser tool as a calculator while behaving as if it had searched. This ultimately constituted the majority of GPT-5.1’s deceptive behaviors at deployment.

I guess it only makes sense that after Liquid Ass UI, we’d get Fuzzy Toilet Seat UI

ehehehehe thanks for that mental image

Of course, one can always reclaim that space if the data truly is inaccessible. Makes me want to write a joke program for “cleaning up” after ransomware that just removes the data from the partition table (or whatever the equivalent for files is - would that just be rm?)

shred -f -u

Out of the 4 comments other than yours, there are exactly 2 that recommend using a different distro.