Install unisonlang with Homebrew

Project links

• Homepage
• Repository

Commands and aliases

• ucm

Project history

Unison Computing traces the language's path from a 2018 company founding through a 2019 first alpha, SQLite-backed local codebases in 2021, Unison Share, projects, contributions, cloud deployment, and finally the 1.0 release in November 2025. The 1.0 announcement presents the milestone as stabilization of the language, distributed runtime, and developer workflow after several years of design and engineering.

The language's defining idea is that definitions are identified by hashes of their syntax trees rather than by names alone. Official docs describe Unison code as content-addressed and stored in a codebase database; names are metadata, while hashes pin exact implementations and dependencies.

Adoption history

Unison's adoption has been centered less on broad language popularity and more on a self-contained ecosystem: UCM, Unison Share, Unison Cloud, a public package/project system, and a community of early adopters. The 1.0 page reports thousands of merged PRs, thousands of GitHub stars, many published definitions, and more than a thousand project authors.

The project has also used the language in its own infrastructure. An official production report describes Unison Computing using Unison for mission-critical parts of Unison Cloud, including compute fabric and transactional storage work.

How it is used

Package users install unisonlang primarily to get the ucm executable. The everyday workflow is unusual for language packages: users edit scratch .u files in their editor, then use UCM to add, update, view, test, run, branch, push, pull, and manage code in the local codebase.

Because code is not organized as ordinary source files in the final representation, package nerds care about where the CLI lives, how the codebase is initialized or upgraded, and how UCM interoperates with Unison Share, project metadata, editor tooling, and cloud workflows.

Why package nerds care

Unison is a packaging outlier: it is a language runtime, buildless code database, package manager, version-control model, and deployment story wrapped around one CLI. That makes the Homebrew formula more than a compiler install; it is the entry point to a non-file-centric development workflow.

It is also a useful case study for language packaging after Git. Instead of treating Git repositories as the primary distribution unit, Unison moves toward hash-addressed definitions, native projects, Share-hosted libraries, and semantic code operations.

Timeline

• 2018: Unison Computing founded.
• 2019: First official alpha release and Strange Loop introduction.
• 2021: Local codebases moved to SQLite; Unison Share first deployed.
• 2023: Projects and Share contributions added.
• 2024: Unison Cloud became generally available; Unison Share was open-sourced.
• 2025: UCM Desktop, MCP support, branch history comments, and Unison 1.0 release.

Related projects

• The official FAQ frames Unison as related to Haskell through functional programming, type inference, pattern matching, algebraic data types, and purity, while differing through strict evaluation, abilities, content-addressed code, and its codebase workflow.
• Its ecosystem includes Unison Share for code hosting, Unison Cloud for deployment, UCM Desktop for local browsing, editor/LSP tooling, and Unison projects as the package-like unit for libraries and applications.

Sources

• https://www.unison-lang.org/blog/experience-report-unison-in-production/
• https://www.unison-lang.org/docs/projects/
• https://www.unison-lang.org/docs/the-big-idea/
• https://www.unison-lang.org/unison-1-0/
• source_facts.package-manager