RISC-V is getting a serious public dressing-down
A post titled 'RISC-V: They Should Have Known Better' by dmitrygr got significant traction. The core critique is architectural: no central authority mandates vendor compliance, which means extension detection is broken in practice, vendors overlap things, and the open ISA promise is not translating cleanly to interoperable hardware. Commenters who had early enthusiasm for RISC-V described learning to 'wait before getting excited about the new shiny thing' from past experience.
The pattern: RISC-V has enormous promise as an open alternative to ARM and x86 in embedded and server contexts, but the governance model is creating real fragmentation. This is a recurring problem with open standards: the lack of a strong central authority means the spec can be clean while the ecosystem is a mess.
One commenter wryly noted that dmitrygr is unlikely to be invited to the next RISC-V design committee meeting. The criticism is pointed enough to sting.
So what?
Founders building on or around RISC-V silicon (especially in edge AI, embedded systems, or custom hardware) should factor ecosystem fragmentation into their timeline and cost assumptions. The chip may be cheap, the software integration may not be. Extension compatibility needs to be validated vendor-by-vendor, not assumed.