Hacker News Reader

Comment by RcouF1uZ4gsC | Hacker News Reader

Seems like yet another CUDA alternative. Thing is, even if you were wanting to move away from CUDA, the churn of the alternative models would be scary. Do you want to develop for CUDA which has been stable and developed for quite some time, or do you want to try a new standard that you don’t known if it will be obsolete in a couple of years?

View on HN

> do you want to try a new standard that you don’t known if it will be obsolete in a couple of years

Some incarnation of oneAPI is bound to exist as long as Intel has a foothold in the HPC market. For example, MKL and MKL-DNN have been rebranded with a oneAPI prefix. So no, the long term stability argument doesn't hold water.

I'd also note that they appear to have added support for cuBLAS and cuDNN as backends in their respective oneAPI libraries. It would be hilarious if that lead to more people running oneAPI on non-Intel hardware than first party stuff.

otoh Intel has over the years developed a few parallel libraries / extensions that have then been deprecated, for instance Cilk Plus...

and ISPC, and... and...

Has ispc been deprecated? Last GitHub commit was three days ago.

it's a pet project.

its open source, so it has been kept "alive" on and off for years already

> Seems like yet another CUDA alternative.

How many real alternatives are there though aside from OpenCL? Not to mention if you're interested in targeting something that isn't an Nvidia GPU.

Reply on news.ycombinator.com