Originally posted by log0
View Post
Announcement
Collapse
No announcement yet.
Vulkan Presentations On Multi-Threading, HPP, Pipeline Cache & More
Collapse
X
-
Originally posted by timofonic View PostWhat about Rust + Vulkan? The concept seems perfect, specially because SPIR-V that acts as OpenCL too (right?).
Comment
-
-
Originally posted by timofonic View Post
Why didn't they unify it?
Comment
-
Originally posted by Ancurio View Post
Because those are two different APIs with different shader/kernel code specifications. There are no descriptor sets in OpenCL for example. I think the trend is for Vulkan to cover more and more compute ground so it can be used in similar places as OpenCL is today, eventually taking its place as an API fit for general purpose compute.
What about sound processing?
Maybe Vulkan should unify all Khronos functions inside it in a coherent and homogeneus way. This way, Vulkan would be enough and SDL2 or others just be tinier higher level wrappers in the Vulkan-friendly ecosystems
Comment
-
Originally posted by timofonic View Post
Yes, please. That's what really should have been since day one, in my opinion. It's the only way to compete both DirectX and CUDA.
What about sound processing?
Maybe Vulkan should unify all Khronos functions inside it in a coherent and homogeneus way. This way, Vulkan would be enough and SDL2 or others just be tinier higher level wrappers in the Vulkan-friendly ecosystems
Comment
Comment