So much of the slowdown in my last company's data pipeline was from Python and its interpreter. Training our model took two days when the ML Engineers first built it, but I got it down to a few hours after spending a ton of time getting it to use multiprocessing, GPUs, and TPUs, and I was only given that time because we were working at a large, profitable company that had the budget to let me and my team spend months on it. Having Mojo would have been a godsend for us and likely would have saved months of fighting against the Python interpreter and nightly build versions of a bunch of different software.
Mojo is the most excited I have been for a language in a very long time. In my view, it is set to do what Julia tried to do and failed, precisely because Mojo people understood that they have to meet people where they are, and they are in Python. Julia changed too many things to the point that it was annoying to remember what was the same and what was different (and also Julia is a 1-based index language, instead of 0-based, which is such a small difference and such a annoying source of bugs). I hope to start to use Mojo soon, when it is more matured.
Wow this is sick! My banana orchard is full of monitoring devices with scripts written in Python. If I port them to Mojo then my entire region will benefit from juicer, thicker bananas! Que bueno!
Yes, but it's not fortran or c using intrinsics and pragma everywhere (check out the totally unreadable NumPy implementation). I think the whole point is to empower the experts.
@@someghosts it's a joke from "2015 LLVM Developers’ Meeting: Joseph Groff & Chris Lattner “Swift's High-Level IR: A Case Study..."", Chris Lattner is the creator of Swift, and LLVM
Looking through the language documentation, I miss: a switch or match statement, the ability to make that an expression, pattern matching, guards, sum datatypes (you can't define your own version of optional in mojo), tuples, structure and tuple decomposition... Get rid of def as fn is much better and add those things and we are talking. But cudos for producing a value semantic programming language that does perform well. Swift failed to achieve that (yet). The performance of mojo-generated code is impressive.
I am that unicorn that he said does not exist (in the beginning of the talk), yet I had trouble getting hired in a related job. (A PhD related to ML/AI + veteran in CS/CE)
"Yet another thing" seems to misunderstand the stated goal. This isn't just a general purpose language that's meant to run on CPUs and serve HTTP requests. This is a toolchain for building software that can be deployed on a wide variety of accelerators. This is net-new value.
I see Mojo as a replacement for python, the fact that every python code will be valid and faster Mojo Code is just incredible. Its basically a python but with a real and strong type system. It even can be a very solid alternative to Rust if mojo can be as safe as Rust and handles unsafe stuff better than Rust
I really havent seen that validated. When a python file is not COMPLETELY REWORKED it is not valid Mojo. So it supposedly defaults to python... that will be slower as calling python means you have to fire up the interpreter...
Lmao this is something Python developers has sought for years. Few years ago Rob Pike from Go said most of Go's early adopters were from Python. They were looking for a language as expressive as Python but with better performance. You can also see Python devs trying to adopt Rust. Mojo is a game changer for the Python community, the excitement is expected.
Some consider python "difficult to maintain". So I wonder if, in practice, combining that with user-authored kernel-specific optimization passes will be even harder to maintain.
I believe that effect would be the opposite, big python projects are difficult to maintain because - a) performance overhead creeps in, and overcoming it becomes a technical debt. b) The language commonly is used to have things done asap (and that is good), and the maintainability is not a concern. c) Performance critical parts are written in C and C++. d) Code 'legacifies' over time with original developers leaving and their though being lost. What it would result in - is that you now can skip writing a library in C, that you would then funnel to Python; There is a better way to solve overhead creep; There would be more libraries that have better separation of concerns and less external dependencies; This is a huge win overall.
@@OREYG Interesting perspective. I should have mentioned I was talking more about dynamic/duck typing makes testing & changing code hard, and how the directives may add another layer of complexity. One might have to worry about composing functions and how the directives interact. To your point though, code that would have these compiler directives would hopefully be mostly kernel code, which is very much write+profile once, then leave it alone! (ie. the forking approach to software maintenance :) )
I'm sorry man, Mojo and it's infra might actually be something great, but the initial presentation and even the homepage is so full of B$ (68.000 times faster!!!11) that I have a hard time taking it seriously.
In this day and age the clickbait is required. Without it your language would never hit the news and we won't be watching this video here. There are a lot of languages which we don't hear about simply because there is no hype around them, like nim or crystal.
Then see through the B$, and don't be the kid that giggles at dirty sounding names in a science class. It's quite easy try mojo to see if it has merit.
Haha. Well it actually got that much faster but not with the code an average person would write. For normal Python - Mojo code it got about 100x faster.
I just hope for the love of God BDFL Chris hands it off to open source community. This proprietary stance is gonna kill it before it even hits the ground.
You lost me with the concept (yet another "low-level" language with high-level syntax, with inevitable massive tradeoffs on both ends) then got me back with the pitch (optimised to mobilise the existing talent along a specific stack) then lost me again with the rationale (we can't get people off Python so we'll make not-Python and hope they don't notice) then slowly gained me back again as I thought about it (regardless of how intelligent or stupid the talent pool is, rewriting all existing code is just impractical) then almost lost me again again with those graphs (why is the comparison against _Python_ instead of anything people actually use for performance-critical code? which one of those bars is you and which other one do we care about?). In the end I'm conflicted. I'll say you've lost me because the 🔥seems to be part of the language name. You could have had me if you'd used Courier Prime for _all_ the monospace, not just some of it.
No bro come on. Life is not that easy xD The « import package » culture of python devs is a bad thing. Software is a bit more complex than that. Building the technology is different from using it, so super high level tech users like python devs don’t see what’s happening underneath the tip of the iceberg.
But you actually can and always see the source code... importing things is way better than whatever hell brews in rust every time you compile the thing
As a system programming language, it will be only compete with rust/c++. For web dev/machine learning/mobile app development/ERP, etc won't be affected a bit by this. 😂😂😂
You can't believe how excited I am for Mojo. I have yearned for a faster total reimplementation of Python for years. Go Modular!
Being and engineer and programmer myself and notoriously hard to impress: My deepest respect for Chris and his work!
So much of the slowdown in my last company's data pipeline was from Python and its interpreter. Training our model took two days when the ML Engineers first built it, but I got it down to a few hours after spending a ton of time getting it to use multiprocessing, GPUs, and TPUs, and I was only given that time because we were working at a large, profitable company that had the budget to let me and my team spend months on it.
Having Mojo would have been a godsend for us and likely would have saved months of fighting against the Python interpreter and nightly build versions of a bunch of different software.
as an alltime swift guy from the first day it came out - i'm excited for Mojo
i watch every interview with Chris and he never dissapoints
1
This might be transformative, I'm going to contribute the first day they make it open source!
Thanks for this. A lot to unpack. I really hope Mojo succeeds in solving some of these challenges.
great work guys!
I don't care for Mojo, but I love hearing about the compiler tech!
This is way a much more attractive language than Rust. Looking forward to trying this.
Thanks ! I have the mojo for Mojo.
I don’t understood all stuff but I hyped to learn as much as possible!
Mojo is the most excited I have been for a language in a very long time.
In my view, it is set to do what Julia tried to do and failed, precisely because Mojo people understood that they have to meet people where they are, and they are in Python.
Julia changed too many things to the point that it was annoying to remember what was the same and what was different (and also Julia is a 1-based index language, instead of 0-based, which is such a small difference and such a annoying source of bugs).
I hope to start to use Mojo soon, when it is more matured.
what's the roadmap for native windows release?
Amazing
Wow this is sick! My banana orchard is full of monitoring devices with scripts written in Python. If I port them to Mojo then my entire region will benefit from juicer, thicker bananas! Que bueno!
cool video)
Do you have matmul number on nvidia HW compared to their library?
seems pretty cool actually
so is it open source?
They said that their gemm implementation is 2k lines. So that means that you still need considerable expertise and time to write these core libraries?
Yes, but it's not fortran or c using intrinsics and pragma everywhere (check out the totally unreadable NumPy implementation). I think the whole point is to empower the experts.
@@soracc_ Can’t see how this low level can be made more readable in any language.
Chris Lattner has come a long way since his days as an intern working on Swift :D
Inside joke?
@@someghosts it's a joke from "2015 LLVM Developers’ Meeting: Joseph Groff & Chris Lattner “Swift's High-Level IR: A Case Study..."", Chris Lattner is the creator of Swift, and LLVM
Man I wish someone like Chris Lattner came to JavaScript to rebrand and fix it.
Looking through the language documentation, I miss: a switch or match statement, the ability to make that an expression, pattern matching, guards, sum datatypes (you can't define your own version of optional in mojo), tuples, structure and tuple decomposition... Get rid of def as fn is much better and add those things and we are talking. But cudos for producing a value semantic programming language that does perform well. Swift failed to achieve that (yet). The performance of mojo-generated code is impressive.
5:00
I am that unicorn that he said does not exist (in the beginning of the talk), yet I had trouble getting hired in a related job. (A PhD related to ML/AI + veteran in CS/CE)
what’s ur phd in?
We need fewer things... Proceeds with creating yet another thing.
Yeah not really..
"Yet another thing" seems to misunderstand the stated goal. This isn't just a general purpose language that's meant to run on CPUs and serve HTTP requests. This is a toolchain for building software that can be deployed on a wide variety of accelerators. This is net-new value.
need compiler guilds
I see Mojo as a replacement for python, the fact that every python code will be valid and faster Mojo Code is just incredible. Its basically a python but with a real and strong type system. It even can be a very solid alternative to Rust if mojo can be as safe as Rust and handles unsafe stuff better than Rust
I really havent seen that validated. When a python file is not COMPLETELY REWORKED it is not valid Mojo. So it supposedly defaults to python... that will be slower as calling python means you have to fire up the interpreter...
Having the user have to define there own objective function for auto-tuning is the killer for me
How did you get over 100K users in just one year? I remember just a few months ago it was very closed beta. Is it because of popularity of python?
Lmao this is something Python developers has sought for years. Few years ago Rob Pike from Go said most of Go's early adopters were from Python. They were looking for a language as expressive as Python but with better performance. You can also see Python devs trying to adopt Rust. Mojo is a game changer for the Python community, the excitement is expected.
Waiting for someone to explain what the heck they said lol jk
I believe Python will take over as the de facto programming language within 5 years.
I believe hamburgers will take over as the de facto sandwich within the decade
@@ITSecNEO I should have specified I meant Python with the Mojo compliler will take over. :)
Some consider python "difficult to maintain". So I wonder if, in practice, combining that with user-authored kernel-specific optimization passes will be even harder to maintain.
I believe that effect would be the opposite, big python projects are difficult to maintain because -
a) performance overhead creeps in, and overcoming it becomes a technical debt.
b) The language commonly is used to have things done asap (and that is good), and the maintainability is not a concern.
c) Performance critical parts are written in C and C++.
d) Code 'legacifies' over time with original developers leaving and their though being lost.
What it would result in - is that you now can skip writing a library in C, that you would then funnel to Python; There is a better way to solve overhead creep; There would be more libraries that have better separation of concerns and less external dependencies;
This is a huge win overall.
@@OREYG Interesting perspective. I should have mentioned I was talking more about dynamic/duck typing makes testing & changing code hard, and how the directives may add another layer of complexity. One might have to worry about composing functions and how the directives interact.
To your point though, code that would have these compiler directives would hopefully be mostly kernel code, which is very much write+profile once, then leave it alone! (ie. the forking approach to software maintenance :) )
3:10 not a research project…say it again for the ppl in the back lol
So you don't use numpy 😂😂
I bet they are just doing this with python for now, but they will eventually invent a new AI focused language
I'm sorry man, Mojo and it's infra might actually be something great, but the initial presentation and even the homepage is so full of B$ (68.000 times faster!!!11) that I have a hard time taking it seriously.
In this day and age the clickbait is required. Without it your language would never hit the news and we won't be watching this video here. There are a lot of languages which we don't hear about simply because there is no hype around them, like nim or crystal.
Then see through the B$, and don't be the kid that giggles at dirty sounding names in a science class. It's quite easy try mojo to see if it has merit.
Haha. Well it actually got that much faster but not with the code an average person would write. For normal Python - Mojo code it got about 100x faster.
What is you definition of BS?
I just hope for the love of God BDFL Chris hands it off to open source community. This proprietary stance is gonna kill it before it even hits the ground.
Python is the glue code for many of these things I don't understand how this is useful for your aim of having a unified ai framework from bottom up.
please Chris please go back to Tesla !!! patch things up with Elon . at this point in humanity history we need you there!!!!
You lost me with the concept (yet another "low-level" language with high-level syntax, with inevitable massive tradeoffs on both ends) then got me back with the pitch (optimised to mobilise the existing talent along a specific stack) then lost me again with the rationale (we can't get people off Python so we'll make not-Python and hope they don't notice) then slowly gained me back again as I thought about it (regardless of how intelligent or stupid the talent pool is, rewriting all existing code is just impractical) then almost lost me again again with those graphs (why is the comparison against _Python_ instead of anything people actually use for performance-critical code? which one of those bars is you and which other one do we care about?). In the end I'm conflicted. I'll say you've lost me because the 🔥seems to be part of the language name. You could have had me if you'd used Courier Prime for _all_ the monospace, not just some of it.
😂 This one has had an entire roller-coaster ride out of this talk. That'll be $10.
Perl was better
Mojo basically adds all the bloated crap from cpp into python
You’re wrong 😑
Couldn't Mojo just been a python package?
9:23
@@NickWindhamI don't agree with that as a good reason
@@yorailevi6747 fair enough
No bro come on. Life is not that easy xD The « import package » culture of python devs is a bad thing. Software is a bit more complex than that. Building the technology is different from using it, so super high level tech users like python devs don’t see what’s happening underneath the tip of the iceberg.
But you actually can and always see the source code... importing things is way better than whatever hell brews in rust every time you compile the thing
Wake me up when it's open-source 🥱
it is open for standard library
As a system programming language, it will be only compete with rust/c++.
For web dev/machine learning/mobile app development/ERP, etc won't be affected a bit by this. 😂😂😂