AMD betrays Linux users with Vivado licensing reversal
AMD quietly changed the licensing terms for Vivado, its FPGA development toolchain, in a way that breaks the workflow for Linux users who had specifically chosen AMD hardware because of its historically better Linux and open toolchain support. HN commenters are furious, with one noting they have 'specifically chosen AMD many times' for exactly this reason, and another invoking the specter of another CUDA-like vendor lock-in situation. The phrase 'AMD never misses a chance to miss a chance' appeared early in the thread and landed with clear resonance.
The pattern is familiar: a hardware company builds market share by being the open, Linux-friendly alternative, then once entrenched, begins tightening licensing and toolchain control. Nvidia did this with CUDA, and now AMD appears to be testing the same playbook with Vivado. The timing is particularly bad given that AMD has been gaining ground as a credible alternative in the AI accelerator market, where the open-source toolchain story was a meaningful differentiator.
The practical damage here is not just to existing users. It is a credibility hit that will make future buyers skeptical of AMD's commitments. Trust in toolchain stability is slow to build and fast to destroy.
So what?
If you are building hardware-adjacent products or making infrastructure decisions that involve FPGA tooling, factor toolchain lock-in risk into your vendor selection explicitly, not just current feature sets. AMD's move is a reminder that 'open by default' is a positioning choice, not a structural commitment, and it can change when the business calculus shifts.