> RadiantOS treats your computer as an extension of your mind. It’s designed to capture your knowledge, habits, and workflows at the system layer. Data is interlinked like a personal wiki, not scattered across folders. This sounded really interesting... till I read this: > It’s an AI-native operating system. Artificial neural networks are built in and run locally. The OS understands what applications can do, what the…
Most of the text on the site seems LLM written as well. Given that the scope of the project involves making their own programming language, OS, and computing hardware, but they don't seem to have made very much tangible progress towards these goals, I don't understand why they decided to spend time making a fancy project site before they have anything to show. It makes me doubt that this will end up going anywhere.
Radiant Computer
161–165 of 165 posts
Re: Radiant Computer
#162Earlier quoted context omitted.
People had similar fears about OLE in Windows 95.
That’s kind of where my mind went too. They’re pitching this functionality for use by AI, but if it’s actually something like OLE or the Smalltalk browser or something like that where you can programmatically enumerate APIs, this has a lot of potential for non-AI use cases too that I generally find lacking in conventional platforms.
Re: Radiant Computer
#163I'm interested in the idea of a clean slate hardware/software system. I think being constrained to support existing hardware or software reduces opportunities for innovation on the other. I don't see that in this project. This isn't defined by a clean slate. It is defined by properties that it does not want to be. Off the top of my head I can think of a bunch of hardware architectures that would require all-new softw…
I am also interested and I have many ideas about it. However, although my ideas are different from many existing systems in many ways (in many ways that most operating system projects aren't), there are many similarities too, so they are not quite "truly radical".
> I think being constrained to support existing hardware or software reduces opportunities for innovation on the other.
I think this is correct. (My ideas are not intended to be constrained to support existing hardware and software, although emulation of other systems is still possible (NES/Famicom, Game Boy Advance, uxn, etc).)
> It is defined by properties that it does not want to be.
Although it is not sufficient by itself, I think that it is still helpful to define what it is not supposed to be, as well as what it is supposed to be.
Re: Radiant Computer
#164Earlier quoted context omitted.
Chatting on Discord is not actually your problem. Communicating with your friends and with random strangers who have the same parasocials as you is your problem. And the latter is artificial anyway.
The last Discord I joined was for a local math and formal methods meetup group in my area. The one before that was the official chat space for an open source project. I disapprove of both these groups choosing Discord to run their official chat on. Nonetheless, it's what they picked, so I need to use some kind of software to send messages to Discord's backend to communicate with these groups if I want to participate…
Re: Radiant Computer
#165The exokernel makes this a nonstarter if you ever want to run untrusted code, as it implies hardware takeovers, compromised peripherals/TPMs/drives/etc. especially when it claims to be AI first.
They defined the kernel as the smallest possible thing that would reliably multiplex hardware to the untrusted userspace components. So, network driver was a thing that would know just enough about the network card to put incoming packets in one of N queues based on e.g. a filter on some header values (some hardware will do this for you!). Or just enough to know that NIC 1 is reserved by component A so component B cannot have it (at this time) (VFIO hardware can present multiple virtual devices). A block storage driver was something that knew component A owned blocks 1-10000 and component B owned blocks 10001-20000 (these days, enterprise NVMe could partition into multiple virtual devices in hardware!). No network protocols, no filesystems etc in kernel, but still a central kernel that manages trust boundaries.