cloudhead
@cloudhead.io
Computers, graphics, protocols.
Working on @radiant.computer
Previously @radicle.xyz
Working on @radiant.computer
Previously @radicle.xyz
Pinned
cloudhead
@cloudhead.io
· Nov 4
Radiant Computer
A new kind of personal computer
radiant.computer
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
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
Reposted by cloudhead
Radiance IR (RIR) tentative syntax. Below is example code for a simple loop that sums numbers.
December 17, 2025 at 10:20 PM
Radiance IR (RIR) tentative syntax. Below is example code for a simple loop that sums numbers.
Software can afford to be broken because it can be patched over the air, therefore most software is in a permanently broken state. ¯\(ツ)/¯
December 17, 2025 at 8:50 PM
Software can afford to be broken because it can be patched over the air, therefore most software is in a permanently broken state. ¯\(ツ)/¯
Here's a list of things I've saved countless hours on by using an LLM:
1. Writing tests for specific functions or branches
2. Documenting code
3. Finding the bug (regression) that causes a test to fail
4. Refactoring: renaming things, moving code around, changing function signatures, etc.
1. Writing tests for specific functions or branches
2. Documenting code
3. Finding the bug (regression) that causes a test to fail
4. Refactoring: renaming things, moving code around, changing function signatures, etc.
December 16, 2025 at 1:40 PM
Here's a list of things I've saved countless hours on by using an LLM:
1. Writing tests for specific functions or branches
2. Documenting code
3. Finding the bug (regression) that causes a test to fail
4. Refactoring: renaming things, moving code around, changing function signatures, etc.
1. Writing tests for specific functions or branches
2. Documenting code
3. Finding the bug (regression) that causes a test to fail
4. Refactoring: renaming things, moving code around, changing function signatures, etc.
Choosing an intermediate representation (IR) for Radiance is tricky — every language seems to do it differently, and many languages have multiple IRs, especially those that target LLVM.
Rust has MIR, Zig has ZIR, Swift has SIL.. I think I should just start simple and see what design falls out of it
Rust has MIR, Zig has ZIR, Swift has SIL.. I think I should just start simple and see what design falls out of it
December 15, 2025 at 10:40 AM
Choosing an intermediate representation (IR) for Radiance is tricky — every language seems to do it differently, and many languages have multiple IRs, especially those that target LLVM.
Rust has MIR, Zig has ZIR, Swift has SIL.. I think I should just start simple and see what design falls out of it
Rust has MIR, Zig has ZIR, Swift has SIL.. I think I should just start simple and see what design falls out of it
Just discovering Gleam (the programming language) and really like how sensible and minimal the language design is!
For example, there is no distinction between sum types and product types; they make it work by allowing field access without destructuring in simple cases. Very cool.
gleam.run
For example, there is no distinction between sum types and product types; they make it work by allowing field access without destructuring in simple cases. Very cool.
gleam.run
December 13, 2025 at 9:55 PM
Just discovering Gleam (the programming language) and really like how sensible and minimal the language design is!
For example, there is no distinction between sum types and product types; they make it work by allowing field access without destructuring in simple cases. Very cool.
gleam.run
For example, there is no distinction between sum types and product types; they make it work by allowing field access without destructuring in simple cases. Very cool.
gleam.run
What would an OS with built-in version control at the file system level look like?
December 13, 2025 at 1:15 PM
What would an OS with built-in version control at the file system level look like?
"Don't re-invent the wheel" is why our software has shit performance.
December 7, 2025 at 8:33 PM
"Don't re-invent the wheel" is why our software has shit performance.
There is something really freeing about coding LLM agents: they let you change your mind.
Previously, I'd avoid large mechanical code changes that weren't absolutely necessary, due to how much time it would take.
Now, changing my mind about a certain design decision is no big deal.
Previously, I'd avoid large mechanical code changes that weren't absolutely necessary, due to how much time it would take.
Now, changing my mind about a certain design decision is no big deal.
December 5, 2025 at 9:44 PM
There is something really freeing about coding LLM agents: they let you change your mind.
Previously, I'd avoid large mechanical code changes that weren't absolutely necessary, due to how much time it would take.
Now, changing my mind about a certain design decision is no big deal.
Previously, I'd avoid large mechanical code changes that weren't absolutely necessary, due to how much time it would take.
Now, changing my mind about a certain design decision is no big deal.
This was a lot of work, since it exposed several bugs in the C code generator and type checker that I had to fix, all the while ensuring parity between the C and R' code!
Making a compiler self-hosting is hard when the bootstrapping compiler isn't stable yet, but I'm eager to not touch C anymore!
Making a compiler self-hosting is hard when the bootstrapping compiler isn't stable yet, but I'm eager to not touch C anymore!
November 27, 2025 at 11:47 AM
This was a lot of work, since it exposed several bugs in the C code generator and type checker that I had to fix, all the while ensuring parity between the C and R' code!
Making a compiler self-hosting is hard when the bootstrapping compiler isn't stable yet, but I'm eager to not touch C anymore!
Making a compiler self-hosting is hard when the bootstrapping compiler isn't stable yet, but I'm eager to not touch C anymore!
When your BSS section is 17GB because you thought "eh, I'll think about memory allocation later and just use static memory for now" 😵💫
November 26, 2025 at 8:07 PM
When your BSS section is 17GB because you thought "eh, I'll think about memory allocation later and just use static memory for now" 😵💫
Sometimes you have some really serious design problem to solve, but you've got this itch to do something totally distracting and not relevant, like implement a Lisp, or some actor-based concurrency, and you start to convince yourself that this is actually the solution your problem, but it's a trick!
November 22, 2025 at 11:15 PM
Sometimes you have some really serious design problem to solve, but you've got this itch to do something totally distracting and not relevant, like implement a Lisp, or some actor-based concurrency, and you start to convince yourself that this is actually the solution your problem, but it's a trick!
Thinking about how to reduce the complexity of separate compilation.. 🤔
November 22, 2025 at 8:49 AM
Thinking about how to reduce the complexity of separate compilation.. 🤔
If there's a promising alternative to OSI licenses, I'm ready to adopt it for the entire @radiant.computer platform.
One of the reasons I've held out on putting any new code out in the last couple of years is because I don't want it to benefit my enemies.
One of the reasons I've held out on putting any new code out in the last couple of years is because I don't want it to benefit my enemies.
November 20, 2025 at 8:49 PM
If there's a promising alternative to OSI licenses, I'm ready to adopt it for the entire @radiant.computer platform.
One of the reasons I've held out on putting any new code out in the last couple of years is because I don't want it to benefit my enemies.
One of the reasons I've held out on putting any new code out in the last couple of years is because I don't want it to benefit my enemies.
I am so down for this -- I've been releasing software for 20 years under OSI-approved licenses, with the hope that this will empower individual users; but those who end up benefiting the most are likely Big Corps. We need a post open-source movement and better licenses.
Anti-fascistic software is made possible by pro-labor licensing.
I've been trying to write this piece for years. Every time I get started I'm just overwhelmed with paralyzing visions of the FOSS commentariat accusing me of WrongThink.
But I'm tired and we urgently need to get our shit together.
I've been trying to write this piece for years. Every time I get started I'm just overwhelmed with paralyzing visions of the FOSS commentariat accusing me of WrongThink.
But I'm tired and we urgently need to get our shit together.
Open Source Power
We have to talk about open source licensing.
blog.muni.town
November 20, 2025 at 8:30 PM
I am so down for this -- I've been releasing software for 20 years under OSI-approved licenses, with the hope that this will empower individual users; but those who end up benefiting the most are likely Big Corps. We need a post open-source movement and better licenses.
Reposted by cloudhead
Working on the module system implementation in R', getting the module graph setup.
package = compilation unit (equivalent to rust "crate")
module = namespace within package
package = compilation unit (equivalent to rust "crate")
module = namespace within package
November 12, 2025 at 12:07 PM
Working on the module system implementation in R', getting the module graph setup.
package = compilation unit (equivalent to rust "crate")
module = namespace within package
package = compilation unit (equivalent to rust "crate")
module = namespace within package
Of course, @radiant.computer ended up on the front page of HN, and of course, the main pushback is the idea of integrating AI with the OS. So here are some thoughts:
1. Betting against AI is dumb, and not having any plan on how to integrate AI in a new computer platform would be just as dumb.
1. Betting against AI is dumb, and not having any plan on how to integrate AI in a new computer platform would be just as dumb.
November 5, 2025 at 9:59 PM
Of course, @radiant.computer ended up on the front page of HN, and of course, the main pushback is the idea of integrating AI with the OS. So here are some thoughts:
1. Betting against AI is dumb, and not having any plan on how to integrate AI in a new computer platform would be just as dumb.
1. Betting against AI is dumb, and not having any plan on how to integrate AI in a new computer platform would be just as dumb.
Reposted by cloudhead
i'm excited for efforts like this. hardware & software *need* to be cohesive—designed as one.
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
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
Radiant Computer
A new kind of personal computer
radiant.computer
November 5, 2025 at 8:05 AM
i'm excited for efforts like this. hardware & software *need* to be cohesive—designed as one.
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
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
Radiant Computer
A new kind of personal computer
radiant.computer
November 4, 2025 at 11:02 PM
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
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
Last week I spoke at length about @radicle.xyz on the Hashing It Out podcast. Lots of interesting topics surrounding #p2p. Have a listen 🎧!
press.logos.co/podcasts/has...
press.logos.co/podcasts/has...
Cloudhead | Radicle - Logos Press Engine
In this episode, we interview Cloudhead from the Radicle project, discussing the intricacies of maintaining a peer-to-peer code collaboration platform. Cloudhead explains the challenges and innovation...
press.logos.co
May 16, 2024 at 3:08 PM
Last week I spoke at length about @radicle.xyz on the Hashing It Out podcast. Lots of interesting topics surrounding #p2p. Have a listen 🎧!
press.logos.co/podcasts/has...
press.logos.co/podcasts/has...