Postman defined the last era of API tooling. But not the next one.
Every major tooling shift starts this way.
Slack did not replace email by becoming a...
Sounds great in theory, but without a concerte suggestion on how that might actually work and be implemented it’s basically a scifi daydreaming nothingburger. (Or the pitch for the writers upcoming startup)
As far as I can see it is still just postman but the request and api definitions are stored in textfiles (and there are multiple projects that do exactly that already).
It seems to me that the blog author is talking about something beyond that.
Sounds great in theory, but without a concerte suggestion on how that might actually work and be implemented it’s basically a scifi daydreaming nothingburger. (Or the pitch for the writers upcoming startup)
There is Bruno, which is git based (also its FOSS). We use it in our team for a few months now and the git model is well suited to the context.
As far as I can see it is still just postman but the request and api definitions are stored in textfiles (and there are multiple projects that do exactly that already).
It seems to me that the blog author is talking about something beyond that.
Maybe. But then I don’t get their point tbh
Just in case you wanna try it out : https://voiden.md/
We have a very different approach to API tooling.
I knew it …