BlazingSQL is Now Open Source

https://www.codeplay.com/products/computesuite/computecpp Enable SYCL for all openCL devices so Intel, AMD, Nvidia, FPGAs, a lot of things and smartphones which is order of magnitude more devices than CUDA.Products targeting only nvidia devices are mostly niche markets which is pathetic. As for debuggers codexl has been extended to support it.

Except SYCL there's Open{MP/ACC} gpu offloading which become viable and portable. There's also HIP/rocm which transpile to openCL AND CUDA (best of both worlds?) And can transpile CUDA to HIP almost totally automatically. That's how AMD ported tensorflow to openCL.

Smartphones? Which ones?

iOS with its ageing OpenCL drivers, or the new Metal Shader drivers?

Or Android, which Google rather uses their own languages, Renderscript and Halide?

Yes some OEMs do happen to ship non standard Android drivers that also support OpenCL, which require vendor specific SDK to be actually usable, thus not an option versus Renderscript or Halide.

Do you happen to actually know CodePlay? They got their name creating compilers with vectorization optimization for the PS3 and other game consoles.

Their ComputeCpp is a pivot into the GPGPU world and their aren't doing the community edition just from the kindness of their hearts, rather as path into their products.

"If you want to do things with this release, be prepared to be a pioneer. This release is pre-conformance, which means that we do not implement 100% of the SYCL specification. We currently only support Linux and two OpenCL implementations, by Intel and AMD, but wider support is coming. You may find that some unsupported implementations of OpenCL work with ComputeCpp. That's great, but we don't officially support anything else (yet). Most of the open-source libraries being ported to SYCL are not completed yet. This means that you should only check out some of these projects if you want to do some development yourself. We are building a big vision here: large, complex software highly accelerated on a wide range of processors, entirely by open standards. So, please be patient, or work with us."

Feels like it still needs to mature a little bit.

Even Intel, despite their SYSCL contributions to clang (experimental release last 31st July), has been developing in parallel their own extensions, Data Parallel C++, that no one knows in what form will they contribute back to Khronos, if at all.

Meanwhile CUDA has been developed to be language agnostic from the get go, with out of the box support for C, C++, Fortran. Now with Julia, Haskell, Java, .NET support as well.

While Khronos kept banging the C is good enough message until it was too late for vendors to actually care about SPIR-V.

Not the same. Two companies make x86 processors, and in the very specific case of this article/comment thread, more than one company supports OpenCL. Nvidia/cuda is a one-pony show, no matter how you look at it.