this post was submitted on 19 Jun 2024
715 points (98.6% liked)

Technology

59219 readers
3980 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 6 points 4 months ago (1 children)

Sure, and there are more people with that access than just AMD, ARM, NVIDIA, and Intel.

If game devs supported RISC-V, Valve could've made the Steam Deck without having to get AMD's help, which means they would've had more options to keep prices down while meeting their performance goals. Likewise for server vendors, phone manufacturers, etc, who currently need to buy from ARM (and fab themselves) or AMD/Intel.

And that's why I mentioned 3D printing. Making custom 3D models of LEGO pieces is out of reach for many (most?) and even owning a 3D printer is out of reach for many. I have one, but I've only built a handful of things because it's time consuming.

As it gets more software support, we should see a lot more variety in RISC-V chips. We're not there yet, but we should be excited because it's starting to get traction, and the future looks bright.

[–] cmhe@lemmy.world 1 points 4 months ago* (last edited 4 months ago) (1 children)

It also means that anyone can make their own instruction set extensions or just some custom modifications, which would make software much more difficult to port. You would have to patch your compiler for every individual chip, if you even figure out what those instructions are, and what they do. Backwards, forwards or sideway (to other cpus from other vendors) compatibility takes effort, and not everyone will try to have that, and instead add their own individual secret sauce to their instruction set.

IMO, I am excited about RISC-V, but if the license doesn't force adopters to open their designs under an open source license as well, I do expect even more portability issues as we already have with ARM socs.

[–] sugar_in_your_tea@sh.itjust.works 2 points 4 months ago* (last edited 4 months ago)

Compilers basically already do that, and distributed executables usually assume minimal instruction support. Compilers can detect what's supported, so it's largely a solved problem, at least if you compile things yourself.