I'm really excited to play with it as a hobby developer. Simply because I like doing low-level programming/optimizing for the fun of it.
And I'm currently working on my Msc. in computational science (and possibly a PhD. afterwards) so I'm also going to see how easy it is to shoehorn generic-HPC into this API. OpenCL is nice (well... maybe not nice but workable) but historically the graphics APIs have had better performance for less work. But I guess you could count me as a low level API programmer come to think of it.
I believe that newer versions of OpenCL will benefit from Vulkan due to the mutual dependence on SpirV. My biggest hope is that this will finally reduce our reliance on out of date and buggy drivers to get OpenCL support on multiple platforms.
SPIR-V will be a huge boon for everyone and everything I hope, especially given the LLVM support (Haskell or Rust compilers anyone?). But it only augments the compiler step (AFAIK). I've had plenty of bugs in the host-side code before.
And of course, a newer version does not neccesarilly mean that the out-of-date implementations will suddenly become "in-date": if anything they're even more out of date now ;)
And I'm currently working on my Msc. in computational science (and possibly a PhD. afterwards) so I'm also going to see how easy it is to shoehorn generic-HPC into this API. OpenCL is nice (well... maybe not nice but workable) but historically the graphics APIs have had better performance for less work. But I guess you could count me as a low level API programmer come to think of it.