I'm now doubly-glad since it seems like, indeed, the bdfl has lost both the plot and the B. The fact that Omarchy is also some weird corporate-sponsored AI-pilled linux reskin is further concerning.

In retrospect, his jamming of things like thruster, hotwire, etc etc into the framework and then now basically abandoning them has me grateful I didn't adopt them, even though I thought they seemed pretty well-intended at the time.

Accommodated employees perform better. Non-accommodated employees perform worse.

For some people, an office is an accommodation - they need that not-home space with other people in it. For others, a home office is an accommodation - a very convenient/local space with very few distractions.

It should come as absolutely no surprise that putting someone somewhere they do not feel accommodated is going to reduce performance.

I also really reject this boomer-esque idea that in-office helps underperformers underperform less. Instead I find it helps under-performers _appear_ to underperform less because they can chat up the boss and more visibly do performative stuff like showing up early or leaving late.

But good god, the second it gets to anything concurrency-related, it just loses its mind. As much as it's gotten vaguely ok to try to let the agents loose on some bits of the codebase, they simply can't even do table stakes stuff with the kinds of concurrency you see in real life.

So this seems to make a lot of sense to me and I'll be glad to have the functionality, especially when PDF functionality is such a mess in the general world (lots of barely-working software).

This "It's not (just) X, it's Y." pattern is so LLM-y it's almost hard to read it now.

But I'm very distracted by Germany - what happened/is happening there that they're faring so much worse than, say, France? (And in several of the cited measures, worse than the UK too?)

Separately: Once you hit a certain threshold, you get an account rep and can ask for IC+ billing. This is sometimes better than the blended/sticker rate.

And furthermore, once you're really big enough, you can negotiate down Stripe's markup on the interchange. (As with any big enterprise contract).

(You'll forgive me for conflating humanity and intelligence - we are homo spaiens, after all. Thinking man.)

I'm not _confused_ why these "AI" "Labs" are using that definition though. It's extremely clear they're trying to eliminate the need for the non-owner class. They're not selling LLMs (some companies are, but not these companies). These companies are selling the idea of labor without laborers to people who hate and fear laborers - and their utter dependence on them - more than anything else in their lives.

Really looking forward to the scam collapsing. Crypto wasn't very satisfying to me because too many of the victims were just idiots. This time, it's class warfare.

Luckily for planetary overlord hopefuls, you probably don't need the whole package to become overlord. Just machines that can build machines.

I will remark that I don't really understand why any of the current idiot overlord hopefuls even want the job. The entire world is _already_ functionally their slaves. The only thing jeff bezos doesn't have that I can imagine he wants is the world to not think he's an asshole. But short of complete genocide of the human race, I don't think even overlord status will make progress on that. Might even be counterproductive.

Theoretically, they could just split out "explicit" vs "normal" risk categories, but there's two top problems there: 1) it's just fundamentally a smaller-yet-way-more-annoying category than the rest of their payments, and 2) tons of your partners (banks etc etc) have blanket-banned for all of the above reasons.

So... here we are.

In general, the people against these kinds of things aren't against the simple extra check of something that's theoretically already true (registered to vote / ID at voting place, citizenship at banks, etc). They're against forcing people to provide arcane, asterisk-ridden (including married women! a large demographic!) documents.

If we just had a normal federal ID system like a normal country, where you just got one mailed to you when your kid was born just like their social security card manages to do, then this would all be much more fine. But noooo god forbid we be normal for once. Much better to keep using random bullshit in place of a national ID.

For example, ruby uses blocks a lot. Ruby blocks are curious little thingies because they are arguably just syntax sugar for a HOF, but man it's great syntax sugar. Python then has "yield" which is simultaneously the same keyword ruby uses for blocks, but works fundamentally differently (instead of just a HOF, it's for generating an iterator/generator) and while there are some decorators that can use yield's ability to "pause" execution in the function to send control flow back out of the function for a moment (@contextmanager) which feels _even more_ like ruby blocks, it's a rather limited trick and requires the decorator to adapt the Generator to a context manager and there's just no good way to generalize that.

Somehow this is the perfect storm to make LLMs completely incapable of converting ruby code that uses blocks for more than the basic iteration used in the stdlib. It will try to port to python code that is either nonsensical, or uses yield incorrectly and doesn't actually work (and in a way that type checkers can even spot). And furthermore, even if you can technically whack it with a hammer until it works with yield, it's often not at all the way to do it. Ruby devs use blocks not-uncommonly while python devs are not really going to be using yield often at all, perhaps outside of @contextmanager. So the right move is usually to just restructure control flow to not need to use blocks/HOFs (or double down and explicitly pass in a function). (Rubyists will cringe at this, and rightly so... Ruby is often extraordinarily expressive).

The fact that such a simple language feature trips them up so completely is pretty odd to me. I guess maybe their training data doesn't include a lot of ruby-to-python conversions. Maybe that's indicative of something, but I digress.

I also think that AI might be the beginning of the end of copyright. While before, everyone with money clearly had tremendous incentive to keep copyright strong, now all of a sudden trillions of dollars are basically predicated on the idea that LLMs aren't violating copyright. Copyleft has been a major tool in the FOSS toolbox. If that's weakening, I don't ALSO want free software to be locked out of agentic programming too.

This comes as the latest concern of mine in a long line around "how software gets written" remaining free-as-in-freedom. I've always been really uneasy about how reliant many programming languages were on Jetbrains editors, only vaguely comforted by their "open-core" offering, which naturally only existed for languages with strong OSS competition for IDEs (so... java and python, really). "Intellisense" seemed very expensive to implement and was hugely helpful in writing programs without stopping every 4 seconds to look up whether removing whitespace at the end of a line is trim, strip, or something else in this language. I was naturally pleased to see language servers take off, even if it was much to my chagrin that it came from Microsoft, who clearly was out of open standards to EEE and decided to speed up the process by making some new ones.

Now LLMs are the next big worry of mine. It seems pretty bad for free and open software if the "2-person project, funded indirectly by the welfare state of a nordic or eastern-european nation" model that drives ridiculously important core libre/OSS libraries now is even less able to compete with trillion dollar corporations.

Open-weight, quantized, but still __good__ models seem like the only way out. I remain somewhat hopeful just from how far local models have come - they're significantly more usable than they were a year ago, and we've got more tools like LM Studio etc making running them easy. But there's still a good way to go.

I'll be sad if a "programming laptop" ends up going from "literally anything that can run debian" to "yeah you need an RTX 7090, 128GB of VRAM, and the 2kW wearable power supply backpack addon at a minimum".