Live data from Hacker News

Nvidia announces native GPU programming in Rust

developer.nvidia.com

61–70 of 334 posts

Re: Nvidia announces native GPU programming in Rust

#62

I strongly dislike CUDA. Once you have allowed that proprietary cr*p into your C++ codebase, it is very hard to get rid, and you end up with code that is either tied to a single vendor or an #ifdef hell, probably both. The best way to program GPUs is face up to the reality that they are not the same machine as the CPU, write your kernels in separate files, and launch them manually, like in Metal, OpenCL, and D3D12, e…

You could also use Mojo, one language for all targets.

Or julia if you want a much more mature ecosystem.

Re: Nvidia announces native GPU programming in Rust

#63
post #58

Earlier quoted context omitted.

People never really read documentation before. Agents do read it now, and they seem to understand LLM-written text just fine.

> People never really read documentation before. The heck you talking about? How do you think we wrote software for the last 50 years?

when you start to internalize that these kinds of statements are an indication of how the average developer of the last 10-15 years operated the adoption rate of AI makes a lot more sense

Re: Nvidia announces native GPU programming in Rust

#65
post #58

Earlier quoted context omitted.

People never really read documentation before. Agents do read it now, and they seem to understand LLM-written text just fine.

> People never really read documentation before. The heck you talking about? How do you think we wrote software for the last 50 years?

Yeah lol it’s basically the only reliable way to know how things work. Pre-AI, I read documentation for libraries that I used almost every day.

And now with AI I’m using it to fact check Claude. And still reading it for myself to understand why other peoples code is written a certain way. It’s basically the most important thing to reference when coding.

Sure today Claude can just read the library code and tell you what a function does or how to do something. But it still won’t tell you why something is a certain way or won’t figure out specifically-designed usage patterns as reliably as the author telling you “this is an example of doing x”

Re: Nvidia announces native GPU programming in Rust

#66
post #6

> The launch is checked rather than trusted. Damn even Nvidia is putting out fully Claude-written articles.

> even Nvidia Why "even Nvidia"? They are fully behind using AI for basically everything. What's next? "Damn, even McDonald's is putting out unhealthy food"

[dead]

Re: Nvidia announces native GPU programming in Rust

#67
post #58

Earlier quoted context omitted.

> People never really read documentation before. The heck you talking about? How do you think we wrote software for the last 50 years?

when you start to internalize that these kinds of statements are an indication of how the average developer of the last 10-15 years operated the adoption rate of AI makes a lot more sense

This is extremely depressing, I think I'm coming around to the realization that you may be right and I've been naive my entire career.

Re: Nvidia announces native GPU programming in Rust

#69

Earlier quoted context omitted.

You could also use Mojo, one language for all targets.

Or julia if you want a much more mature ecosystem.

I highly recommend Julia for (scientific) GPU programming but it would be nice if there was a larger community and/or funding behind the GPU side of things. It has very few core devs for what it is.

Re: Nvidia announces native GPU programming in Rust

#70
post #45

I strongly dislike CUDA. Once you have allowed that proprietary cr*p into your C++ codebase, it is very hard to get rid, and you end up with code that is either tied to a single vendor or an #ifdef hell, probably both. The best way to program GPUs is face up to the reality that they are not the same machine as the CPU, write your kernels in separate files, and launch them manually, like in Metal, OpenCL, and D3D12, e…

> I strongly dislike CUDA. Once you have allowed that proprietary cr*p Genuine question...why not just type "crap"? It's not even that much of a curse, but I've never really understood the point of self-censorship. If you don't want to curse then you could just use a non-curse word.

* is used to give emphasis and show that they are using the word as curse word rather just calling it bad
Post reply on HN