341–350 of 360 posts
Earlier quoted context omitted.
How about "Pockmark!... Freshwater swabs!... Bully!.." or "Amoeba! Bashi-bazouks! Chowderheads! Certified Diplodocuses! Nyctalop! Ectoplasm!" ?
I was so disappointed when I tried reading tintin in other languages and found the dear captain was straight up using slurs in those. I wonder whether the english language ones have been edited over the years to remove that sort of thing
Findes der en Haddock/Egon Olsen tiradegenerator derude?
Since I can write a simple compiler to target x64 machine code, it should be possible to write one to target my GPU.
Though, I'm certain that vendor lock is probably more profitable for them.
Since NVIDIA owns huggingface now and huggingface has the excellent Candle [1] crate for inference on Rust, this seems like a good step towards nice native Rust kernels. [1] https://github.com/huggingface/candle
noob here - what's the benefit of this? Will using Rust lead to more optimal LLMs or code or both?
Earlier quoted context omitted.
Once again... There's literally no point to a low level shader language for heterogenous back ends.
Why? The point of a shader language is to define a function that outputs some graphics. Why should that not be portable between GPUs/CPUs of different vendors?
Does this mean I can write shaders in Rust for use with WGPU or Vulkan?
Do it in Go and I’m interested
GPU kernels want explicit memory control and as little go-runtime like overhead as possible
Earlier quoted context omitted.
There's no such censorship on TikTok, it's entirely groupthink based on people saying "when I use that word my video is seen less so therefore it's being censored". Youtube is a lot more guilty of it though, as well as demonetizing.
How is that not a form of censorship? It is direct suppression of certain forms of speech. YouTube has its problems but I don't think it's had quite as strong of an effect on language.
I think it would be much nicer, although unrealistic at the moment given the number of combinations of GPU vendors and variety of hardware, to directly target the underneath GPU ISA machine code. Since I can write a simple compiler to target x64 machine code, it should be possible to write one to target my GPU. Though, I'm certain that vendor lock is probably more profitable for them.
Earlier quoted context omitted.
> 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.
I thought that cp*p is some kind of ugly cuda pointer declaration :D And being non-standard C++ syntax it wouldn’t compile.