Gleam Language Now Hosted on Tangled – What It Means for Developers

Gleam Language Now Hosted on Tangled – What It Means for Developers

Gleam is now available on Tangled, the decentralized Git forge

TL;DR: Gleam’s source code has been mirrored to Tangled, a federated Git hosting service, giving the language a new home for open‑source collaboration—but users report a rough onboarding experience and missing features.

Why hosting Gleam on Tangled matters

  • Decentralization: Tangled provides a federated alternative to GitHub, GitLab, and Codeberg, aiming to reduce reliance on corporate‑owned code hosts.
  • Community visibility: By placing the official Gleam repository on Tangled, the language gains exposure to developers interested in self‑hosted or federated workflows.
  • Potential for integrated CI/CD: Tangled’s infrastructure (built on NixOS) promises reproducible builds, which aligns with Gleam’s emphasis on type‑safety and reliability.

What the Tangled repository contains

The Tangled mirror mirrors the main branch of the official Gleam repo:

  • ~11 k commits across core components such as compiler-cli, compiler-core, compiler-wasm, and the language server.
  • Recent activity (last 2 weeks) includes performance‑focused commits like faster formatters, improved JavaScript code generation, and new lints added to the built‑in "clippy" tool.
  • Documentation and tooling (e.g., README.md, CHANGELOG.md, RELEASE.md) are all present, making the repo a full‑featured source of truth for the language.

Early user feedback – onboarding friction

Several commenters on Hacker News highlighted practical obstacles when first accessing Tangled:

"First hearing of Tangled, tried signing up and this first‑time user experience needs to be tightened up. … they ask for an email, send you an email, ask for a username, but you can’t actually log in with this username directly…" – pbjerkeseth

"I created a repo but can’t look at it because I get a 404. The login was quite painful; I needed several attempts to enter my atproto handle…" – LukaD

"I tried Tangled and ran my own Knot, but never saw updates to the repo on Tangled itself. IPv6 worked only after enabling a lot of IPv4 NAT and creating a dummy A record." – sc68cal

These reports suggest that Tangled’s authentication flow, UI consistency, and network configuration are still maturing. For developers accustomed to the seamless experience of mainstream platforms, the friction may be a barrier to adoption.

How Tangled’s CI/CD works (and what’s missing)

One commenter pointed to Tangled’s CI implementation:

"If you too are wondering their CI story, it is based on NixOS: https://blog.tangled.org/ci/ …" – esafak

Tangled leverages NixOS to provide deterministic builds, which could be a strong fit for Gleam’s compile‑time guarantees. However, no concrete CI pipelines for Gleam projects are documented in the repository, and users asked:

"How are folks doing CI on Tangled?" – vvern

Until official CI templates or GitHub‑style Actions are offered, teams will need to craft custom Nix expressions or rely on external runners.

Community perception of the partnership

The announcement sparked a mix of curiosity and skepticism:

  • Positive curiosity – Some users expressed excitement about a new decentralized git provider: "I’ve been looking for a decentralized git provider for a while" – propstober.
  • Skepticism about the platform choice – Others questioned why the Gleam team chose a VC‑backed forge over community‑run services like Codeberg: "I’d love to hear why they chose a VC funded forge over e.g. Codeberg" – lavela.
  • Confusion about the headline – Several commenters admitted they were unfamiliar with both projects, calling the headline “satirical” or “bubble‑ass”: "I have no idea what Gleam or Tangled is" – hnarn.

These reactions underline the need for clearer communication about what Tangled offers and why it aligns with Gleam’s philosophy of building "friendly, type‑safe, scalable systems."

What developers should watch for next

  1. Improved onboarding – Expect Tangled to refine its sign‑up flow, unify branding across auth pages, and fix 404 errors for newly created repositories.
  2. Official CI templates – Look for Nix‑based CI examples in the Gleam repo or in Tangled’s documentation to streamline automated testing and releases.
  3. Community tooling – As the mirror gains traction, community‑contributed actions, Git hooks, or integration scripts may appear, reducing the current manual setup burden.
  4. Performance updates – Recent commits show active development on the compiler and formatter, indicating that the Gleam project remains vibrant despite the new hosting location.

Bottom line

Hosting Gleam on Tangled marks a step toward decentralized code collaboration for a language that already emphasizes safety and scalability. While the move brings strategic benefits, early adopters must navigate a still‑evolving user experience and limited CI support. As Tangled matures, it could become a compelling alternative for Gleam developers seeking a federated, reproducible workflow.

Sources