Radiant Computer

Radiant Computer

@radiant.computer

A personal computer for the next generation. https://radiant.computer

398 followers2 following32 posts

Work has started on the Radiant Kernel. * It’s an exokernel. Very minimal. * It uses ring buffers as the only syscall interface (think io_uring). * There is no virtual memory — protection works via static analysis. * There are no device drivers, software has direct hardware access.

View full thread

Also note that most of these compilers are optimized for incremental compilation. Radiance is optimized for whole program compilation. The only other language we know of that by design does not do incremental compilation is Jai.

All benchmarks are run on a single thread. Radiance compiles its own source code, while the other compilers are compiling synthetic code. When allowed to use multiple cores, Go was the fastest. Radiance isn't optimized for parallelism currently.

View full thread

The release includes `forge`, a simple read-only Git forge that supports SHA-256 repositories, and HTTPS cloning. Forge was entirely vibe-coded. Let us know if you encounter any issues with it.

The Radiance language is still in an early stage, but the compiler is already self-hosting. The compiler sits at around 18 KLOC. It has zero dependencies, meaning that it links and emits machine code directly. It also includes an intermediate language.

Radiance is not meant to be used outside of the Radiant system, at least for now. It requires a RISC-V emulator to run, and does not emit ELF-compatible binaries. It was designed to be small like C, but ergonomic like Rust. We're getting there. The compiler and emulator are MIT licensed.

Radiant Computer reposted

Working on the module system implementation in R', getting the module graph setup. package = compilation unit (equivalent to rust "crate") module = namespace within package

You are up to date.