cloudhead

I'm working on a new kind of computer. It's called the Radiant. I've been dissatisfied with the state of personal computing for many years now, so it's time I did something about it. If you think computers could be so much better than what they are, this is for you. radiant.computer

“Pseudo intelligence”

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.

This. It’s just as hard to write high quality code with agents, if not harder.

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!

LLMs are incredibly useful despite writing poor quality code, but we need better code review tools.

Progress on my TUI diff tool 👀

New #comics acquired!

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.

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

Radiant is open-sourcing its compiler toolchain and launching code.radiant.computer today.

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!

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...

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

Yes, this is a web-based Git repository browser created from scratch in a couple of hours using an LLM.

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...

Incompatibility allows true progress.

🪵 A new log entry was posted: "Radiance Intermediate Language" radiant.computer/log/011-radi...

"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...

‘What Remains of Edith Finch’ puts every other game I played recently to shame. What a crazy experience.

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).

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.

Interpreted languages have an edge in multi-agent workflows, because agents can't break the build for other agents. Compiled languages have an edge because they created more effective agentic loops. Languages with optional type-checking probably are the best of both worlds in this respect.