The Mojo language (by Modular, now Qualcomm) is now open-source
11–20 of 121 posts
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#12I had been holding off on testing out mojo till it was open sourced, and started picking it up this week. So far I've been enjoying the language (pythonic, comptime, tile support) and plan to spend time using it to work with gpus to learn more, the puzzles are also pretty cool.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#13When mojo 1.0 was announced, I looked into porting my current rust project (a very opinionated type-driven DICOM library/anonymizer that has a spec implemented in haskell) and it wasn't ready for that sort of work yet vs continuing with rust. Which is fine! The numerics side looks great. I'm glad they have reached 1.0 and open sourced.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#14Maybe I'm a party pooper, but given Qualcomm history, open sourcing just after acquisition feels like they don't care about it and they're going to let it die while they cut Modular in pieces and extract all the juice possible of their cloud offering.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#15Don't reward them with your support just because they are forced to open source something.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#16Strategically speaking, I think this only makes sense as an anti-NVIDIA play.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#17Qualcomm is a notoriously closed source company. Don't reward them with your support just because they are forced to open source something.
I do not see your point.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#18Qualcomm is a notoriously closed source company. Don't reward them with your support just because they are forced to open source something.
Re: The Mojo language (by Modular, now Qualcomm) is now open-source
#19Does this project have any meaningful traction? Seemed like a cool idea, but I wasn't even sure what problem does it solves. Looks like its completely missing from the regular discussion / news outlets. Every 1-2 years some barely visible post/article reminds me it even exists...
At this point "developers" these days sound a lot more like consumers than those who actually do research on a tool that solves a problem. Ocaml is barely mentioned in the news and rarely HNers here use that language, but it is Jane Street that maintains and uses it.
Judging by hype isn't a great way of evaluating a language. I am not going to check the entire Nvidia stack, from CUDA, to CUTLASS to cuDNN and even on PyTorch's side just to solve a runtime error that could have originated from either place when Mojo solves all of that.