"But humans also make bad PRs" and this is obviously true. But if I spend hours/days helping a human get a PR over the finish line I've taught that person how to do future PRs better. Maybe they never come back, but at a minimum I've taught another human something useful.

If I'm talking to an AI agent, there's a 100% chance that next session every nanosecond I put in reviewing the PR is wasted. The next PR even by the same "author", will have the same issue.

It's not sustainable.

4/4

"I have a PR here, if you have any suggestions just telnet into my Emacs session to make the changes you want."

It's just a lose/lose proposition, there will never be an upside to the project. There's only two possibilities for a substantilly AI generated PR:

1) It is perfect and we merge it as-is.
2) It is garbage and should be closed.

1) rarely happens, especially not today. People who heavily use AI for their PRs do so because they don't (want to) know the engine deeply enough.

3/x

PRs should be donations of someone's time and expertise. Not someone's donation of tokens bought from Anthropic/Google/OpenAI/whomever. *IF* we wanted to AI generate PRs at all (and we do not) then the useful way would be for someone to give use money to use an AI.

What is step 2 after the PR is submitted? I review and then the person "donating tokens" copy/pastes that into their Claude Code session? If I wanted to use Claude Code I'd be 1000x better off just using the tool.

2/x

This is a version of something I said in the #godot contributor chat, my views on #ai or #aislop

I don't want to wave away the various ethical concerns, particularly around using "public" AIs, given that a lot of them are literally powered by gas. But I want to push back against the idea that an AI authored PR would be good if the code was good. It is not.

A thread 1/x

The exact moment software went downhill was when #mozilla changed away from this.

#retrocomputing

My current thinking is that in order to make a resolution independent UI toolkit one must first have a resolution independent drawing library?

The things I've found on that were algorithms based on device independent pixels.

Is that still actually the state of the art?

My primary design constraint is that I want the scaling to be zero cost when there's no actual scaling happening.

Can anyone point me to some good books/posts on the subject?

#programming #uidesign #hidpi

Oh no, is this going to be my toot of the year?

Last year it was me destroying a DVD drive. Now this?

Next year I'll find a way to have ai destroy a DVD drive.

Not to brag, but if anthropic had paid me $20,000 and given me a month I'd also have been able to write them a very shitty C compiler.

I got to handle a @mntmn reform at #fosdem2026 it's a really nice machine to handle!

Better than the website makes it out to be; check out their store! https://mnt.re/

#repairabletech #europeanalternatives

Today I learned two important lessons. One of the lessons is that sometimes changing 1 line of code can take 5 hours.

The other lesson is enclosed in the following PR:

https://github.com/godotengine/godot/pull/100422

#programming #c #cplusplus #godotengine #eldrichhorror

What is this thing called?

Well. The "SpiderMan" obviously, what else?

#retrocomputing #modem #spiderman

Oh, and DB9 serial... pass through?

What can this possibly be for? (This is not rhetorical, I do not know).

#retrocomputing #modem

Oh... And a ... centronics cable?

I see...

#retrocomputing #modem #centronics

Oh look! An DB25 to DB9 converter! Useful for plugging into a #computer

#retrocomputing #modem

There was a power chord as well. Somewhat atypical...

Yeah, why NOT have a power strip integrated into your modem's power adapter?

#retrocomputing #modem #wtf

I went #thrifting yesterday. I found a #modem. It looked different than any other modem I had seen, so I got it.

First off, lovely color scheme!

🧵

#retrocomputing #hotpink #modem