this post was submitted on 02 Jan 2025
37 points (97.4% liked)

Hardware

896 readers
533 users here now

All things related to technology hardware, with a focus on computing hardware.

Rules (Click to Expand):

  1. Follow the Lemmy.world Rules - https://mastodon.world/about

  2. Be kind. No bullying, harassment, racism, sexism etc. against other users.

  3. No Spam, illegal content, or NSFW content.

  4. Please stay on topic, adjacent topics (e.g. software) are fine if they are strongly relevant to technology hardware. Another example would be business news for hardware-focused companies.

  5. Please try and post original sources when possible (as opposed to summaries).

  6. If posting an archived version of the article, please include a URL link to the original article in the body of the post.

Some other hardware communities across Lemmy:

Icon by "icon lauk" under CC BY 3.0

founded 2 years ago
MODERATORS
Alphane_Moon
[email protected]
37
RISC-V is making moves, but how will it hit the mainstream? (www.theregister.com)
submitted 2 weeks ago by GreenEngineering3475 to c/hardware
12 comments fedilink hide all child comments
 

Can it topple x86 and Arm, or is the gap too wide to close?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 2 weeks ago* (last edited 2 weeks ago)

That's perhaps one of the biggest headaches for RISC-V and the architecture as a whole: software compatibility. While both Arm and the x86 ecosystems are extensively supported, the same can't be said for RISC-V.

I think the future will be that software comes to the end-user device nearly-compiled (think WebAssembly modules) and then is transformed into the final machine code on-device. This way ensures maximum hardware compatibility while retaining portability.

In that case, it doesn't matter so much what hardware you're sporting, as long as it supports the basic instructions.