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 they expose, and how they fit together. It can integrate features automatically, without extra code. AI is used to extend your ability, help you understand the system and be your creative aid.
(From https://radiant.computer/system/os/)
That's... kind of a wierd thing to have? Other than that, it actually looks nice.
I don't think anyone denies the current utility of AI. A big problem of the current OSes is that AI features are clumsily bolted on without proper context. If the entire system is designed from the ground up for AI and the model runs locally, perhaps many of the current issues will be diminished.
I do. "AI" is not trustworthy enough to be anything but "clumsily bolted on without proper context."
They haven't done their due diligence: there's already a well-known language named R: https://www.r-project.org/. The prime isn't sufficient disambiguation.
An admirable goal. However putting that next to a bunch of AI slop artwork and this statement...
> One of our goals is to explore how an A.I.-native computer system can enhance the creative process, all while keeping data private.
...is comically out of touch.
The intersection between "I want simple and understandable computing systems" and "I want AI" is basically zero. (Yes, I'm sure some of you exist, my point is that you're combining a slim segment of users who want this approach to tech with another slim segment of users who want AI.)
mwcampbell•25m ago
nicksergeant•21m ago
debo_•21m ago
d-us-vb•17m ago
What is a screen reader but something that can read the screen? It needs metadata from the GUI, which ought to be available if the system is correctly architected. It needs navigation order, which ought to be something that can be added later with a separate metadata channel (since navigation order should be completely decoupled from the implementation of the GUI).
The other topic of accessibility a la Steve Yegge: the entire system should be approachable to non-experts. That's already in their mission statement.
I think that the systems of the past have trained us to expect a lack of dynamism and configurability. There is some value to supporting existing screen-readers, like ORCA, since power users have scripts and whatnot. But my take is that if you provide a good mechanism that supports the primitive functionality and support generalized extensibility, then new and better systems can emerge organically. I don't use accessibility software, but I can't imagine it's perfect. It's probably ripe for its own reformation as well.