Mojo: The usability of Python with the performance of C
docs.modular.com
docs.modular.com
> 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.
Devs: “The server is down…”
Nowadays easily replicatable with cloud development, Web IDEs and shells.
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.
https://docs.modular.com/mojo/faq.html#will-mojo-be-open-sou...
Open source would have been ideal, but when people ask for open source it's mostly them asking for free. We know that most developers don't truly care about open source beyond the surface level given how popular VSCode is.
If you want to make money and pay rent, Open Source has shown to be disastrous for almost all business models.
For a language, I think opennness and standards are so important because the usage is broad. The licensing aspects are also important, but I’m even hesitant to use open source languages that are largely run by a single org (eg, Go).
Some of the performance gains look absolutely ludicrous.
I think this relates to GPI programming however where of course the speedup for highly parallel operations will be prefers of magnitude. But that’s not about the language per se.
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.
But can't they just open source it and not accept PRs?
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.
Additionally I've consulted on a couple of large Python that were a mess, but on closer inspection, the team was doomed to fail no matter what tool they used, and honestly I think Python just helped them get further than they otherwise would have. :)
An FAQ entry on how it's faster than C would be appreciated.
God forbid in this era of corporate assimilation any rogue geeks do something unprofessional!
We should strive to make the world more accessible, not less. We can’t even discuss the extension on HN without spelling it out in different ways.
Decisions like that make me very wary about the quality of other decisions made in the language.
That’s my attempt at making the connection.
It also just seems like a fun thing kids do. I don’t even know how to enter an emoji as a file extension so it could be a way to filter out oldsters who don’t know the new ways.
Like it's meant to be represented as mojo[fire emoji]...