Right, what it does is give you *some* extra type safety without introducing lifetime bounds (T: 'a) into the language. If you want to store a reference in a struct, you either use a raw pointer (*T) (unsafe) or use a reference counted pointer (safe).

... Manual memory allocation is an option, especially with `defer` (eg. Zig), but not ideal. I'm looking at something between Swift's built-in reference counting, second-class references[0] (borrow checker lite), and RAII (it's too good to pass).

[0]: borretti.me/article/seco...

A modern commodore basic is directionaly right!

Memory management is a really important topic: the Radiant is designed as a hard realtime system, so we're going to avoid having a GC. On the other hand, Rust's borrow checker is pretty heavy handed and complex...

Likely something much more integrated into the OS ... with vim keybindings ;)

In all seriousness, I think we can do a lot better when it comes to editors, especially with deep language integration.

Interesting read, thanks. I think we need to strike a balance: having it to automated means that we stop paying attention and just pass on all capabilities down, always. Having it too manual will lead to the same situation..

I have one set up under radiant.computer/log/rss.xml -- does that work?

4. Many people seem to confound AI companies and AI slop with the technology that is AI. Today it may all look like the same thing, but eventually there will be more than one way to harness the technology. We will find a principled way to do it.

2. Generative AI is just computation, but a new kind of it. Discriminating against it doesn't make sense if you think computers are cool.

3. AI is actually useful and will only get more useful with time. Most of the people who don't want AI today will want it in 5 years.

Yes, Midjourney. If I had more time, I would do it myself!

Haha, thanks I will consider this.

Do you mean something like Unison? (www.unison-lang.org)

As for global content-addressability yes I think that makes sense, we built something like that for @radicle.xyz -- it doesn't have to be complicated.

We've got a long journey ahead, but I'm hoping to find people along the way who believe in this future, and want to help us build it.

In the meantime, you can follow our progress on @radiant.computer or write us.

🌅

Neither will it use an existing programming language. To that effect I've been working on Radiance, the native language of the Radiant system; and R', its subset.

radiant.computer/system/radia...

It's still very early days. I started the project beginning of this year, and have been full time on it since August.

There is a lot to do. To fulfill the promise of personal computing, we have to question everything down to the OS layer.

Radiant won't be based on any pre-existing OS or kernel.

Says the guy who takes money from the German government.. nice try.