Home

Language

Pattern Matching Exhaustive match with guards and destructuring. Type System Inference, unions, null safety, Result types. Generics Monomorphized generics with trait bounds. Traits Shared behaviour without inheritance. Error Handling Errors as values, propagated with try.

Systems

Memory Model Ownership and borrowing, no collector. Comptime Run real code during compilation. Concurrency Async, await, channels and tasks. FFI Call C without a binding generator.

Toolchain

TypeScript Compiler home tsc checks and emits TypeScript. Macros Hygienic macros over the real AST. Editor & CLI Tooling LSP, formatter, test runner, package manager.
Every language, codegen and tooling row, with status. Capability matrix

Build with Home

Systems Programming Native binaries with predictable latency. Game Development Frame budgets without collector pauses. Operating Systems Freestanding builds, no runtime required.

Ship with the toolchain

Web Services HTTP servers and databases in one binary. CLI Tools Single-file distribution, fast start. TypeScript Migration Type-check today, move code when ready.
Guide
Standard LibraryArchitectureCompiler PipelineConfigurationDX CommandsPackage Management
Capability MatrixTypeScriptNode.jsBunRoadmap

Pantry Integration

Copy page
Copy page as Markdown for LLMs
View as Markdown
View this page as plain text
Open in ChatGPT
Copy content and open ChatGPT
Open in Claude
Copy content and open Claude
Open in Perplexity
Search with Perplexity AI
On this page 8

Overview

Home uses Pantryfor system-level package management. Pantry is keptseparate from the Home language itself to maintain clean separation of concerns.

Files

  • pantry.json - Declares Home's system dependencies (e.g., Zig compiler)
  • pantry-lock.json - Lockfile for reproducible builds

Usage

System Packages

Use pantry directly (not through Home):

pantry install nodejs.org
pantry list
pantry search python
pantry update

Shell Integration

Pantry integrates with your shell for automatic environment activation on cd:

# Handled by pantry's zshrc integration
cd ~/Code/my-project  # Automatically activates environment

Why Separate

Home is a programming language, not a system management tool.

Pantry is a system package manager, handling:

  • System dependencies (Node.js, Python, etc.)
  • Development environments
  • Shell integration for cd hooks

Keeping them separate means:

  • ✅ Home stays focused as a language compiler/interpreter
  • ✅ Pantry handles system concerns independently
  • ✅ No bloat in the language tooling
  • ✅ Clean architecture for home-os future

For Home Development

The Pantry lockfile pins what Home itself needs to build: Zig 0.17 dev, installed through Pantry.

For Home-OS

When building the OS, this separation becomes even more important - the OS will have its own package management layer, and Home remains just the programming language.

Edit this page on GitHub

Released under the MIT License.

Copyright © 2026 Home Programming Language