> 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 In

> 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.