Context
Today's install path is:
git clone https://github.com/home-lang/home.git
cd home
pantry install # pulls zig 0.16-dev
zig buildThat's reasonable for the stacksjs / pantry crowd, but anyone discovering Home from outside has to:
- Know what pantry is
- Install pantry first
- Wait for a from-source build
- Pin themselves to whatever Zig dev version we happen to need
For comparison, getting started with Bun, Rust, Deno, or Zig itself is a single shell line. The curl-pipe-sh installer is industry standard for new languages.
Proposal
- Set up release builds in CI that produce static
homebinaries for:aarch64-macos,x86_64-macosaarch64-linux,x86_64-linux(musl-static)x86_64-windows(zip with .exe)
- Publish them as GitHub Release assets, named
home-<version>-<target>.tar.gz(predictable URLs) - Write an installer script at
https://home-lang.org/install.sh(or a similar canonical URL) that:- Detects platform
- Downloads the right tarball from the latest release
- Verifies a checksum (published alongside the tarballs)
- Extracts to
~/.home/bin(or~/.local/bin) - Prints PATH instructions
- Update README to lead with
curl -fsSL https://home-lang.org/install.sh | bash - Bonus: Homebrew tap (
home-lang/tap/home) for Mac users who'd rather not pipe curl into bash
Open questions
- Where does the install script live? Own repo, or in this one under
/install.sh? - Domain:
home-lang.org? (placeholder above) - We're currently pinned to "Zig 0.16-dev." Releases should ship a static
homebinary so end users don't need any Zig install at all.
Why this matters
- Removes the largest install-friction wall for outside contributors
- Makes the "try Home" experience comparable to peer languages
- Required for any tutorial / blog post we'd want to write or share