> Luckily, AMD has an open-source solution for developers just for that. HIP (Heterogeneous-computing Interface for Portability) is a C++ runtime API and kernel language that allows developers to create portable applications for AMD and NVIDIA® GPUs from a single source code. This allows the Blender Cycles developers to write one set of rendering kernels and run them across multiple devices. The other advantage is that the tools with HIP allow easy migration from existing CUDA® code to something more generic.

Yeah, I've read that.

But this is not an open standard, it's just a hack, and it is under the control of a vendor.

Worse, it is nothing but a thin layer above an even more proprietary layer.

> But this is not an open standard, it's just a hack, and it is under the control of a vendor.

It's under a permissive license (MIT). What makes you say it is "just a hack"? What makes it a hack?

> Worse, it is nothing but a thin layer above an even more proprietary layer.

The same is true for OpenCL (layer above a proprietary layer) and pretty much any API interfacing with proprietary hardware/drivers.

Also it's not even proprietary software in the first place, even if you're trying to make it sound that way.

In my experience, on Windows, DirectCompute shaders work OK on AMD too. For optimal performance they require optimizations for specific GPUs, though.

Have you heard of SYCL[1]? :)

[1]: https://www.khronos.org/sycl/

Vulkan! Compute! Shaders!

I hate compute-specific APIs so much. Use Vulkan!

Could you provide some pointers to where someone who's moderately familar with OpenCL should start looking to learn to do compute with Vulkan? I find the documentation quite fractured.

Don't try to use it directly, you need a higher level library.

https://github.com/KomputeProject/kompute seems like what's taking off. There are also smaller ones like https://github.com/Glavnokoman/vuh etc.

Does this mean that OpenCL is being phased out without any serious Vulkan-based replacements being actively worked on?

> I find the documentation quite fractured.

This has been my experience as well: the few Vulkan Hello, World I've seen all have a mile and half boilerplate code before you can open a window and draw an effing pixel in it.

Also, from an admittedly quick glance at Vulkan ... I haven't really seen specs for a full-fledged CUDA / OpenCL modern replacement.

Did I miss something?

It's even worse if you don't wanna draw a pixel, but rather want the compute world's equivalent of hello world (i.e. inner product)!