I’m planning to switch to RISC-V by 2030, and since this is new to me (I’m an old AMD64 (and i386) veteran), I wanted to ask what your thoughts and predictions are regarding performance, stability, and usability as a creator of all kinds of content, whether it’s music, movies, 3D, or watching cat videos on YouTube. I’m also planning to buy a new, fresh computer, maybe a laptop from around 2027/2028. Is that a good idea, or am I biting off more than I can chew? To sum up, I’m asking for your opinions, advice, warnings, and thoughts. Feel free to write not only answers to my questions but anything you consider important in the context of the RISC-V and Linux marriage in the near future


Gemini’s Bullshit Nostradamus Answer
The transition from the veteran AMD64/i386 architecture to RISC-V is perhaps the most significant shift in personal computing since the move to 64-bit. As we look toward the 2027–2030 window, the ecosystem is evolving from a “hobbyist curiosity” into a “production contender.”
Below is a breakdown of what to expect regarding performance, stability, and usability for content creators.
1. Performance: The RVA23 Milestone
By 2027, the “performance gap” will begin to close significantly.
2. Stability: The Linux Marriage
The union between Linux and RISC-V is solid, but the “household” is still being organized.
3. The Creator Workflow (Music, 3D, Video)
This is the “high-risk” area for early adopters in the 2027/2028 window.
4. Advice & Warnings for the Veteran
If you are planning to buy a “fresh” RISC-V laptop in 2027 or 2028, keep these points in mind:
⚠️ The Emulation Tax
As an x86 veteran, you are used to a massive library of legacy software. On RISC-V, you will rely on binary translation layers (like Box64/Box86) to run x86 apps. While efficient, this isn’t “native” and can introduce bugs in complex creative software.
⚠️ Hardware Selection
Don’t just look at clock speeds. Ensure the SoC includes:
💡 The Verdict
Final Thought: The RISC-V and Linux marriage is the future of open computing. It offers a level of transparency and customization x86 can’t match, but the “veteran” move is to ensure your critical software stack is ready before you burn the x86 bridges.