building @ladybirdbrowser. recovering addict. husband of @katalinkult. uncle. gymnasium brother.
Sweden
- Tweets 11,811
- Following 2,212
- Followers 64,517
- Likes 46,704
Pinned Tweet
I don't care about having "fuck you" money, but I would like to create some software with "fuck you" performance.
32
31
942
40,168
Open source is indeed evolving.
If I were GitHub, I would be building for this new model instead of clinging to PRs as the center of OSS collaboration.
PRs have always been a risk/reward calculation, but because code was expensive to produce, reward outweighed the risk.
The cost of producing code is falling fast, but the risk hasn't gone down at all. I would argue it is growing.
We should reorient OSS development around issues as the main contribution vehicle, and treat code generation as an implementation detail.
I see this less as GitHub failing and more as open source evolving.
The current workflow is increasingly absurd: someone uses AI to generate a PR, I use a better AI to review it, then their AI and my AI go back and forth until we converge. Add AI-generated spam on top, and the human is mostly just acting as a router between agents.
I’d rather skip that entire loop.
Imagine you use a project and want a feature. You go to the repo and describe what you want. The project’s AI already knows its conventions, preferences, history, rejected ideas, and boundaries. It can immediately tell you whether the idea is likely to fit and what shape it should take.
If it makes sense, you press a button and the project’s chosen AI implements it, validates it, and presents the maintainer with the request and the code as one thing.
No separate issue. No PR ping-pong. No two AIs talking through two humans.
What AI still canot replace is taste: deciding what a project should be, what belongs in it, and where its boundaries are.
19
8
143
7,744
Andreas Kling retweeted
Due to AI, I have disabled external pull requests on all my repos.
Open source, as we have known it, was fun while it lasted. (It’s been 15 years for me)
I will still maintain projects and handle issues.
141
115
2,473
524,130
People who dislike AI tell me that I'm preaching too much about AI.
I'm not trying to convince anyone to use AI. Do whatever you want bro.
I'm trying to make people think ahead and extrapolate where things are going, whether they personally use AI or not.
25
4
252
7,983
To understand the future of open source software, it’s important to look at the XZ Utils backdoor attack.
Imagine the potential value of such a vulnerability existing.
Imagine the time and effort involved in getting it into place.
Now imagine you wanted to put as many of those vulnerabilities in as many software programs as possible.
How would you do it before AI agents existed? How would you do it now?
21
7
185
13,550
Stages of grief about the effect of AI on open source.
Denial:
- AI code is slop! Nobody serious will use this.
- Open source will keep working exactly like it always has.
Anger:
- These AI slop PRs are ruining GitHub!
- Ban AI-generated code!
- If you close PRs, you're not open source anymore!
Bargaining:
- Okay, AI can write code, but only if a human reviews every line.
- Maybe adversarial AI review will make arbitrary external code intake safe again.
Depression:
- Wait, if code generation is basically free, what is a contribution anymore?
- Is GitHub-style open source culture just going away?
Acceptance:
- Open source is still open source, even if the contribution model evolves.
- Good issues, test cases, benchmarks, specifications, and ideas become the scarce inputs.
- Upstream may stop accepting arbitrary code while forking becomes much easier.
Bonus stage! Reconstruction:
- Projects redesign around maintainer-controlled agents, issue-driven development, stronger test/validation infrastructure, and new ways for contributors to earn trust.
58
51
461
39,877
mfw another "reporter from Bloomberg/TechCrunch" really "loves my work" and wants to "schedule a call"
6
1
152
6,530
Andreas Kling retweeted
We also turned off Coolify's PR for non-contributors two days ago.
Reviewing full AI, untested PRs takes a lot of time and we waste so much on them.
This is a temporary experiment.
Every OSS project that matters will do this, soon. If you’ve always wanted to get a PR in somewhere, now is the time.
7
3
87
6,839
Zoomers who grew up in the GitHub era keep telling me that closing PRs means projects are no longer open source.
Obviously, all the requirements for open source still apply. Public code intake was never part of the definition; it was just a popular contribution model for a time.
51
10
562
17,063
Yeah, this is clearly where things are going. We all have feelings about it, but that doesn't change anything.
My addition: there's no future where you're accepting code contributions from strangers if your software needs to be secure. Pull requests are over, file issues!
It takes a while to build the confidence, but there's no future where you're manually reviewing every line of agent code. Not much acceleration in that. You need adversarial agent reviews, you need automated testing, and maybe you spot check. That's it. From prompt to production!
30
8
326
36,268
The best defense against scammers posing as tech journalists is understanding you have nothing to gain from talking to tech journalists.
9
5
221
7,928
Dinner with extended family members last night, none of them working in tech.
A: I do all my Google searches in ChatGPT now! It's so fast! Crazy how things change!
B: I heard on the radio that AI may destroy humanity soon. Andreas?? Is this true???
C: I use AI all day at work, and it's clear it will do my entire job within a year or two. I am trying to get promoted to management as soon as possible, so I can stay employed.
D: Hey what do I invest in to profit from all this AI stuff?
Reminder to go outside your bubble and hear a wide spectrum of perspectives 😅
25
4
486
37,742
Browsers should do CSS layout off the main thread! 🤓
Top left: @ladybirdbrowser (work in progress)
Others: Chrome, Safari, Firefox
48
52
1,505
61,526
Work in progress, but this is so fucking cool I just have to share..
I'm moving the entire CSS pipeline off the main thread in @ladybirdbrowser. This allows us to animate any CSS properties we want and they just keep going smoothly despite heavy JS execution!
Video demo is animating a bunch of flex and grid layouts while JS churns on the main thread. Same demo in Chrome for comparison.
Welcome to the future, bros 😎
41
39
1,198
35,559
