Urgent.News

What's breaking now, across thousands of outlets.

Tech

Modular's Mojo programming language hits 1.0 milestone

Developers await open source compiler release to dispel uncertainty following Qualcomm acquisition

Modular's Mojo programming language hits 1.0 milestone

Modular s Mojo attained its 1.0 milestone on Tuesday, marking a stable and production-ready general-purpose programming language. The language's main objective is to unify the AI software stack, enabling developers to target diverse GPUs, CPUs, ASICs, and other systems that run AI workloads. In collaboration with MAX inference framework, Mojo aims to simplify AI software, systems, and tool development, without relying on vendor-specific platforms such as Nvidia's CUDA or AMD's ROCm.

CUDA, Nvidia's proprietary GPU programming platform, is often preferred by AI-oriented tech companies seeking an open-source alternative for optimization on their specific hardware. Chris Lattner, known for creating LLVM, Clang, Swift, and MLIR, has been developing Mojo since 2023 through his startup Modular, which was acquired by Qualcomm in June.

Mojo strives to combine the accessibility of Python with Rust-like memory safety and system programming capabilities, often found in languages like C, C++, and CUDA. The 1.0 release introduces new features like Python-style lambda syntax, an improved Language Server Protocol for code editors, and Mojo AI skills. The language's standard library is under the Apache License v2.0 with LLVM Exceptions.

Modular plans to open-source the compiler this year, with the language website hinting at a potential release at Modcon next week. During a streamed Q&A session, Lattner addressed concerns about Qualcomm's acquisition of Modular, stating that Nvidia and AMD remain strong open-source contributors, and he doesn't anticipate any issues with the platform's vendor-neutrality.

Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at theregister.com →

More in Tech

I Wanted Kubernetes Without an Always On EKS Bill

I wanted a Kubernetes lab that would still be there the next morning. A temporary cluster on my laptop would be useful for testing manifests, but it would disappear when I closed the lid.

  • Reporter sought always-on Kubernetes lab for testing.
  • Intel N100 server with Debian and Docker containers used as host.
  • k3s chosen for single-node cluster due to resource compatibility.

More from Tuesday 11 August →