Show HN: Gitdot – A better GitHub. Open-source, written in Rust

Original Article ↗ Hacker News Discussion ↗

A new open-source Git hosting platform, Gitdot, positions itself as a minimalist, Rust-based alternative to GitHub, drawing interest for its clean, fast, CLI-inspired web interface and plans for features like stacked diffs and simple issue tracking. Commenters welcome more competition in the forge space but question marketing claims such as being “better than GitHub,” “anti‑AI,” and “built in Rust” as differentiators, especially given missing essentials like mobile support, SSH, mature documentation, and a clear long-term business model. The project also prompts broader debate about AI-assisted “vibe-coded” software, accessibility and UX trade-offs, and whether new forges should improve existing tools like Forgejo or SourceHut rather than starting from scratch.

Overall Reception

  • Many are excited to see a new open-source forge, appreciate the minimalist aesthetic, and like that it’s self-hostable in principle.
  • Others see it as very early-stage, “cardboard rocket vs SpaceX,” and think “better than GitHub” is premature given missing core features.

UI / UX & Design

  • Minimal, terminal-inspired UI gets a lot of praise for being clean, focused, and fast-feeling.
  • Several find it confusing: tiny fonts, low affordance on inputs/buttons, unclear navigation back to home, and hover-to-preview behavior seen as distracting and inaccessible (later changed).
  • Some suggest not “innovating everywhere” at once; better to lean on standard patterns and accessibility (larger fonts, clear controls, mobile layout).

AI & “Anti‑AI” Messaging

  • FAQ originally emphasized “no AI,” “anti‑AI,” and no copilot or training/selling user data.
  • Commenters point out the repo contains extensive use of Claude/agents to generate code and design.
  • This is viewed by some as hypocritical or disingenuous marketing; others distinguish “no AI product features” from “using AI as a dev tool.” Wording was later toned down.

Tech Stack: Rust, React, Vibes

  • “Written in Rust” as a headline differentiator draws heavy skepticism; many say the language choice is irrelevant to users and feels like marketing.
  • Others argue language does signal culture (performance, safety, static binaries) and can matter to contributors.
  • Some criticize using React/SPAs and modern styling while claiming minimalism; others say they care more about behavior than stack.
  • Accusations of “vibe-coded”/LLM-slop vs defenders who see AI-assisted coding as compatible with “no AI features” for end users.

Features, Workflow, and Self‑Hosting

  • Lacks many GitHub staples: issues, PRs, CI, SSH support, mobile UI, full docs for self-hosting.
  • There is a basic CLI and plans for stacked diffs, Nix-based CI, simple bug tracker, and richer code review.
  • Some see it closer to a Gitea/Forgejo alternative than a GitHub replacement yet.

Performance & Mobile

  • Many report very fast navigation; others hit slow file loads and jitter, possibly from HN traffic and NFS-backed storage.
  • No mobile support is a major complaint; some want at least a degraded desktop view or a clear “no mobile yet” message.

Naming, Trademark, and Business Model

  • Use of “gitdot” is flagged as potentially violating Git’s trademark policy on portmanteaus; project owners acknowledge not doing full due diligence and may rebrand if needed.
  • “We don’t make money; pre-seed + personal runway” worries users who want a clear long-term monetization plan and fear future “enshittification.”
  • Suggestions include charging directly and fairly for private repos, possibly self-hosted or encrypted options, rather than chasing free tiers.