Sample Launch Kits

hyperfine v2.0.0

Here's how we'd launch hyperfine v2.0.0.

Unofficial sample: not written, reviewed, or endorsed by the hyperfine maintainers. Not affiliated. Based only on the public README and release notes: https://github.com/sharkdp/hyperfine · release notes. Drafts below are written as suggestions for the maintainers; Dev Hype has not posted any of them.

Positioning brief

For: developers who benchmark CLI tools, builds, and scripts.
Problem: one-off time runs are noisy; caches and shell overhead skew results.
Hook: hyperfine 2.0 measures more than time — peak memory and hardware counters, out of the box.
Proof: statistical analysis over many runs, warmup/prepare commands, outlier detection, parameter scans, exports to CSV/JSON/Markdown/AsciiDoc (README). v2.0.0: --metrics, --env, direct execution by default, JSON schema v2 (release notes).

X thread (draft for the maintainers to post)

1/ hyperfine 2.0 is out. The command-line benchmarking tool now shows wall-clock time AND peak memory by default — and can track instructions, CPU cycles, cache misses, and branch misses too. 🧵 2/ Pick what you measure with the new --metrics option. The terminal output gives an overview of every metric you select. 3/ New --env: set env vars per benchmark without a shell. hyperfine -P threads 1 8 --env 'OMP_NUM_THREADS={threads}' 'my_command' 4/ Commands now run directly by default (--shell=none) — no shell startup overhead to correct for. Need pipes or globs? Add -S. 5/ Heads up: JSON export moved to schema v2 with metadata, per-run measurements, and summaries for every metric. results[i].mean → results[i].summary.time_wall_clock.mean. 6/ Still everything you rely on: warmups, cache-clearing prepare commands, outlier detection, parameter scans, CSV/JSON/Markdown export. Release notes + migration: github.com/sharkdp/hyperfine/releases/tag/v2.0.0

Follow-ups (5)

Compare two git branches without timing the checkout: hyperfine --parameter-list branch main,perf --setup 'git switch {branch}' 'python main.py'
Cold-cache vs warm-cache: --warmup 3 for warm, --prepare to drop caches before each run. Same tool, honest numbers.
Migrating to 2.0? Three things: -S for shell syntax, setup/prepare/conclude/cleanup still run in a shell, JSON is schema v2.
hyperfine -L compiler g++,clang++ '{compiler} -O2 main.cpp' — non-numeric parameter lists in one line.
What metric are you adding to your benchmarks now that peak memory is on by default? Reply with your favorite hyperfine flag.

Product Hunt

Name: hyperfine 2.0
Tagline (≤60): Command-line benchmarking: time, memory and HW counters
Description: hyperfine benchmarks any command with statistical analysis across many runs. Version 2.0 adds peak memory by default, selectable metrics (instructions, CPU cycles, cache and branch misses), --env for per-run variables, and direct execution without a shell. Warmups, cache-clearing, outlier detection, parameter scans, and CSV/JSON/Markdown export included. Cross-platform.
First comment: Suggested maker comment, to be written by the maintainers in their own words: explain that hyperfine was made to answer "which command is faster?" with statistics rather than a single time run; summarize 2.0 (peak memory shown by default, hardware counters via --metrics, no intermediate shell by default with -S to restore it, JSON export with per-run measurements for every metric); point script authors to the migration notes; ask which metrics matter most in their workflow.

Show HN (Show HN posts must come from the maker)

Title: Show HN: Hyperfine 2.0 – CLI benchmarking with memory and hardware counters Text: Hyperfine is a command-line benchmarking tool. You give it commands; it runs each many times, does statistical analysis, detects outliers, and can compare them. 2.0 adds alternative metrics: peak memory is shown by default, and --metrics selects instructions, CPU cycles, cache misses, branch misses. Commands now run without an intermediate shell by default, which removes the shell-overhead correction for fast commands (-S restores the old behavior). --env sets variables per run, and the JSON export is a new schema with per-run data for all metrics — a breaking change for scripts. Feedback on the new defaults welcome.

r/rust — "hyperfine 2.0: benchmark CLI commands with peak memory and hardware counters" — angle: Rust-built tool, focus on --metrics and direct exec rationale; link to the issue explaining the shell change.
r/commandline — "hyperfine 2.0 released — --metrics, --env, no shell by default" — angle: practical one-liners (branch compare, -L lists, warmup vs prepare).
r/programming — "Benchmarking beyond wall-clock: hyperfine 2.0" — angle: why measuring memory/instructions alongside time gives a fuller picture; link to release notes. Each post body would follow: what changed → 2 commands → breaking changes → link → maker disclosure.

Release notes (condensed)

hyperfine 2.0.0 — measure more than time. - Added: --metrics (peak memory, instructions, CPU cycles, cache/branch misses); peak memory shown by default; --env; plotting/analysis scripts support metrics. - Breaking: direct execution by default (--shell=none; use -S); setup/prepare/conclude/cleanup always run in a shell; JSON export schema v2.

7-day schedule

Day	Platform	Asset
1 Tue	X thread 9am PT; Show HN 8am PT	launch
2 Wed	Product Hunt 12:01am PT; X follow-up 1
3 Thu	r/rust; X follow-up 2
4 Fri	X follow-up 3 (migration)
5 Sat	r/commandline
6 Sun	X follow-up 4
7 Mon	r/programming; X follow-up 5 (ask)	recap
Daily: 2×30 min reply windows.

↑ Back to sample list

uv 0.13.1

Here's how we'd launch uv 0.13.1.

Unofficial sample: not written, reviewed, or endorsed by the uv maintainers. Not affiliated. Based only on the public README and release notes: https://github.com/astral-sh/uv · release notes. Drafts below are written as suggestions for the maintainers; Dev Hype has not posted any of them.

Positioning brief

For: Python devs juggling pip, pip-tools, pipx, poetry, pyenv, virtualenv; vibe coders running one-off scripts.
Problem: too many tools, slow installs.
Hook: one Rust-built tool for Python packages, projects, scripts, tools and Python versions.
Proof (README): "10-100x faster than pip" (links BENCHMARKS.md); universal lockfile; inline script metadata; workspaces; global cache; macOS/Linux/Windows; installs via curl or pip. 0.13.1: smaller binary, faster Simple API parsing, CPython 3.16.0a1, Linux SPARC, safer uninstalls.

X thread (draft for the maintainers to post)

1/ uv 0.13.1 just shipped: smaller binary, faster Simple API parsing, and CPython 3.16.0a1 available. If you haven't tried uv yet, here's the short version 🧵 2/ uv is one tool to replace pip, pip-tools, pipx, poetry, pyenv, twine, virtualenv and more. Written in Rust; its README cites 10-100x faster than pip (benchmarks linked). 3/ Projects: uv init, uv add ruff, uv run ruff check, uv lock, uv sync. Universal lockfile, Cargo-style workspaces. 4/ Scripts: declare dependencies inline in a single file and uv run it. Great for quick automations. 5/ Also new in 0.13.1: Linux SPARC support, missing trusted hashes reported in resolution errors, and tool/Python uninstalls no longer touch unrelated neighboring files. 6/ Install: curl -LsSf https://astral.sh/uv/install.sh | sh or pip install uv. Already have it? uv self update. Notes: github.com/astral-sh/uv/releases/tag/0.13.1

Follow-ups

uv self update — if you used the standalone installer, that's the whole upgrade.
Try Python 3.16.0a1 in a throwaway env with uv's managed Python versions.
uv pip is a pip-compatible interface — same commands, faster.
Preview: uv tool upgrade now works with tool-install-locks enabled.
What did uv replace in your stack? pipx? pyenv? poetry? Reply below.

Product Hunt

Name: uv
Tagline: Fast Python package and project manager, written in Rust
Description: uv replaces pip, pip-tools, pipx, poetry, pyenv, twine and virtualenv with one tool. Manage projects with a universal lockfile, run single-file scripts with inline dependencies, install Python versions and CLI tools, and use a pip-compatible interface. Global cache for disk efficiency. macOS, Linux, Windows. Install with curl or pip.
First comment: Suggested maker comment, to be written by the maintainers: uv's goal of being a single tool for Python packaging; what 0.13.1 adds (smaller binary, faster index parsing, CPython 3.16.0a1, Linux SPARC); ask which workflow readers would move to uv first and where it falls short.
Note: uv is established; PH may suit a major version better than a patch. We would flag this to the maintainers.

Show HN (Show HN posts must come from the maker)

Title: Show HN: uv 0.13.1 – Python package manager, smaller and faster parsing Our note: HN discourages reposting well-known projects for patch releases; recommend skipping Show HN for 0.13.1 and saving it for a major release. Draft kept: "uv is a Python package and project manager written in Rust... (README highlights) ... This release reduces binary size, speeds Simple API parsing, adds CPython 3.16.0a1. Feedback welcome."

r/Python — "uv 0.13.1 released: smaller binary, faster index parsing, CPython 3.16.0a1" (check sub's release-post rules/flair).
r/learnpython — angle: "one tool instead of venv+pip+pyenv" beginner walkthrough using README project example (no release spam). Each post body would follow: summary → commands → link → maker disclosure.

Release notes (condensed)

uv 0.13.1 — Enhancements: ignore Requires-Python upper bounds in uv pip check/--strict; Linux SPARC; report missing trusted hashes. Python: CPython 3.16.0a1. Preview: uv tool upgrade with tool-install-locks; PEP 825 variant labels parsing. Performance: smaller binary; faster Simple API parsing; less metadata parsing overhead. Fixes: uninstalls no longer delete unrelated adjacent files.

7-day schedule

Day	Platform	Asset
1	X thread	launch
2	r/Python; follow-up 1
3	follow-up 2
4	r/learnpython guide
5	follow-up 3
6	follow-up 4
7	follow-up 5 (ask)	PH/HN held for major release

↑ Back to sample list

gum v2.0.2

Here's how we'd launch gum v2.0.2.

Unofficial sample: not written, reviewed, or endorsed by the gum maintainers. Not affiliated. Based only on the public README and release notes: https://github.com/charmbracelet/gum · release notes. Drafts below are written as suggestions for the maintainers; Dev Hype has not posted any of them.

Positioning brief

For: people writing shell scripts and dotfile aliases who want interactive prompts without writing Go.
Problem: shell scripts are ugly and hard to make interactive.
Hook: "A tool for glamorous shell scripts" — choose, input, write, confirm in one line each.
Proof (README): built on Bubbles and Lip Gloss; tutorial builds a Conventional Commits helper; packages for brew, pacman, dnf, nix, flox, winget, scoop, apt, yum, FreeBSD; binaries for Linux, macOS, Windows, FreeBSD, OpenBSD, NetBSD. v2.0.2: fixes raw ANSI capability sequences leaking (Bubble Tea v2 bump).

X thread (draft for the maintainers to post)

1/ Make your shell scripts glamorous. gum gives you menus, inputs, text areas and confirm prompts — one command each, no Go code. 🧵 2/ Pick from a list: gum choose "fix" "feat" "docs" "chore" 3/ Ask for text: gum input --placeholder "scope" — or multi-line with gum write. 4/ Guard the dangerous stuff: gum confirm "Commit changes?" && git commit -m "$SUMMARY" 5/ Chain them and you get a full Conventional Commits helper in a short script — the README walks through it. 6/ v2.0.2 fixes raw ANSI sequences leaking in non-input programs. brew install gum (or pacman, dnf, nix, winget, scoop…). github.com/charmbracelet/gum

Follow-ups

Save output to a variable: TYPE=$(gum choose fix feat docs) — gum prints the choice to stdout.
Dotfile idea: wrap your most-used git alias in gum confirm.
Packaged nearly everywhere: brew, pacman, dnf, nix, flox, winget, scoop, apt, FreeBSD pkg.
Built on Bubbles + Lip Gloss — the same Charm libraries, from Bash.
What's the first script you'd gum-ify? Share it.

Product Hunt

Name: Gum
Tagline: Glamorous, interactive shell scripts — no Go required
Description: Gum gives shell scripts ready-to-use UI utilities: choose from lists, prompt for input, write multi-line text, confirm actions. Built on Charm's Bubbles and Lip Gloss. Use it in scripts and dotfile aliases with a few lines. Available via brew, pacman, dnf, nix, winget, scoop and more, with binaries for Linux, macOS, Windows and BSDs.
First comment: Suggested maker comment, to be written by the maintainers: why Gum exists (Charm's TUI polish for people writing Bash, without Go); the v2.0.2 fix for stray ANSI output; ask what scripts people build with it.
Note: patch release; PH best paired with a feature release.

Show HN (Show HN posts must come from the maker)

Title: Show HN: Gum – interactive prompts for shell scripts without writing Go Text: Gum is a CLI that exposes TUI components (choose, input, write, confirm) as commands you call from shell scripts. Example: a Conventional Commits helper built from four gum calls (README). Built on Bubbles/Lip Gloss. Latest is v2.0.2. Feedback welcome. (Caveat: likely posted before; the maintainers would decide.)

r/commandline — "Gum: menus and prompts for your shell scripts in one command each" — commit-helper walkthrough.
r/unixporn or r/dotfiles — angle: dotfile aliases with gum confirm/choose (check showcase rules).
r/bash — practical: capturing gum output in variables.

Release notes (condensed)

gum v2.0.2 — Fixed: raw ANSI capability sequences no longer leak in no-input programs (Bubble Tea bump, #1155, @andrinoff).

7-day schedule

Day	Platform	Asset
1	X thread; Show HN	launch
2	r/commandline; follow-up 1
3	follow-up 2
4	r/bash
5	follow-up 3
6	r/dotfiles; follow-up 4
7	follow-up 5

↑ Back to sample list

Sample launch kits

hyperfine v2.0.0

Positioning brief

X thread (draft for the maintainers to post)

Follow-ups (5)

Product Hunt

Show HN (Show HN posts must come from the maker)

Reddit

Release notes (condensed)

7-day schedule

uv 0.13.1

Positioning brief

X thread (draft for the maintainers to post)

Follow-ups

Product Hunt

Show HN (Show HN posts must come from the maker)

Reddit

Release notes (condensed)

7-day schedule

gum v2.0.2

Positioning brief

X thread (draft for the maintainers to post)

Follow-ups

Product Hunt

Show HN (Show HN posts must come from the maker)

Reddit

Release notes (condensed)

7-day schedule