A developer publishing under the handle Speedstu put a project on GitHub this week called CUDA-for-AMD-Windows. It takes binaries compiled against CUDA, NVIDIA's programming toolkit and the thing most AI code is actually written for, and runs them on Radeon cards under Windows. No Linux partition, no ROCm rewrite, no porting project. The repo is honest about its state: experimental, unproven past small workloads, the sort of thing that breaks on the first serious model thrown at it. As a product it is unremarkable. As an address, it sits on the most contested piece of ground in the industry.
CUDA compatibility is the reason a builder in a shortage year pays NVIDIA's price instead of AMD's. The reason is inheritance rather than raw silicon: the code you already have, and the code everyone you might hire already knows, assumes CUDA. Jensen Huang has been direct about where that puts the business. "You sell a chip one time, but when you build software, you maintain it forever," he told Tom's Hardware at CES. That sentence describes a moat and an obligation in the same breath, and the obligation is the part a translation project goes after.
Three other things surfaced within a few days of it, from corners with nothing to do with each other. On r/LocalLLaMA, someone published a configuration that fits Qwen3.8 27B at INT4 with a 144,000 token FP8 key-value cache onto a single 24GB 3090, using vLLM's ahead-of-time compilation path, reportedly faster than the llama.cpp setup most owners of that card settle for. A community project called The Hugging Bay proposed distributing model weights over BitTorrent rather than through a hosted hub. And Simon Willison handed ChatGPT an address and got back looping five and ten kilometer running routes computed straight from OpenStreetMap data, with no routing service anywhere in the loop.
Four dependencies, four substitutions, one week: the GPU vendor, the VRAM budget, the model hub, the vertical API. In each case the answer to a cost or a scarcity was a compatibility path around it rather than a purchase through it. Call the pattern compatibility as price control. The substitute is rarely the better product and its usual fate is to stay the second choice. What it does is put a visible number on the incumbent's incompatibility, and a number that is visible is a number that can be argued about at renewal.
Every one of those four substitutions cost fewer engineering hours than the purchase it avoided, which is the entire reason any of them happened.
This shape has run several times inside the current industry's memory and it runs the same way each time. Samba, Andrew Tridgell's reimplementation of Microsoft's file-sharing protocol from 1992, never displaced Windows in the enterprise. It turned per-seat licensing into a conversation instead of an invoice. WINE has spent three decades not quite running Windows applications well enough to matter, and has kept a floor under the cost of leaving the whole time. Napster and the torrent networks that followed did not take the record business away from the labels; they set the ceiling that paid downloads and then streaming had to clear. Losing on the merits and winning on the price sheet is the normal outcome, not the disappointing one.
One exception marks the boundary. AMD's 64-bit extension to x86 in 2003 did take the standard, and it took it because Intel's alternative asked the entire industry to recompile for Itanium. When the incumbent's own road demands a rewrite and the challenger's road does not, compatibility stops being a discount and becomes the default. That is the test to run against any shim: is the incumbent asking its customers to do work they were not already doing? NVIDIA is not. Continuity is the product. Which is why a translation project aimed at CUDA presses on price and leaves share alone.
The pattern has clean failure conditions, which is what makes it worth naming instead of admiring. It needs the constraint to be contractual or architectural, something a shim can route around. VRAM is neither. The 3090 recipe squeezes a model into a card that already exists, and no amount of compiler work conjures memory the board does not have. The pattern also needs the substitute to be credible rather than good, and credible is a low bar that plenty of projects still fail. If CUDA-for-AMD-Windows never clears toy workloads, no purchasing conversation ever cites it and the ceiling never gets set.
The exposure runs wider than hardware. Willison's running-route demo is a small thing pointing at a large category: services whose product is a convenient wrapper around a public dataset. Routing over OpenStreetMap, geocoding, address validation, timezone lookup, a long tail of vendors selling access to data that is already open. A model with tool access and a tolerance for reasoning over raw files is a poor version of each of those services and an adequate version of several. The ones that hold their pricing are selling what the dataset does not contain: coverage guarantees, latency commitments, someone to sue.
The commercial version of this is already legible in spend data, with the caveat that the data comes from a source with a house interest. Ramp's Economics Lab, writing from transactions on Ramp's corporate card and therefore describing a tech-forward slice rather than American business, argues in its September index update that adoption of cheaper models keeps rising while uptake of Fable 5 stays mediocre, and that the combination is a problem for companies whose revenue assumes customers keep trading up. Same mechanic, one level above the hardware. Cheap-and-compatible never has to be better to change what the premium tier can charge.
Where this goes next gets decided by parties that have not moved yet. AMD has spent years funding ROCm, the native path that asks developers to port their code, while the translation work that would make porting unnecessary sits on a stranger's GitHub account with no vendor behind it. Hugging Face has not had to say anything about torrent mirrors, because no widely used repository has mirrored there. Those two silences were the most interesting thing in the week.
The tension nobody has resolved is whether a vendor can take a compatibility win without conceding the argument it has been making for a decade. AMD's developer pitch says the native toolchain is the future and the port is worth doing. The shim implies the port was optional all along. Both can hold for a while, and then somebody at AMD has to decide whether to fund the project that makes their own platform story unnecessary. There is no comfortable version of that meeting.