Why are you using Mojo?
Just curious: why are you using Mojo?
i will start with the obvious, lets see where this goes 😉
19 Replies
:mojo:
performance
Scientific and high-performance computing (CPU + Accelerators).
It's pretty fun to code in Mojo! I always wanted to use a more pythonic systems programming language. Mojo's syntax, dunder methods, etc - this all gives a really nice flow when you're coding.
I actually don't get much of a performance boost in my application with Mojo, but maybe I'm doing it wrong.
Tired of the two language problem.
I have one foot in the ML world and one foot in the geospatial world, and both struggle with the "two-language" problem.
I.e. debugging gets annoying when you have to switch from Python to the language that your libs are written in (C/C++).
Having one language all the way through would be awesome.
I always wanted a language where I don't break my mental model when working with low-level ops and high-level data-sciency pipelines. I find it nice in Mojo to implement things like performant IO and parsing, statistics, and interactive visualization (currently, using Python interop) all in one language, same set of tooling .. etc.
Coming from Python, Mojo is for me all about performance as possibility without completely leaving familiar territory. Mojo as superset of Python seems for me not to be around the corner right now, yet many reasons to be optimistic about it:mojo:
Go has nice geospatial libs) and two-language problem is Julia’s trademark 😄
Yeah, I also like Julia. Best syntax out there IMHO.
But in my day-to-day: all the ML libs I need to use are in Python, the geo libs are in Python, and the company I work for uses Python, so hard to shift all of those things.
I'm planning to use it for game development, starting with basic non-graphical simulations that would be linked to Unreal Engine for rendering.
I’d like to use Mojo because i’m familiar with python’s approach, and writing things quickly in python is easy, but I don’t feel python is often scalable or sustainable for more long lived software
I'm hopeful (down the line) about getting some of Rust's safety and typing guarantees without having to be keeping track of memory management concepts that are extraneous to business logic (as Rust's borrow checker model often seems to be). What I'm hoping for is a Python I Can Trust.
I've always dreamed of a language like this. I really love Python; I hate being forced to use another language when performance is important.
I want to get into GPU programming and currently reading the "Programming Massively Parallel Processors" which mainly uses CUDA C++ for teaching the parallel programming principles. I want to see if I can do the same programs using Mojo. Would love to know if there are any resources available for this.
Congrats @Toji, you just advanced to level 5!
Because it feels like the next step from using python. I love the performance but I think the strong typing with python syntax is the biggest part for me. I always use types in my code and python like code being compiled to native binaries is another major plus.
It also makes me feel like I’ve moved from the script kiddy (not to say python isn’t an absolutely amazing language) to big boy world if you get what I mean
Yeah, using Mojo will make you feel like KFC bucket
1) In my field, we have a three language problem. Python, Fortran and C++. Connecting different tools is a distance dream. So having a unified language that can connect tools and interoperability is great! I’m also working on a library currently using mojo.
2) the syntax is good, familiar and the types are great and makes it easy to learn ( makes me feel secure about my code lol, it’s awkward to go back to non typed python code after working on mojo).
3) since it’s in early stages, I feel that it’s more easy to learn the fundamentals of the language. And since I have started mojo, I’ve fallen into the rabbit hole of learning more about how memory, accelerators and stuff works in general, which is great, little more knowledgable every day xD
Prototyping a bit of algorithmic trading strategies (and learning the basics of Mojo while going along)
I can definitely agree that because I came so early and have seen all the changes in real time that the harder to grasp concepts seem far more natural