News for hackers. Stuff that matters.
Re:Vulkan1.3 on the M1 in 1 Month by robertoandred on Wednesday June 05, 2024 @06:44PM (#40591498)
Apple created OpenCL. It was nvidia who made everyone else avoid it.
Re:Vulkan1.3 on the M1 in 1 Month by talldayo on Wednesday June 05, 2024 @07:35PM (#40591867)
What does that prove, though? Apple gave up. Ironically, now Nvidia is one of the only remaining companies that supports OpenCL anymore.

Apple is experiencing firsthand what the lack of a CUDA analog does to a company. Whether or not they care is up to them, but clearly the laser-focus on high-performance GPU compute is not doing Apple Silicon any favors in the server space or in the desktop.

Re:Vulkan1.3 on the M1 in 1 Month by robertoandred on Wednesday June 05, 2024 @07:57PM (#40591975)
It proves that the idea that Apple avoided OpenCL is ludicrous.
Re:Vulkan1.3 on the M1 in 1 Month by talldayo on Wednesday June 05, 2024 @08:29PM (#40592169)
Where does Apple support OpenCL today then?
Re:Vulkan1.3 on the M1 in 1 Month by robertoandred on Thursday June 06, 2024 @12:58PM (#40599710)
It still works on Apple Silicon
Re:Vulkan1.3 on the M1 in 1 Month by talldayo on Thursday June 06, 2024 @03:39PM (#40601499)
Works != supported
Re:Vulkan1.3 on the M1 in 1 Month by troupo on Friday June 07, 2024 @07:52AM (#40607730)
You mean "literally fully ported to a completely new architecture" != supported?
Re:Vulkan1.3 on the M1 in 1 Month by pjmlp on Thursday June 06, 2024 @03:41AM (#40594642)
Sure, sure, like Google, Intel and AMD aren't to blame for having made a mess out of OpenCL on their products.
Re:Vulkan1.3 on the M1 in 1 Month by talldayo on Thursday June 06, 2024 @12:09PM (#40599116)
Go ahead, blame literally every single person except the lead maintainer and developer of the project.
Re:Vulkan1.3 on the M1 in 1 Month by pjmlp on Thursday June 06, 2024 @02:13PM (#40600587)
The reality is that Google, AMD and Intel have more than enough time since 2009, to provide a developer experience, and drivers, that would make people actually use OpenCL instead of CUDA.

Instead, Google created the proprietary Renderscript for Android, while AMD and Intel kept delivering broken drivers, partial implementations of OpenCL, never delivered a proper OpenCL 2.x implemenation with mature C++ support, IDE and GPGPU graphical debuggers.

Re:Vulkan1.3 on the M1 in 1 Month by talldayo on Thursday June 06, 2024 @03:43PM (#40601523)
It wasn't Google, AMD and Intel's job to improve the developer experience. You can chew them out for bad drivers, but they did improve and now AMD and Intel's OpenCL implementations are the reference-quality ones.

Again, you can blame everyone else for doing their own thing but the project only has one father that could estrange it. Apple's blindness killing OpenCL makes everything in Microsoft and Google's graveyard look reasonable by comparison. If Apple wants a repeat of the Metal for gaming situation in AI, they are more than welcome to self-sabotage themselves until they run out of energy.

Re:Vulkan1.3 on the M1 in 1 Month by pjmlp on Friday June 07, 2024 @05:05AM (#40606750)
Sure little dreamer, blame NVidia and Apple for Intel, Google and AMD incompetency.