Skip to content

21 languages · 466 libraries · 2004+ examples

Know what to reach for, and why

Not another API reference. Guides to what each language and library is actually for — where it fits, what it competes with, and the trade-offs you usually discover six months in.

How it works

The same structure on every page

So you always know where to look, whichever language or library you land on.

01

Honest trade-offs

Each language guide states what it is genuinely good at and genuinely bad at — the GIL, Java's startup cost, Rust's learning curve. Choosing well means knowing the price.

02

When to use, when not to

Library pages answer the real question. Concrete situations where it fits, situations where it does not, and the alternatives worth weighing against it.

03

Code that shows the idiom

Annotated examples of how the language is actually written, plus the pitfalls that catch everyone — mutable defaults, N+1 queries, dangling references.

Guides

Languages

History, key facts, strengths, trade-offs, idiomatic code, a learning path, and the mistakes everyone makes.

About

Common questions

What is this site for?

Documentation tells you how a library works once you have already chosen it. This site is for the step before that: understanding what a language or library is actually for, what it competes with, and whether it fits your problem. Every page is written to be read start to finish, not searched for one API call.

How is this different from the official docs?

Official docs are authoritative and rarely comparative — they cannot tell you to use something else. Each library page here adds a plain summary, concrete situations where the library is the right call, situations where it is not, and named alternatives with the reason they differ. Then it links you to the official documentation for the details.

Is the content free?

Yes, all of it, with no account required. The site is supported by advertising.

How current is this?

Language guides cover releases through 2025 and note where a feature is recent enough that older tutorials will disagree. Library entries describe stable, widely-used versions. Where a library's API changed significantly between major versions, the page says so — that is usually the thing that costs people an afternoon.