Talk:Mojo (programming language)

Wiki Education assignment: Digital Writing

This article was the subject of a Wiki Education Foundation-supported course assignment, between 21 August 2023 and 8 December 2023. Further details are available on the course page. Student editor(s): KoJa23 (article contribs). Peer reviewers: Applejuicelover444.

— Assignment last updated by OsseusIgni (talk) 13:54, 31 October 2023 (UTC)

Does this article need to be rewritten?

@Siroxo: Why does the article have these cleanup tags? Jarble (talk) 18:56, 19 November 2023 (UTC)

Hi there. I had been trying to help maintain this article, but it kept (and apparently keeps) drifting more towards a PR focus on what the product will one day do and buzzwords / marketing pushed by the developers, often citing the developers themselves, churnalism, or various unreliable primary sources. I couldn't really keep up with the additions without resorting to frequent reverting, which I didn't want to do, so I tagged it. I didn't want to overload tags so I settled on 2.

Worries remain today. Here's a quick problem I found, though I'm sure there are more: The Mojo programming language aims to be fully compatible with the Project Jupyter ecosystem. It plans to add a borrow checker, an influence from Rust, and to add integration to transparently import Clang C/C++ modules and transparently generate a foreign function interface between C/C++ and Mojo.. Adding marketing like this is certainly UNDUE/non-NPOV unless multiple fully independent (like WP:ORGIND sources) are reporting it.

Given the way it's developing, it's likely this article should be in draft space, but the AfD resulted in keep.

—siroχo 23:25, 19 November 2023 (UTC)

Reviving this old thread because the concerns Siroxo raised are what I've been working through with recent edits. Disclosure first: I work for Modular and have noted this on my user page per WP:PAID; recent edit summaries carry it too.

Over the past few hours I've tried to clean up the promotional and stale language and add better external sourcing. Both code examples had not compiled for over two years (the let keyword was removed from the language in early 2024); they're replaced with examples verified against the current release. The "plans to add a borrow checker" / "intends to add a foreign function interface" style of claim quoted above is rewritten to describe only what has shipped, with citations. A YouTube-comment ref, an X/Twitter ref, and a pricing-page ref are gone. Where independent coverage exists I've used it in place of, or alongside, Modular's own docs: InfoQ, InfoWorld, heise, and a 2025 Oak Ridge National Laboratory benchmark, negative findings included.

I've left the {{Primary sources}} and {{Promotional}} tags alone on purpose. Whether the article has improved enough is for editors without my conflict to judge. If anything I've touched reads as promotional or under-sourced, please revert or flag it and I'll supply sources or stay out of the way. There are two larger additions (a Reception section draft, and restructuring the examples per-feature like Rust (programming language)) that I'd rather propose here than add directly; I'll post those separately when I have free time. Whatwouldsea (talk) 18:46, 12 June 2026 (UTC)

License

Article lists the license as Apache 2.0, but this appears to be inaccurate. The "free forever Community Edition" uses what looks like a custom license, and there are additional terms for the other, paid tiers.

https://www.modular.com/pricing ~2026-10341-82 (talk) 18:16, 15 February 2026 (UTC)

You're right, only the standard library has been released under an open source license (as is cited in the article Modular has promised to release the rest of the language under an open source license in 2026; we'll see). Updated the infobox for what's currently accurate. Mike Linksvayer (talk) 18:57, 15 February 2026 (UTC)