NVIDIA CUDA
The most recommended of 12 GPU compute frameworks
Developers recommend CUDA for its mature ecosystem, easy defaults and performance on NVIDIA GPUs. Main caveat: it only runs on NVIDIA hardware and is not portable.
Developers recommend CUDA for its mature ecosystem, easy defaults and performance on NVIDIA GPUs. Main caveat: it only runs on NVIDIA hardware and is not portable.
164 people gave an opinion
- recommend it
- 91
- criticize it
- 73
- approval share
- 55%
Recommended in 12 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Owned for 18 years
Median of the 3 owners who said how long they have had it.
Each square is one year.
Why it doesn’t carry the badge
- 91 people recommend itNeeds 10 or more, met.
- 1.2 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 12 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Mature ecosystem and large library
“The CUDA runtime coming with a gazillion reasonably decent kernels (DNN, BLAS, CUTLASS) and a concurrency system (NCCL) is a big deal”
Comment from 12 Aug 2026 in “Nvidia's Risky Business” “training requires the mature ecosystem and numerical stability of cuda to handle mixed-precision operations”
Comment from 27 Nov 2025 in “TPUs vs. GPUs and why Google is positioned to win AI race in the long term” “it's still the easiest to use, with most available resources when you inevitable need to dig through stuff”
Comment from 10 Nov 2025 in “Asus Ascent GX10” - Comment from 7 Dec 2025 in “The AI wildfire is coming. it's going to be painful and healthy”
- Comment from 16 May 2026 in “The old world of tech is dying and the new cannot be born”
- Comment from 12 Apr 2026 in “Nvidia's moat is not what it used to be”
- Comment from 9 Dec 2025 in “AMD GPU Debugger”
Easy defaults with optional complexity
“Cuda has shown that, when done right, defaults and a convenience layer can make for a well received API without sacrificing performance.”
Comment from 17 Sep 2026 in “Nvidia announces native GPU programming in Rust” “With a design like Cuda where there is always a default easy path, and a complex but optional path.”
Comment from 14 Jul 2026 in “Alternative(s) to run CUDA on non-Nvidia hardware” “Which is way easier because Cuda always provides the simple API and makes complexity opt-in.”
Comment from 11 Feb 2026 in “Simplifying Vulkan One Subsystem at a Time” - Comment from 10 Feb 2026 in “Simplifying Vulkan One Subsystem at a Time”
- Comment from 22 Nov 2025 in “How I learned Vulkan and wrote a small game engine with it (2024)”
- Comment from 19 Feb 2026 on Hacker News
Strong performance on NVIDIA hardware
“Ease of programming and a giant leap in performance is one of the key reasons for the CUDA platform's widespread adoption”
Comment from 14 Jul 2026 in “Alternative(s) to run CUDA on non-Nvidia hardware” “CUDA is far-and-away the better hardware architecture, not to mention better-supported by the community.”
Comment from 20 Feb 2026 in “Ggml.ai joins Hugging Face to ensure the long-term progress of Local AI” “its not super easy to use, but unlocks orders of more magnitudes of power for the use cases it excels at”
Comment from 11 Aug 2026 in “Nvidia's Risky Business” - Comment from 13 Apr 2026 in “Taking on CUDA with ROCm: 'One Step After Another'”
Long backward compatibility across GPUs
“CUDA focused not just on keeping one backward compatible one, but also made it work from cheapest NVS card to high end parts”
Comment from 15 Nov 2025 in “HipKittens: Fast and furious AMD kernels” “the compute capabilities from 2014 are still instrumental for accelerating training and acceleration workloads”
Comment from 13 Apr 2026 in “Apple's accidental moat: How the "AI Loser" may end up winning” “The next 20 years of cuda support weren't luck, as anyone trying to use AMD will know.”
Comment from 31 Aug 2026 in “Apple caught off guard by AI demand for Mac Mini and Mac Studio” - Comment from 11 Aug 2026 in “Mojo 1.0 Is Here”
What people warn about
Each mark is one comment
Locked to NVIDIA hardware
“I'm asking you to imagine how much easier everything would have been if Cuda was cross-platform without any performance or ergonomic penalties.”
Comment from 9 May 2026 in “Mojo 1.0 Beta” “All wannabe replacements fail, because they focus only on the CUDA C++ compiler and nothing else.”
Comment from 14 Sep 2026 in “CUDA for AMD on Windows” “Trying to bake CUDA assumptions into model design, and pushing the software ecosystem to be as Nvidia first as they can.”
Comment from 27 Aug 2026 in “Nvidia agrees to acquire Hugging Face for $13B” - Comment from 28 Nov 2025 in “TPUs vs. GPUs and why Google is positioned to win AI race in the long term”
Build and toolchain friction
“I do mind that all of the SDKs don't dynamically load the various CUDA shared libraries at runtime”
Comment from 17 Sep 2026 in “Nvidia announces native GPU programming in Rust” “it was so niche that you ended up compiling from source literally everything since no wheels were available for it”
Comment from 25 Aug 2026 in “Hot Chips 2026: CUDA Targets RISC-V” “nvidia libs are broken with clang-21 and recent glibc due to stuff like rsqrt() having throw() in the declaration”
Comment from 20 Nov 2025 in “CUDA Ontology” - Comment from 17 Sep 2026 in “Nvidia announces native GPU programming in Rust”
Breaks backward compatibility over time
“Newer hardware may require a CUDA toolkit version that is newer than what the project maintainer intended.”
Comment from 20 Nov 2025 in “CUDA Ontology” “nvidia is not interested in maintaining any semblance of backwards compatibility when it comes to CUDA”
Comment from 11 Aug 2026 in “Mojo 1.0 Is Here” “Just because it's still called CUDA doesn't mean it's portable over a not-that-long of a timeframe.”
Comment from 28 Nov 2025 in “TPUs vs. GPUs and why Google is positioned to win AI race in the long term” Proprietary closed stack
“everything is open source except CUDA itself. So any issue that happens on the CUDA level, you are forced to wait for them to fix it.”
Comment from 16 Sep 2026 in “Nvidia announces native GPU programming in Rust” “the worst privacy, transparency, and FOSS integration due to their insistence on a heavily proprietary stack”
Comment from 13 Apr 2026 in “Taking on CUDA with ROCm: 'One Step After Another'”
Other GPU compute frameworks people recommend
The four most recommended other GPU compute frameworks, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 12 GPU compute frameworks, rankedWhat people said
40 of the 232 comments that mention it, newest first. Each links to the original comment.
“Cuda has shown that, when done right, defaults and a convenience layer can make for a well received API without sacrificing performance.”
“messes with your build system, ties your build system to platforms that have their toolchain binaries available”
“I do mind that all of the SDKs don't dynamically load the various CUDA shared libraries at runtime”
“everything is open source except CUDA itself. So any issue that happens on the CUDA level, you are forced to wait for them to fix it.”
“All wannabe replacements fail, because they focus only on the CUDA C++ compiler and nothing else.”
“The next 20 years of cuda support weren't luck, as anyone trying to use AMD will know.”
“Trying to bake CUDA assumptions into model design, and pushing the software ecosystem to be as Nvidia first as they can.”
“it was so niche that you ended up compiling from source literally everything since no wheels were available for it”
“The CUDA runtime coming with a gazillion reasonably decent kernels (DNN, BLAS, CUTLASS) and a concurrency system (NCCL) is a big deal”
“its not super easy to use, but unlocks orders of more magnitudes of power for the use cases it excels at”
“GPU architectures are supported by the full tool suites for at least 10 years by CUDA”
“nvidia is not interested in maintaining any semblance of backwards compatibility when it comes to CUDA”
“I had actually a ton of success using Strassen turboplicattion kernels with some extra custom CUDA”
“With a design like Cuda where there is always a default easy path, and a complex but optional path.”
“No ridiculous descriptor management and binding in cuda, just passing pointers and handles via launch arguments.”
“Ease of programming and a giant leap in performance is one of the key reasons for the CUDA platform's widespread adoption”
“NVIDIA developed CUDA and (perhaps more importantly) an entire GPU software ecosystem around it.”
“CUDA has support for C, C++, Fortran, Python JIT, and anything else targeting PTX, graphical GPU debugger”
“I'm asking you to imagine how much easier everything would have been if Cuda was cross-platform without any performance or ergonomic penalties.”
“the compute capabilities from 2014 are still instrumental for accelerating training and acceleration workloads”
“got the same stuff done in less than a day that I could not do in a whole week in Vulkan”
“the worst privacy, transparency, and FOSS integration due to their insistence on a heavily proprietary stack”
“CUDA’s moat isn’t just writing kernels, it’s the whole ecosystem + hard earned perf intuition.”
“CUDA feels really cozy, because like Microsoft, NVidia understands the Developers, Developers, Developers mantra.”
“CUDA is far-and-away the better hardware architecture, not to mention better-supported by the community.”
“You don't need advanced C++ knowledge anymore to write and run a CUDA project anymore.”
“Which is way easier because Cuda always provides the simple API and makes complexity opt-in.”
“Cuda allows to easily get stuff done first then check the more complex stuff to optimize”
“Raw CUDA works for the heavy lifting but I suspect it gets messy once you implement things like grammar constraints or beam search.”
“CUDA, by comparison, is having zero expense spared in it's development at every layer of the stack”
“This is exactly yet another reason why researchers prefer CUDA to the alternatives.”
“there is a huge library of CUDA code that will run out of the box on NVIDIA hardware is a big advantage”
“Just because it's still called CUDA doesn't mean it's portable over a not-that-long of a timeframe.”
“training requires the mature ecosystem and numerical stability of cuda to handle mixed-precision operations”
“Cuda shows that allocation of GPU memory and copy from host to device can be one-liners”
“CUDA isn't all that and a bag of chips. It just is the Facebook/Twitter of the data science and from that LLM space.”
“nvidia libs are broken with clang-21 and recent glibc due to stuff like rsqrt() having throw() in the declaration”
“Newer hardware may require a CUDA toolkit version that is newer than what the project maintainer intended.”
“CUDA focused not just on keeping one backward compatible one, but also made it work from cheapest NVS card to high end parts”
“it's still the easiest to use, with most available resources when you inevitable need to dig through stuff”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.