I haven't thought twice about where "lorem ipsum" was from. It's fascinating how much history there is behind something so inconsequential. And I'm glad that some people still dig for answers when most just parrot falsehoods.

| Techblog | https://utcc.utoronto.ca/~cks/space/blog/ |
| Github | https://github.com/siebenmann |
| Flickr | https://www.flickr.com/photos/22276923@N06/ |
I haven't thought twice about where "lorem ipsum" was from. It's fascinating how much history there is behind something so inconsequential. And I'm glad that some people still dig for answers when most just parrot falsehoods.

Blog post: When su replaced login for becoming another Unix login https://utcc.utoronto.ca/~cks/space/blog/unix/SuAsLoginReplacement
tl;dr: System III, and then this was half-adopted by 4.3 BSD. But in the process I learned that up through V6, su only let you become the superuser. Only in V7 did su let you become any UID.
Sparked by @simontatham 's https://www.chiark.greenend.org.uk/~sgtatham/quasiblog/tron-legacy/
Every Kuwubernetes cluster promises a beautifully architected and orchestrated design that flexes effortlessly with demand
but actually delivers all the elegance of six famished ferrets thrown directly into the spaghetti pot, and all the resilience of a 1975 business office that can't balance the ledger and close out the month when Pat takes a week off to visit Cancún
edit: the typo stands, it is henceforth Kuwubernetes eternally
People who have small enough Emacs configurations to keep it in one file have more restraint and discipline than I have, even if a decent chunk of mine is comments.
(3701 lines total, which is apparently 1414 lines of comments, 20008 lines of code, and 279 blank lines. There's some duplication of standard bits across files. Scc¹ produces amusing cost estimates for it. The largest amount of stuff is for MH-E.)

Sloc, Cloc and Code: scc is a very fast accurate code counter with complexity calculations and COCOMO estimates written in pure Go - boyter/scc
My taste in IDE-like experiences is for them to be mostly program text in (possibly split) windows, which is something Acme delivers, and I've always liked the core Acme ideas (although in practice it's a bit too minimal for me).
This is probably also why I like GNU Emacs' LSP support with Eglot. Most of the super-smarts are out of the way unless I want them, and it's all program text all the time by default.
I was wondering (for Reasons) if there was any LSP server support for Acme¹, and it turns out that there is, https://github.com/9fans/acme-lsp . This isn't as crazy as you'd think; a lot of code navigation interactions with a LSP server are basically you asking it for things and it giving you results back, and you can do that via Acme style commands and interactions.
¹ https://9fans.github.io/plan9port/man/man1/acme.html also https://en.wikipedia.org/wiki/Acme_(text_editor)
psst
hey you, with the eyes 👀
stop being stubborn and increase your computer's default font size. magnify that web page you're reading a bit
maybe try a different display font, most things default to sans fonts these days but I personally find serifs much easier to read, especially at, ahem, bigger font sizes
also, if light mode hurts your eyes, there's a significant chance the problem is that you bought a new monitor that gets 10x brighter than your old monitor and you turned it up to 100% brightness out of habit
Today's bike club group ride¹ was a classic ride that started at Taddle Creek Park, went up the St Clair hill, over to the Beltline, down through a bit of Prospect Cemetary, and then sideways to skip the giant hill in favor of a nice tunnel under the railway tracks that got us down to Davenport, over to Shaw, down to Harbord so we could go past Pedaal, and up to Future Bakery on Bloor where the ride de facto ends. It was fun and slow-paced (as Tuesday rides are).
The first warning arrived on a Tuesday morning, six weeks after consultants advised moving away from dependency on six hundred small excel scripts - and nobody at Zenith Ledger Advisory paid much attention.
It appeared in the system dashboard between routine audit notifications and a maintenance reminder