All-in-one C++, Rust, AND Python Successor? Mojo 

I always find "compared to Python" when talking about speed a little bit useless. Python is always slower than anything, except when you're using a C lib, so compared to what Python exactly?

I can't live without curly brackets

Finally, a python that I can use without scratching my hair off my head

When you started wondering why that print call wasn't giving an ownership error, I envisioned a bunch of early adopters spitting out their coffee hoping they don't fix that "bug" and bork their prototype codebases.

Seems like a hotch potch. Can't imagine auditing a codebase with fn functions and def functions coexisting simultaneously. Also, I use Rust for its borrow checker guarantees. In such a language it seems like it would be impossible to ensure that GC has to do a lot less work than necessary which will impact performance. Although it can't replace systems languages, it has the potential to become a de-facto replacement of Python at some point.

Thank for wonderful presentation! In their doc(roadmap) it's mentioned that ownership is only partially implemented, no proper lifetime support right now. It's wonderful to see how Mojo incorporate c/c++ freedom, rust safety and python dynamic feature in same language.

Python easiness and syntax with features and performance as C++ and Rust. Mojo is going to be a massive game changer whenever it officially releases to the public as stable release. I love the new research and development into modern programming language development and design. Making newer better programming languages to replace all the old ones that have been the status quo for decades is what we need to do more of.

8:12 I'm probably wrong because I'm not familiar with the ownership concept that seems to be from Rust, but I think it's because - first you created rocky - then you changed its mass value using inout - then you ran the cell again, but giving the ownership to the function - so when calling print(), you might be referring to the first one you created, or the location in memory of the first rocky.mass So to investigate, you could try starting clean and running again

Thank you! Impressive first look, and agree with your ending: can't imagine building anything with it just yet.

This is legit awful. I've been waiting for a Python-like language that can do stuff like this, but why change totally basic idiomatic things about Python just in Mojo? Like for example why the hell does Int and Bool have to be upper case, when they aren't in Python? Also all this fuss with inout and owned is just hella confusing. If I want a borrow checker or want to manage my own memory I would much rather use Rust, Zig or just plain C. I already have a problem with Python having a lot of implied and hidden behaviour, this just feels like putting on yet another layer of that. Also what exactly does this give us beyond what you can already get with Numba or Cython? I get that matrix multiplication go brrrrr, but we already have all these other amazing options, some of which (JAX) also run on GPU and TPU. To me this whole thing just looks like the C -> C++ transition. Just add a lot of shit to a language without any seriously thought out concept, keep patching it, until it becomes 5 languages at once, and call it a day. I sincerely hope this will not actually start being a thing.

What I find most important is that this language aims to be a superset of Python. Same as Kotlin and Java, or Typescript and Javascript. Or C and C++. That way migrating old codebases can happen by simply changing the file endings. I'm excited about that, and will probably start using it in a project when it's possible to do that.

It’s quite honestly infuriating that a language in this early stage with so much *design* still to do, let alone implementing and fixing basic stuff, gets soooo much attention just because they plastered the label “A.I.” on it. Yes, it can do very fast matrix multiplication, but that could have gone into a Python extension.

pattern matching and rust-like enums are a must for me now :/

Thanks for sharing your exploration of Mojo. I'm guessing all the extra details, e.g., "register passable" are a good thing, but from this first tour of the language, it seems quite cumbersome. I think I'll wait till 2.0.

Sounds promising, but i doubt it will be used in any way other than python replacement. Python has a bunch of serious desigh flaws which Mojo had no choice but to inherit in order to keep compatibility. I'd really love if people just migrated from python to nim instead of writing dosens of tools for python, destroying it's ecosystem consistency even further

Closed source = argument is invalid

To me it seems like two languages combined to a Frankenstein hybrid

I was hoping for Option, Result and Error Handling like Rust do. I personally use Python or Rust and Mojo just doesn't fit anywhere for me right now.

It is often said that Julia solves Python's "2-language problem" (using Python for general coding and another for routines that need speed). But soon we can say Julia solves Python's "10-language" problem!

Mojo was recently caught lying about their benchmarks. This did it for me. Lost all credibility.

looks interesting, but it's another one of those languages that treats windows as a 2nd class citizen, so it's probably going to end up being a niche language.

What does the presenter mean, "it's looking pretty pythonesque?" This language is a SUPERSET of python. Does he know set theory, or at least, the meaning of the word superset? He's got that up-speak accent, too, that he was using in the beginning, like everything is a question, but it wasn't.

my high hopes for Mojo ruined in 17 minutes 19 seconds.

If anybody from Mojo/Modular is reading this, please make the error messages less technical. Try to make them so any average programmer can understand what went wrong.

Being a superset of python can make it easy for people to adopt Mojo, but it will inevitably become a mess like JavaScript and typescript

The Python community really doesn’t need any more fragmentation.

Chris Lattner is still salty about his failure from Swift + Tensorflow. This is just yet another pathetic attempt to divide the python community.

Mojo is very promising to make it really compelling for rust devs they have to add features like Enum and match, it would be actually insane if they manage to take those features from rust with better defaults and making it easier to use. So excited for Mojo and thank you for the high quality videos as always!

Simply, no. I am interested to see how it plays out though.

You can't be serious with all this hype for Mojo, really. You want a fast language that can call Python with zero overhead? Well, there's Julia for that. It is also a language focused on being at least partial python replacement. Why not Julia? The only actual reason i can think of is Julia being garbage collected, but you can even work around that with manual memory management.

I always did like python, its been my main language for a good 10 years now, but this seems like it's trying too much, there's too many different keywords and it doesn't feel consistent, all I really want is rust with maybe some optionally relaxed safety rules (maybe some of the behind the scenes inference of lobster when you leave some details out). Or just an easier way to do dynamic memory, but then again I haven't messed around in unsafe too much, I don't mind raw pointers so maybe that's the way. Seems like a potential case of making things worse for the sake of backward compatibility (except to multiple languages).

If only Nim was more known. Basically Python like syntax but compiled and C like performance

i32 > Int I like first type naming much more than latter ..

it would be interesting to know if its possible to make DSP Programming with Mojo

Are people that obtuse to Nim? Like it already is what Mojo is trying to become.

Someone thought "Would not it be nice if rust had python syntax?" They don't understand the point of python. Python is for people who don't want to code, but have to. They want to get away with doing the minimum and are happy with a slow running program as long as they can move on and start doing something else.

I find it funny that to make a language like Python faster you have to create a whole new language on top of it, it’s very interesting yea, but it kind of defeats the purpose of using Python entirely. (yes there’s PyPy but it’s still meh)

I can't stand Python's 'dunder' syntax but it doesn't look like Mojo offers any alternative to it. I mean, this is just the ugliest thing in Python. Wasted opportunity!

Just code in Julia for your high performance computing needs. Has all you'll need, speed and ease. What's the point in reinventing the wheel. 😏

for me it seems mojo is helping you to get things done quickly while rust is helping you get things done correctly while the internals are very similar.

I need curly braces., I just don't like python's indentation only style, so Mojo isn't going to work for me either. I do indent blocks, but that's not enough to me on its own.

"Get started today" by giving us all your personal details and we _might_ let you learn more ... 🤦‍♂

If it doesn't have a GOTO command I'm not using it.

thank you for a great first look at this weird language.

you forget the compile time evaluation inspired by Zig lang, which will be a major feature for Mojo

Still 100% on paper. Sure its GA now its still need to be in peoples hands to fiddle and see how good it really is. Overall, I don't really like Python except for simple things.

looks muck simpler than Rust, C++, but I'll die without curly brackets 🥲

Additionally you need to import list from collections I think

I think that this error related to using object after passing ownership is fixed

While it's interesting to follow your train of thought, I still feel this video could have used a bit more background research/preparation before recording.

7 Behold, he cometh with clouds; and every eye shall see him, and they also which pierced him: and all kindreds of the earth shall wail because of him. Even so, Amen. (Rev.1:7) 12 And I beheld when he had opened the sixth seal, and, lo, there was a great earthquake; and the sun became black as sackcloth of hair, and the moon became as blood; 13 And the stars of heaven fell unto the earth, even as a fig tree casteth her untimely figs, when she is shaken of a mighty wind. 14 And the heaven departed as a scroll when it is rolled together; and every mountain and island were moved out of their places. 15 And the kings of the earth, and the great men, and the rich men, and the chief captains, and the mighty men, and every bondman, and every free man, hid themselves in the dens and in the rocks of the mountains; 16 And said to the mountains and rocks, Fall on us, and hide us from the face of him that sitteth on the throne, and from the wrath of the Lamb: 17 For the great day of his wrath is come; and who shall be able to stand? (Rev.6:12-17)

There will be a lot of push back from this, sadly. Look at what happend at the early stages of typescript

It looks nice, but no thanks. Good video anyway👍.

I do want to build a large project within the next months to years. We have a product on sale that we bought that needs to be re-written due to bad code, and we want to shift to a different direction with the product after the sales have begun. I am the lead developer, who is still carrying the product on my own. I will decide on the tech stack and we need optimal performance that scales well. Mojo could change everything for us. I'm not ready for a C++ project and I think those times are over nowadays, I also think Rust is great, but I will have trouble to find people and they will be expensive. I do think it's easy to find many Python developers who could quickly adapt to Mojo, those programmers would just lack to program the Mojo way to get the most performance out of it. A lot of stuff could be enforced with linting though, and a lot can be teached and shared, abstracted and re-used. Our project is not related with AI, but the option for using a borrow checker without enforcing this way of programming is a selling point for me. As long as I, as the dev lead, can enforce practices on the project level, I'd want to consider Mojo for it.

It's more technical than Python. I had to pay attention to a lot more details.

This is just a py replacer

Mojo, if you can replace c++ than Ai will replace you and we will be replaced by promote engineers and those will eventually be replaced by the autoGpt and world will crashed..so plz don't try to replace c++ plz

Ownership is likely only modify perms

I think it seems like a great language for games

What is that environment you were coding in?

I feel like when a language trying to pump the hype then it will end up like vlang 🤔

Does this get compiled or it is interpreted?

is this faster then C++ and saver then Rust ??

I wonder why this over Julia: they seem to have the same objectives or very very close.

Mojo is a mojón

Yes lord!

Same ol'OOP 💩...

More mojo

Its a cool language if numpy didn't exist, python wasn't an actively developed language with a strong foundation, and integrating C/Rust modules into python wasn't a piece of cake. However, having Mojo concepts migrated into python 3.14/3.15 is something i wouldn't be surprised to see

still prefer nim

Wow time flies. Mojo is already 7 months old.

make_larger is a function that’s done at the time of the print

lets wait for the final release

From the github repo it doesn‘t look serious at all

Could your perform some your own benchmarks?

Seems like demoware at the moment. Got complicated AI stuff working at the expense of the basics

I use VSC, which one are you using?

Thanks for the video! This one is not for me, for the fact it has many of the things I dislike about Python.

I don't see mojo going very far. The only advantage of mojo is the backwards-compatibility to python. If you subtract the backwards-compatibility to python from mojo, there is nothing left but a strange raggle-taggle of other languages mix. I think Rust got a much wider spectrum (from bare metal to frontend) and concise way of doing things. Maybe Rust is missing the ecosystem python got, but Rust got a pretty strong base, which Mojo is lacking as an unreleased language. PS.: I mean Python is only a strange way to bind c-packages together. Using Mojo for using python to bind c-packages together doesnt make it better.

The hype train?

borrowed not being default in rust is probably my biggest issue with it, to a level I could not imagine I could get annoyed with a fact. so mojo got me there straight.

"orders of magnitude faster than python" doing it yourself is faster than python most of the time

Hahahaha, lmao.

A Python killer for sure. But I doubt it will compete with Rust for low level system programming.

Really similar to Scala to me

I really don't think we need any more programming languages. What does this do that others can't? Edit: reminds me of xkcd 927

more Mojo please)

Finally!!! I'll be adopting it as soon as it's usable. And promises to keep adding modern programming techniques. The most important thing for Mojo designers to take note is to be pragmatic (like Python, Kotlin), not evangelistic (I say this is right, and you must follow it) like Rust or C++. Do most of the work in the compiler.

First!

Warning: horrible pedantry incoming... The word voilà (from French, literally "see there") has a v in front /vwäˈlä/ Mojo looks really cool though. Rust and Python are my favorite languages.