The API Tooling Crisis: Why developers are abandoning Postman and its clones?
(efp.asia)
from dhruv3006@lemmy.world to programming@programming.dev on 21 May 11:14
https://lemmy.world/post/47156990
from dhruv3006@lemmy.world to programming@programming.dev on 21 May 11:14
https://lemmy.world/post/47156990
#programming
threaded - newest
justuse.org/curl/
So much work and investigation into a tool that is a front end for something already on your system.
But how do you collaborate?
expose a backdoor endpoint on every collaborator’s device and peruse their shell history
I just wish that they wrote more articles. Their writing style is superb. Can’t argue with this though:
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 me”. It’s so conservative neckbeard and offputting.
Go back to the future:
addons.mozilla.org/en-US/firefox/addon/rester/
I also use Bruno: github.com/usebruno/bruno
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: voiden.md/download repo: github.com/VoidenHQ/voiden
welcome to try and give feedback!
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!
TL;DR;
Enshittification