Earlier quoted context omitted.
How did Mojo already lose when Qualcomm just made a $4B bet on it? You're forgetting that the language is still pre-1.0. The way I think of this... if Modular is able to remain an open platform, being part of an established corporation with existing customers is a better way to drive penetration compared to acquiring new customers.
The founders won the lottery, the language most likely will never make mainstream.
Qualcomm to Acquire Modular
101–110 of 134 posts
Re: Qualcomm to Acquire Modular
#102Earlier quoted context omitted.
But the Modular stack is focused on developer productivity. It is still early but there has been substantial work on all these
I am yet to see the same Windows love as CUDA. Same to IDE integration and graphical debugging experience for GPU code. Until now, it was been the usual UNIX cli, and text mode lldb like debugging for CPU side. At least it what I have been made aware of.
Re: Qualcomm to Acquire Modular
#103Earlier quoted context omitted.
one of the reasons I rarely read press releases is that I don't believe in promises -- I believe in _incentives_. In this case, what will Qualcomm be incentivized to do? What are in their interests?
Qualcomm has an enormous incentive in breaking Nvidia's CUDA grip on GPU programming.
However the danger is that the language sees wide adoption but nobody uses it with Qualcomm hardware. Instead it might encourage people to buy AMD. This is a terrible outcome for Qualcomm. They paid to boost someone else's sales.
So the incentive is to make sure it runs best on Qualcomm and to at least slightly hobble other hardware. But the safest thing overall is to support Nvidia, Qualcomm, and that's it.
Re: Qualcomm to Acquire Modular
#104Earlier quoted context omitted.
It's an all stock deal. No cash. With undoubtedly a very healthy earn out. > They must see value in the technology. What value? Mojo doesn't currently support any of Qualcomm's GPUs.
I have a friend who works at Modular. FWIU, the employees got shafted by the acquisition financially.
Re: Qualcomm to Acquire Modular
#105Earlier quoted context omitted.
Julia and the Python JITs from GPU vendors will. Mojo already lost the moment AMD, NVIDIA and Intel decided to fully support Python and Julia. Additionally all of the parallel programming improvements in ISO C++ are coming from them as well, Modular did not have much moat when being a follower and not a driver.
How did Mojo already lose when Qualcomm just made a $4B bet on it? You're forgetting that the language is still pre-1.0. The way I think of this... if Modular is able to remain an open platform, being part of an established corporation with existing customers is a better way to drive penetration compared to acquiring new customers.
I look forward to seeing open source mojo and the community that will bring.
Re: Qualcomm to Acquire Modular
#106Tbh, Modular getting acquired happened sooner than I would have expected, if ever. Don't know how to feel about this one. Also so many mixed feelings about Mojo, the programming language powering Modular. Of course Chris Lattner is free to pursue whatever he wants, his many contributions to tech will always be highly regarded, but to me it feels as if he "wasted" lots of his precious mental capacity on making Mojo a…
Just wanted to confirm that we're still open sourcing Mojo this year!
And appreciate the nuanced feedback.
Re: Qualcomm to Acquire Modular
#107Earlier quoted context omitted.
How did Mojo already lose when Qualcomm just made a $4B bet on it? You're forgetting that the language is still pre-1.0. The way I think of this... if Modular is able to remain an open platform, being part of an established corporation with existing customers is a better way to drive penetration compared to acquiring new customers.
I'm not really sure if Mojo has lost or not, but the community has felt quite different than other language communities I have encountered. The development feels less organic and more driven by venture capital. This is most acutely felt in the current closed source development of mojo itself, which seems like it will continue into the near future. I look forward to seeing open source mojo and the community that will…
The development has been driven by the needs of Modular.
> This is most acutely felt in the current closed source development of mojo itself
Mojo compiler is closed, the language development is quite open. Some of the proposed changes have been shelved or tweaked based on community feedback. However, you should understand that the compiler is closed to avoid design by committee and bike-shedding, Modular will and does veto decisions on core language semantics, see: https://forum.modular.com/t/canonicalize-apis-around-int/253...
> which seems like it will continue into the near future.
The compiler is getting opened this August. I must admit, a lot of people who would be normally interested in the language are hesitant to poke at it with a stick with the current license (myself included).
The language has really great set of features and functionalities wrapped in a familiar syntax, I have zero doubt it'll reach mainstream adoption.
Re: Qualcomm to Acquire Modular
#108Earlier quoted context omitted.
The founders won the lottery, the language most likely will never make mainstream.
Ha! I think whether Mojo will make mainstream or not is already a forgone conclusion. It solves too much of a technical problem to be niche. To me, it is a matter of when... not if.
Re: Qualcomm to Acquire Modular
#109Earlier quoted context omitted.
Ha! I think whether Mojo will make mainstream or not is already a forgone conclusion. It solves too much of a technical problem to be niche. To me, it is a matter of when... not if.
It is not the only solution to that technical problem though. Past attempts at this have shown a clear preference for solutions that actually are extensions of CPython rather than distinct tool chains.
Re: Qualcomm to Acquire Modular
#110Earlier quoted context omitted.
I am yet to see the same Windows love as CUDA. Same to IDE integration and graphical debugging experience for GPU code. Until now, it was been the usual UNIX cli, and text mode lldb like debugging for CPU side. At least it what I have been made aware of.
It doesn't have a lot of Windows support yet because nobody deploys datacenter-scale AI serving on Windows OS.
But I get we don't want to get them on board, only complain how NVIDIA takes over everything.