---
title: "Why Hem"
description: "Background on the decisions behind the language: readable output, the toolchain boundary, and the optional Effect extension."
image: "https://hem.run/social/hem.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://hem.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Hem

These pages explain the design decisions behind Hem: why the language works the way it does, the trade-offs involved, and which alternatives were rejected. You do not need to read these pages to use Hem.

[Why Hem emits readable TypeScript](/explanation/why-hem) explains ordinary emitted values, explicit library imports, checked TypeScript types, and sibling output.

[How Hem fits your toolchain](/explanation/architecture) covers compiler and editor tooling, generated files, and explicit runtime dependencies.

[Why Effect, and why Effect in Hem](/explanation/why-effect-why-hem) compares plain TypeScript, standard Effect, and Hem using a realistic service example. It covers the advantages of Effect, the patterns Hem simplifies, the compiler's safety checks, and the Effect APIs that remain explicit.

Source: https://hem.run/explanation/index.mdx