Tempted to switch to https://github.com/shader-slang/slang for compute shader language. It has some very nice features but I'm a bit worried that I might hit some limits with no workaround (for instance, it doesn't look like they support pointers into groupshared memory)
Anyone has experience with it? Thoughts?
@xoofx I don't have experience, but positive signs are that it is in active development (https://github.com/shader-slang/slang/releases), and is now the "official future language" of Khronos et al (compared to GLSL which is effectively frozen)
[upd: it is not “official language”, just one of Khronos projects]
Sweet Jesus no it is not.
Slang is NOT the official future language of Khronos.
I told them again and again people would assume that.
None of this is your fault, dear friends and readers.
Hey @thekhronosgroup take note.
Slang is under active development, yes. NVIDIA has been actively working on it for years and gotten great mileage out of that. Great!
The compiler has been open source for a while.
What has changed is that NVIDIA wanted to open up governance of the language. Instead of making a new corporate body (like a Rust Foundation setup), they took it to Khronos. It's about a having a corporate body to absorb IP and other legal risks when corporations collaborate.
In no way is this to be interpreted as Slang being a blessed or preferred language for Vulkan or any other Khronos related property.
Excuse me if I'm shouting but I suffered months of meetings making this point and shaping the charter of the Slang Working Group at Khronos.
Neither Google or I participate in the working group. I wish them well but it's not where I can spend energy.
Alexandre Mutel
Aras Pranckevičius
David Neto
beanz
Matthäus "Anteru" Chajdas