Mojo: The usability of Python with the performance of C
> The Mojo standard library, compiler, and runtime are not available for local development yet, so we created a hosted development environment where you can try it out. We call it the Mojo Playground! To provide the best experience possible, the Mojo Playground currently supports a limited number of people.
> Sign up for access to the Mojo Playground. When you receive access, log in to the Mojo Playground using the email address you provided in the above form.
A programming language as a service. Exactly what we all needed.
There are a few key properties of Python that make it a really great language to develop in, especially at the start of a project: no need to figure out type annotations up front, high signal-to-noise syntax, and Python's absurdly dynamic nature. These all work together to speed development, especially the early stages where you're modelling the program's design.
As the program gels, then it becomes a much better time to nail down precise data types and then 99% of Python programs no longer need an extreme level of dynamicity (dynamicness?). So far, Mojo seems to be getting this right: stay out of my way when I'm roughing things in and rapidly iterating, and then if and when it's needed, I'll happily lock in data types in exchange for more speed, AOT compilation, getting onto a GPU or microcontroller, etc.
Closed source. Not interested.
Repost from 2 days ago:
Very excited to see how this comes along! Hopefully we have a JS->TS style jump here!
Some of the performance gains look absolutely ludicrous.
Love the idea, but it seems right now very much tied to their platform.
If I can't install it and run it on my machine, including in prod, it's a hard sell.
But given the tone of their articles, they seem passionate about it, and genuine, so I want to believe Mojo will be released as a FOSS project in the future and they will make money with the service itself.
This looks absolutely amazing. The team building this is A+++ as well
You mention coming into this from the ML world, but any mention of timelines to leveraging Python's ML ecosystem seem absent. Any idea what's in the works in that regard?
"Superset of Python with added features for systems-level code" sounds exactly like Cython. Strange that Cython isn't ever mentioned in any of the comparisons.
Now that's a decent title for a post.
"We believe a tight-knit group of engineers with a common vision can move faster than a community effort. "
But can't they just open source it and not accept PRs?
Python is hardly usable for big projects.
The closest I get to this is hot-deploying a C dynamic lib compiled with debug on a core C++ engine compiled with release.
That way I get stacktraces from "the moving code" I can read remotely without losing performance (move the heavy parts into the core engine).
The engine needs to be extremely stable for this to work though.
undefined
The fire emoji as file extension is odd, complicated, and unprofessional. That's my main take away. (I know .mojo is also supported but it seems you're pushing .[fire emoji] as default.)
An FAQ entry on how it's faster than C would be appreciated.