Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 279 words in the discussion.
Trending Topics
#zluda#more#vulkan#cuda#means#support#iirc#amd#amusement#development
Discussion Sentiment
Analyzed from 279 words in the discussion.
Trending Topics
Discussion (6 Comments)Read Original on HackerNews
> Some of the newly added features may come as a surprise to those of you who keep a close track of ZLUDA development. Most of them were previously explicitly outside ZLUDA's roadmap. There has been a change of plans. ZLUDA development is no longer commercially funded, so it's back to being my weekend project. This means that the priority is no longer what makes commercial sense, but what I find the most entertaining. That's why the sudden addition of textures, PhysX and better Windows support.
Outside of the time commitment that full-time support would offer, I generally think focusing on amusement is a good life strategy.
1: Much initial research and early OSS was CUDA focused due to libaries and momentum, but with more Mac users,etc kernels/frameworks are more portable so with stuff like Unsloth so the CUDA moat is falling there (If it's Vulkan or more propietary backends doesn't matter, Vulkan or OpenCL are probably fairly equal in usefulness since Vulkan support would probably require custom extensions for full performance).
2: As alluded above, ZLuda seems to have focused a bit on ROCm API's for AMD (I think I've seen mentions of other library supports but it's been up and down iirc since he was employed by AMD). The main benefit compared to Vulkan iirc is that ROCm allows for some CUDA-like feature that makes kernel emulation so much less troublesome (or even feasible at all?).
Złuda means "mirage"/"illusion"/"figment of imagination"