I’m looking forward to using a RISC-V computer in 20 years
I already have one! (But it's technically a soldering iron...)
What is RISC-V and why it matters to Canonical
21–30 of 129 posts
Re: What is RISC-V and why it matters to Canonical
#22I’m looking forward to using a RISC-V computer in 20 years
This underestimates the will of governments and companies Europe and especially China to reduce their dependency on US-controlled technology.
ARM isn't US controlled, is it? British and also now Japanese since it's owned by SoftBank.
Meanwhile, wouldn't China be more heavily invested in Longsoon?
Re: What is RISC-V and why it matters to Canonical
#23I stopped listening to what Canonical says. They often get involved in things and disturb the ecosystem then abandon stuff or dig a "not invented here" hole.
Unity, Bazaar, Mir, Upstart, Snap, etc.
All of them had existing well established projects they attempted to uproot for no purpose other than Canonical wanted more control but they can't actually operate or maintain that control.
Re: What is RISC-V and why it matters to Canonical
#24I’m looking forward to using a RISC-V computer in 20 years
[deleted]
Re: What is RISC-V and why it matters to Canonical
#25Not my area of expertise but what exactly is the difference between RISC-V and Power PC? Didn't Power-PC get a good run in the 90s and 2000s? Just wondering why there's renewed interest in RISC-like architectures when industry already had a good exploration of that area.
x86_64 machines are RISC under the hood and have been for ages, I believe; microcode is translating your x64 instructions to risc instructions that run on the real CPU, or something akin to that. RISC never died, CISC did, but is still presented as the front-facing ISA because of compatibility.
Re: What is RISC-V and why it matters to Canonical
#26Re: What is RISC-V and why it matters to Canonical
#27Re: What is RISC-V and why it matters to Canonical
#28I stopped listening to what Canonical says. They often get involved in things and disturb the ecosystem then abandon stuff or dig a "not invented here" hole. Unity, Bazaar, Mir, Upstart, Snap, etc. All of them had existing well established projects they attempted to uproot for no purpose other than Canonical wanted more control but they can't actually operate or maintain that control.
Not sure on the timelines, but snap, upstart and Mir were all attempts at evolving Linux ecosystem that lost to RedHat-backed systems. Unity was legit abandoned, and bazaar... Not sure what they were trying to solve there with git and forges already existing.
Re: What is RISC-V and why it matters to Canonical
#29Not my area of expertise but what exactly is the difference between RISC-V and Power PC? Didn't Power-PC get a good run in the 90s and 2000s? Just wondering why there's renewed interest in RISC-like architectures when industry already had a good exploration of that area.
Ah, PowerPC. For a RISC processor it surely had a lot of instructions, most of them quite peculiar. But hey, it had fixed-length instruction encoding and couldn't address memory in instructions other than "explicit memory load/store", so it was RISC, right?
Re: What is RISC-V and why it matters to Canonical
#30I’m looking forward to using a RISC-V computer in 20 years
unironically, this. i've been hearing about arm computer for almost twenty years and only just recently general-purpose decently-priced arm laptops have been released (qualcomm laptops, the macbook neo). and arm desktop are still not a thing, in practice.
> arm desktop are still not a thing
The desktop market is not the only product space anymore.
Apple has had brilliant success with its ARM processors, proving that ARM is more than capable. Before Apple's switch, Chromebooks had been using ARM since 2011.
Android is the dominant operating system in mobile and most Android devices use the ARM platform. Many of these devices have desktop capability -- they are a viable convergence platform.