You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Comparison page refresh and a "deliberately not planned" section #69
docs/comparison.md is the page reviewers quote, and it is honest today. As the parity issues land (multipart, cookies, client certs, digest, PKCE, Postman import, HTML report) its table and its "What apic does not do" list go stale one row at a time. It also lacks a clear statement of what will never be added and why, so the same requests keep coming.
What
Add a row-level checklist to this issue and tick rows as the parity issues merge; each parity PR updates its row (add that to the PR checklist in CONTRIBUTING.md).
Add Kulala.nvim and ijhttp columns, since both are .http runners people compare against.
New section "Deliberately not planned": scripting and response handlers, custom step definitions, gRPC, WebSocket, MQTT/AMQP, a GUI beyond the terminal UI and the VS Code extension, a hosted workspace. One sentence of reason each, reusing docs/faq.md's wording, and a pointer to the escape hatches.
Link the parity epics from the page so readers can see what is coming.
Activity
Comparison: ijhttp and Kulala.nvim columns, deliberately not planned (#…
dataGriff commentedon Sep 24, 2026
Done in #116 (commit 045a9a0).
Row checklist, as of this merge:
Generated by Claude Code