| ▲ | 3abiton 13 hours ago |
| It's barely gaining adoption though. The lack of buzz is a chicken and egg issue for Mojo. I fiddled shortly with it (mainly to get it working some of my pythong scripts), and it was suprisingly easy. It'll shoot up one day for sure if Latner doesn't give up early on it. |
|
| ▲ | ronsor 11 hours ago | parent | next [-] |
| Isn't the compiler still closed source? I and many other ML devs have no interest in a closed-source compiler. We have enough proprietary things from NVIDIA. |
| |
| ▲ | 0x696C6961 8 hours ago | parent | next [-] | | Yeah, the mojo pitch is so good, but I don't think anyone has an appetite for the potential fuckery that comes with a closed source platform. | |
| ▲ | 3abiton 8 hours ago | parent | prev [-] | | Yes, but Latner said multiple time it's closed until it matures (he apparently did this with llvm and swift too). So not unusal. His open source target is end of 2026. In all fairness, I have 0 doubts that he would deliver. | | |
| ▲ | pjmlp 2 hours ago | parent [-] | | Given Swift for Tensorflow, lets see how this one goes. | | |
| ▲ | jacobgorm 16 minutes ago | parent | next [-] | | Who would anyone want to pair a subpar language with a subpar ML framework? | | |
| ▲ | pjmlp 3 minutes ago | parent [-] | | That is the thing, what lessons were learnt from it, and how will Mojo tackle them. |
| |
| ▲ | saagarjha an hour ago | parent | prev [-] | | That one did get open sourced but nobody ended up wanting to use it |
|
|
|
|
| ▲ | boredatoms 9 hours ago | parent | prev [-] |
| I feel like its in AMD/Intel/G’s interest to pile a load of effort into (an open source) mojo |