hogepodge
We've run a few events this year (disclosing again that I work for Modular, to put my comments into context), and we've had some great feedback from people who have never done GPU programming about how easy it was to get started using Mojo.
C++ is a powerful and mature language, but it also has a steep learning curve. There's a lot of space for making GPU (and other high performance computing) easier, and platforms/languages like Triton and Julia are also exploring the space alongside Mojo. There's a huge opportunity to make GPU programming easier, and a bit part of that opportunity is in abstracting away as much of the device-specific coding as you can.
I was a HPC C++ programmer for a long time, and I always found recompiling for new devices to be one of the most painful things about working in C++ (for example, the often necessary nightmare of cmake). Mojo offers a lot of affordances that improve on the programming experience at the language, compiler, and runtime levels.
It was highly aspirational goal, and practically speaking it's better right now to take inspiration from Python and have stronger integration hooks into the language (full disclosure, I work at Modular). We've specifically stopped using the "superset of Python" language to be more accurate about what the language is meant for right now.
https://www.modular.com/blog/modular-platform-25-3-450k-line...
That's been the foundation for a lot of the performance work we've demonstrated publicly, most recently with our AMD partnership announcement.
https://www.modular.com/blog/modular-x-amd-unleashing-ai-per...
We're pretty committed to doing this work in the open, and we've taken a bunch of direct feedback and contributions from the community that have improved the standard library (also open source) and core language.
We're also putting in a lot of work to make Mojo more accessible for users. For example, our GPU Puzzles series is turning into a cornerstone of demonstrating how Mojo is meant to improve the GPU programming experience (that's work my team is directly responsible for, and I'm really proud of the experience people have had with it).
https://builds.modular.com/puzzles/introduction.html
For production workloads, I can say that we're using it in production, but as you said yourself, adoption takes time. I believe we're on the path to get there, and hopefully the work we're doing in public speaks for itself. It's really important to me that we back up our claims with evidence and real-world use cases.