Quite the contrary, the fragmented ecosystem is holding RISC-V back.
There are currently 3 variants of LoongArch ISA.
The reduced 32-bit version targets MCUs.
And LoongArch64 ATX/MATX motherboards with UEFI support is readily available.
This makes it far more easier to develop with LoongArch.
What evidence do you have that RISC-V is being held back by fragmentation?
Every upcoming general purpose RISC-V core I'm aware of is targeting RVA23. That's even less fragmentation than x86 has.
Meanwhile, I don't know of ANY third-party chip designs using LoongArch, so asserting no fragmentation seems to be misrepresenting the situation a bit.
Yes, distributing non-free, patented code that requires a license, requires a license. The same goes for Debian actually[1], including blocking requests and removing packages that were included before by mistake.
I would even dare say that this is another point for Fedora, enabling
https://rpmfusion.org/ is a one-liner and feels entirely native, never a broken package.
In case you haven’t noticed, we’re not formally at war yet. The US historically doesn’t make the first move since we’re a democratic republic and most constituents do not like war; it would also alienate most of our nominal allies. The best the US can do right now is containment and being ready to cut the supply lines from the Middle East.
There are currently 3 variants of LoongArch ISA. The reduced 32-bit version targets MCUs. And LoongArch64 ATX/MATX motherboards with UEFI support is readily available. This makes it far more easier to develop with LoongArch.