231–236 of 236 posts
Earlier quoted context omitted.
So, without significant indentation?
2026 and still talking about python indentation? what's next, `goto` gripes?
I feel like this language would really benefit from some sort of 1-pager overview. I just spent a fair bit of time on the official site, and I still don't think I have a very good grasp of what problem this language aims to solve, or why I would select it over other similar languages
You'd likely enjoy: https://mojolang.org/nightly/docs/vision/ for why we created it, and there's https://mojolang.org/nightly/docs/faq/ as well :) Feedback welcome as always and thanks for checking it out! Encourage you to watch ModCon next week for some exciting announcements :)
Ok, yes, this is a substantially better entry point to the language than anything I found by clicking around - maybe link it prominently from the main page?
What's wrong with people?
> Finally, we will continue to progressively open-source more of the Mojo language, as well as components in MAX that we have built with it. Our commitment remains unchanged – we will open source the Mojo compiler and toolchain in 2026. Why not now though? Why wait for 4 more months? What magic is there to hide in just making it source available at least.
It's probably very messy and not a great baseline for outside contributors to start create PRs. That's the favorable interpretation, atleast.
I made a language design some years ago. More recently, I had Claude carry out some of the implementation to see if it would work. It did not. I tried again, hand-tailoring the IRs and many of the main algorithms, and it did better but the self-hosting compiler still violates many of the design principles and even behaviors in the design document. I have spent six months of free time reviewing and fixing it myself, and it's just a small pet project. I would not open-source that code any time soon.
I must imagine Mojo is in the same situation.
Earlier quoted context omitted.
Part of that is because there isn’t yet a package format and a central repository. I have a few libraries I would like to contribute or merge with similar projects.
For sure, those things would go a distance towards making it a more competitive language. Why haven't they happened yet though...? Nim is not a young language. Leadership [Andreas] doesn't think they are more important than spending time adding another memory management option.
There has never been much prog.lang. benefit from being "in the stdlib/core" in Nim (unlike Python or Go, say). The benefit is more "software distribution" for the dependency allergic, but the Nim culture is much less micro-deps than seems in vogue lately. All that said, I think having a more batteries core distribution is valuable - just less than you might guess - and practically that needs delegation.
Earlier quoted context omitted.
You'd likely enjoy: https://mojolang.org/nightly/docs/vision/ for why we created it, and there's https://mojolang.org/nightly/docs/faq/ as well :) Feedback welcome as always and thanks for checking it out! Encourage you to watch ModCon next week for some exciting announcements :)
> You'd likely enjoy: https://mojolang.org/nightly/docs/vision/ for why we created it, Ok, yes, this is a substantially better entry point to the language than anything I found by clicking around - maybe link it prominently from the main page?
"Why Mojo?" is now smack bang on the homepage!