CLI Language Coverage Analysis

Select a language, toggle distribution channels, compare coverage across OS/hardware.
All percentages are absolute (share of total developers). Binary and curl|sh excluded.

Results

Channel cells may overlap — a single user can have both npm and Homebrew. The "Best" column shows de-duplicated coverage for the highest-scoring selected language. Disabled channels are crossed out.

Filled = reachable

Unreachable (binary fallback only)

Data Stack Overflow Developer Survey 2024 (Win 62%, macOS 31%, Linux ~27% multi-select; normalized to primary OS, split by ARM/x64). 2025 survey not yet published at time of creation — check SO 2025 for updates.
winget: built into Win 11, available via App Installer on Win 10 — est. 75% of Windows devs.
Binary/curl|sh excluded — universal fallbacks that inflate all languages to ~95%+.

Model Coverage = Σ(OS_share × union(enabled_channel_penetrations)). Union uses pairwise overlap coefficients (e.g., 80% of macOS npm users also have Homebrew). Disabling a channel removes it from the calculation; the gray bar in Coverage tab shows potential gain from re-enabling.

Not shown C#/.NET (NativeAOT) is an emerging CLI option with native winget/brew support, but lacks ecosystem adoption. bun build --compile / deno compile give TypeScript standalone binary capability (40-90MB) — not reflected in coverage.