I don't think that it will happen in the next 5 years, but who knows?
Good podcast on him: https://newsletter.pragmaticengineer.com/p/from-swift-to-moj...
Mojo looked promising initially. The more details we got though, the more it became apparent that they weren't interested in actually competing with Nvidia. Mojo doesn't replace the majority of what CUDA does, it doesn't have any translation or interoperability with CUDA programs. It uses a proprietary compiler with a single implementation. They're not working in conjunction with any serious standardization orgs, they're reliant on C/C++ FFI for huge amounts of code and as far as I'm aware there's no SemVer of compute capability like CUDA offers. The more popular Mojo gets, the more entrenched Nvidia (and likely CUDA) will become. We need something more like OpenGL with mutual commitment from OEMs.
Lattner is an awesome dude, but Mojo is such a trend-chasing clusterfuck that I don't know what anyone sees in it. I'm worried that Apple's "fuck the dev experience" attitude rubbed off on Chris in the long run, and made him callous towards appeals to openness and industry-wide consortiums.
I can't claim to know more about GPU compilers than Lattner - but in this specific instance, I think Mojo fucked itself and is at the mercy of hardware vendors that don't care about it. CUDA, by comparison, is having zero expense spared in it's development at every layer of the stack. There is no comparison with Mojo, the project is doomed if they intend any real comparison with CUDA.
This was even proven in practice with Intel’s Arc. While they had (and to some extent still have) their share of driver problems, at a low enough price that isn’t a barrier.
Its that nvidia relentlessly works with game developers to make sure their graphics tricks work with nvidia drivers. Its so obvious you miss it. Look in the nvidia driver updates they always list games that have fixes, performance ect. AMD never (used?) to do this they just gave you the drivers and expected developers to make their game work with it. The same strategy that MS used for their OS back in the 90's.
Thats at least how things got where they are now.
Intermittent driver timeout or crash may be observed while playing Warhammer 40,000: Space Marine 2 on some AMD Graphics Products, such as the AMD Ryzen™ AI 9 HX 370.)
Lower than expected performance may be observed in Delta Force on Radeon™ RX 7000 series graphics products.
Intermittent stutter may be observed while playing Marvel Rivals when AMD FidelityFX™ Super Resolution 3 frame generation is enabled. "
https://www.amd.com/en/resources/support-articles/release-no...
That is not to say this is good or bad. Just that it appears common.
When it comes to drivers, IMO all they really need is reasonable functionality on linux. That alone would probably be enough to get used in a budget steam machine or budget pc builds, with Windows 11 being a disaster and both RAM and GPU prices shooting through the roof. The choice may soon be Bazzite Linux with a janky GPU or gaming on your phone.
I don't think the Chinese government will be too upset if cheap Chinese GPUs work best with China-made games. It will be quite the cultural coup if, in 20 years time, the most popular shooter is a Chinese version of Call of Duty or Battlefield.
With their new Radeon/RDNA architecture it took AMD years to overcome their reputation for having shitty drivers on their consumer GPUs (and that reputation was indeed deserved early on). And I bet if you go read GPU discussion online today you'll still find people saying that AMD is a worse choice because of drivers.
Oh and that's just to get the drivers to work. Not including company-specific features that need to be integrated by the game devs into their game codebase, like DLSS / FrameGen and FSR. And in the past there was other Nvidia/AMD-specific stuff like PhysX, hair rendering, etc.