I think Fable 5 / GPT 5.6 write better code than the average open source developer now. My reaction to seeing an AI-generated OSS repo is starting to go from negative to neutral.
cloudhead
@cloudhead.io
Computers, graphics, protocols. Working on @radiant.computer Previously @radicle.xyz
This. It’s just as hard to write high quality code with agents, if not harder.
About the conversation around automatic programming, how useful or useless it is. Well, for me it is quite simple: you need to be very good to multiply your output. Retaining quality is harder now, but if you manage you are accelerated 100x. Instead of fighting I enjoy the race.
It would be cool if you could rebase a conversation with an LLM after editing one of the earlier prompts. Just like `git-rebase`, but over a chat log. This would allow edits to trickle down to all subsequent responses.
Vibed a little TUI to configure my Obsbot webcam under Linux, since there is no official software. Works great!
The major downside of vibe coding is that you end up with 1) much more code, and 2) badly factored code, which leads to 3) very poor token efficiency when making changes. It probably still all works, but the cost of maintenance and change grows much faster than for manually written/reviewed code.
LLMs are incredibly useful despite writing poor quality code, but we need better code review tools.
This is the right policy. The problem is not AI in itself, it's low quality contributions, which there are more of now. That is the root issue and that's what should be addressed, not the tools used by the contributor. github.com/rust-lang/le...
Policy proposal: No low-effort contributions · Issue #273 · rust-lang/leadership-council
Note EDIT(@jieyouxu): Please see #273 (comment) for the finalized wording and scope for the policy being proposed for disposition-merge, which is different from the text in this starting issue desc...
github.com
This is what the output of `git show` should look like. I've taken some of the work I did on terminal-based diff rendering for @radicle.dev and made it work as a general git-diff tool.
Good engineering + clever use of LLMs will become unbeatable. We're just getting started.
Radiance compiles itself in 0.2s from scratch on the experimental amd64 backend. It's fast 💨
Trying out autoresearch to reduce compiler code size. Not bad, let's see how much of it I'll keep.
An AST editor is always how I imagined the future of code editing -- text is just the visual representation of it, but the editor should operate directly on the AST. This also makes things like code formatters redundant. This is directionally right: ki-editor.org
Ki Editor | Ki Editor
Multi-cursor structural editor
ki-editor.org
Some more details about compiler bootstrapping, fixed points and trust. Though originally the fixed point was reached after 3 stages, it is now reached in 2!
🪵 Radiant Log #012 -- A fixed point has been reached. radiant.computer/log/012-radi...
The problem with agents is they don’t know what they don’t know. We humans do have an intuition for it.
The Radiance compiler has reached a fixed point. This means it can now compile itself and generate identical output to itself.
user> just fix all the bugs I'm tired and going to bed. llm> ok, I'll fix all the bugs. ... 8 hours later ... llm> Wait, the issue might be... Actually... blah blah llm> But wait! Let me just.. blah blah blah user> I'm going back to bed.
🪵 A new log entry was posted: "A.I. and the Future of Computing" radiant.computer/notes/ai-and...
A.I. and the Future of Computing
A new kind of personal computer
radiant.computer
1. Writing a compiler in C to compile Radiance to RV64 ✅ 2. Porting the C compiler in (1) to Radiance ✅ 3. Compiling the ported compiler in (2) with the compiler in (1) ✅ 4. Compiling the self-hosting Radiance compiler (3) with itself 💥😵💫
I can't think of anything more soul crushing in the UX space than trying to make a keyboard work on a smart phone's touchscreen. It simply is the wrong interface. In fact touchscreens are the wrong interface for most things. ios-countdown.win
Fix the iOS Keyboard
A countdown for Apple to fix the iOS keyboard or lose a customer.
ios-countdown.win
Yes, this is a web-based Git repository browser created from scratch in a couple of hours using an LLM.
Preparing to put sources online 🌐
Great talk about hardware/software co-design and why serious software developers should think about hardware. This is one of the core principles of @radiant.computer h/t @lorenz.leutgeb.xyz www.youtube.com/watch?v=v0Jj...
Bryan Cantrill: Andreessen’s Folly - The False Dichotomy of Software and Hardware
YouTube video by Jane Street
youtube.com
🪵 A new log entry was posted: "Radiance Intermediate Language" radiant.computer/log/011-radi...
Radiant Log #011
A new kind of personal computer
radiant.computer
"On Being a Computer Scientist in the Time of Collapse" is a really excellent and thought provoking read. I'm one of those optimists that is heavily criticized in this essay. web.cs.ucdavis.edu/~rogaway/pap...
web.cs.ucdavis.edu
‘What Remains of Edith Finch’ puts every other game I played recently to shame. What a crazy experience.
I've been in the deep end on the Radiance AST -> IR lowering pass, but I'm starting to see the light of day. I did things a bit differently this time in terms of code production, and I'm not sure it was worth it: I had Claude generate this compiler pass from scratch, which resulted in...
One of the greatest skills in software engineering is to know how much code is needed to implement any given feature. This lets you immediately tell, without reading the code, whether it doesn't account for something (code too short), or it's overcomplicating the solution (code too long).
Writing code has become a lot faster, but understanding code hasn't. What can we do about that?
The biggest problem with vibe coding is understanding the state of the code base at any given time. The reason to write code yourself, or to review all the code written by an agent is to have a clear mental model of the program. This is still a major bottleneck.