If you use the AI cores for general compute (eg. when compiling) then it is quite a bit faster than the RK3588.

At times, the above may vary as specific software may be less optimized on RISC-V.

Something like XLibre or Phoenix would have been taken very seriously 5 years ago.

There is also wors.

https://ruffle.rs

But the only standard you need is WASM. All browsers support it. Use whatever you want to make it. In fact, Ruffle is just a WASM app.

If one government wants to ban LLMs, it will be an incentive for another government to unchain them.

Genies and bottles.

XFCE is much more functional than CDE.

There are still Linux distros that will work on it. Adelie should. I think Arch32 as well. And Tinycore.

I am not as sure about Slackware but I believe the single-core (non-SMP) kernel runs on Pentium.

https://geopoliticaleconomy.com/2026/06/07/study-world-usa-b...

This is not a technology that they have a 10 year lead on. It is maybe 18 months until you can get Mythos from multiple places. And the US administration has no power to block them all.

Perhaps "RISC-V is now" will build some excitement. But there is a danger that it will ring even more hollow if we have to say it for 3 years before it rings true. RISC-V is inevitable and, for many use cases, it is soon. But for most people, it is certainly not now. RISC-V is still too slow and too expensive for most use cases outside of micro-controllers.

In the next 2-3 years, all that will change. RISC-V has a real shot at the embedded mid-range where the ARM product line has stagnated somewhat. RISC-V has caught up in performance, has the features, and is perhaps a bit better in terms of vectors and AI. With luck, we will see things like smart TVs and perhaps even phones. Real success in phones may take a few years of slowly chipping away though.

And on the server side, RISC-V has a chance to break-in. It is not going to put Intel, AMD, or ARM out of business just yet but it can start to build share. Specialized AI workflows offer a real opportunity.

For the SBC market, RISC-V is far too expensive given what it competes with. If RISC-V find volume elsewhere, this could change.

On the desktop/laptop, RISC-V is not even remotely a player. This will be the hardest market to break into. But any success ARM has makes it easier for RISC-V to follow. And once they are both there, what is the advantage of ARM again? Certainly not legacy compatibility.

RISC-V is inevitable. And its time certainly "starts" now. But I am not sure that RISC-V is now for most of us.

Ladybird uses AI to code. This is not them banning AI. This is them not wanting to take responsibility for the code WE write with AI. They think outside code contributions are raising their risk and slowing them down.

I dislike this change but it does not track to what you are saying at all.

Like always with Open Source, if you really believe what you are saying, fork the project. Outrun them if you can.

To my eye, this change does not appear to be driven by a change in corporate governance or profit motive.

They explain that the change and the timing is driven by two things.

1 - The burden and of processing public contributions has increased with the rise of AI

2 - They need to focus and stabliize the code base in preparation to introduce a public alpha

Those reasons ring true enough for me that I do not need to go looking for other motivations. I do not like this change but I can see why they would.