I'm honestly more excited for Mojo as a competitor in the systems programming space (Rust) than the ML space. Where Rust's default way of doing things gives yo

I'm honestly more excited for Mojo as a competitor in the systems programming space (Rust) than the ML space. Where Rust's default way of doing things gives you the most optimal performance (i.e no copy), you pay for that with code complexity and symbol soup syntax. If you want to move fast, you copy things, which is both ugly and wasteful. Mojo on the other hand, based on the ownership presentation, by default makes some assumptions on your behalf for most common situations that you can then override if you need every ounce of performance out of the program. I appreciate this approach more because I can hit the ground running and build something with great performance and then optimize it later when needed. I'm looking forward to building something with it once they finish their work on the networking and asynchronous libraries.