Postman: The 800lb Gorilla That Eats Your RAM
Look, Postman works. It's what everyone uses because it was first to not suck completely. But holy shit does it love to consume memory - I've seen it hit 2GB just sitting there with a few collections open.
The good stuff: Newman CLI actually works for CI/CD automation, the testing framework is solid once you figure out the weird Chai.js syntax, and collections sync across your team without breaking (usually). Mock servers are decent if you can stomach the pricing.
The annoying stuff: The desktop app crashes on Ubuntu 22.04+ with certain graphics drivers (learned this during a deployment when the staging environment needed testing). Collections get corrupted if you edit them simultaneously - lost 3 hours of work because two team members saved at the same time. The pricing jumped from reasonable to "are you fucking kidding me" around v9 - we went from $150/month to $450/month for the same team size.
When to use it: Your company already pays for it, you need advanced scripting, or you're stuck with enterprise compliance bullshit.
Insomnia: Pretty but Kong Fucked It Up
Insomnia used to be great - clean UI, GraphQL that didn't suck, and no Electron bloat. Then Kong bought it and slowly started Kong-ifying everything.
The good stuff: Still the best GraphQL experience by far. Schema introspection works like magic. Git sync is actually native, not some hacky plugin. UI doesn't make you want to gouge your eyes out.
The bad stuff: Import from Postman breaks half your auth setups - spent a Friday rebuilding OAuth flows that worked fine in Postman. Pro features are paywalled harder than before. Plugin ecosystem is dead - most haven't been updated since 2022, and the ones that work break with every major update.
When to use it: GraphQL-heavy work, you hate Postman's UI, or you're already in the Kong ecosystem.
Thunder Client: The VS Code Extension That Could
This is what happens when someone says "fuck it, I'm not opening another app." Works entirely inside VS Code, which is either perfect or useless depending on your workflow.
The good stuff: Zero context switching if you live in VS Code. Cheap as dirt - $4/month is less than your daily coffee. Collections stay with your project files. Fast as hell because it's just a VS Code extension.
The bad stuff: Collaboration features are basically non-existent - sharing collections means emailing JSON files like a caveman. If your team doesn't use VS Code, you're screwed. Pro features are limited compared to the big boys. Breaking changes with VS Code updates happen - extension died for 3 days when VS Code 1.75 launched.
When to use it: You're a solo dev or small team, everyone uses VS Code, and you're tired of switching apps every 30 seconds.
Hoppscotch: The Idealistic Open Source Dream
The only one that doesn't want to lock you into their ecosystem. Actually free, actually open source, actually respects your privacy. Sounds too good to be true, right?
The good stuff: Unlimited everything on the free tier. Self-host it if you're paranoid. No vendor lock-in because you have the source code. Clean web UI that loads fast.
The bad stuff: Missing advanced features the others have. Community plugins are hit-or-miss. Documentation can be sparse for edge cases. Still the "new kid" despite being around for years.
When to use it: You hate paying for tools, need self-hosting, or believe in open source idealism. Also works great for quick tests without installing anything.