TL;DR;
Why developers are abandoning Postman and its clones?
Enshittification
this post was submitted on 21 May 2026
13 points (84.2% liked)
Programming
27014 readers
196 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Didn't read the article, but that's why I abandoned it.
I don't remember making this comment, but it was my verbatim reaction, so I very well could have.
I’ve taken to writing .http files which are runnable on a number of IDEs and plugins. I don’t need to know what anybody else is using to run them, they live with the code and I’m happy.
That said, I’ve seen people on QA do really cool end-to-end tests at load via very approachable scripting on Postman.
There’s lots of room for “to each their own” here.
So much work and investigation into a tool that is a front end for something already on your system.
I just wish that they wrote more articles. Their writing style is superb. Can't argue with this though:
More coming soon. Or not. I don't owe you shit.
I feel like people who make these arguments in earnest are simply terrible at change and lack empathy. "Works for me, so I refuse to understand why it doesn't work for others". It's so conservative neckbeard and offputting.
Yes and no.
There's a lot to be said about empathy, assumed knowledge/expertise, acquisition of knowledge/expertise, mentorship, deadlines, etc...
But on the other hand, there are psychological effects that result in people being truly blind to alternatives. It's not that they don't think the alternative is correct, or that they don't want to spend mental/emotional energy on learning an alternative. It's that they truly can't even consider that there is an alternative until they are explicitly told to use it. That website exists for those people.
But how do you collaborate?
Q: What about team collaboration?
A: It's a text file. Put it in Git. You know, that thing you should be using anyway? Now your requests have version control, code review, and diffs. For free. Revolutionary, I know.
expose a backdoor endpoint on every collaborator's device and peruse their shell history
Our team lives in Git, our communication is happening on slack, our docs written and maintained on confluence and after some time they always drift away from the actual requests inside Postman.
So we built and open sourced Voiden a few months ago: an API tool where all that: specs, tests, context and docs are always together in the same executable plain text file (markdown). We also made this Git native so that every change is versioned and tracked just like code.
The last change we have made is to add a Runner so that one can run the files directly from the terminal and CI/CD pipelines.
here is the tool: https://voiden.md/download repo: https://github.com/VoidenHQ/voiden
welcome to try and give feedback!
_
That looks pretty nice. The documentation said it fears me.
I started using bruno for lazy gui "make a request" needs.
But for anything serious python requests is right there, so I mostly used that for testing.
I remember when postman used to bring little envelopes (sometimes little boxes) to people's homes and was paid by tax money and the small amount of postal fees we paid.
Go back to the future:
https://addons.mozilla.org/en-US/firefox/addon/rester/
I also use Bruno: https://github.com/usebruno/bruno
Never had any use case for collaborating on requests, why do you use it?
When you explore an API in a team and would like to collaborate on that with somebody. If you've worked on any big tech API, with Oauth, and have secrets, writing a script for every request combination takes way too long. Simply pasting the URL and using the stored oauth token within the session is easy with a frontend. And it's reusable and sharable within your team.
I see. Thanks!