Now I just have a Makefile with a bunch of curl invocations, or Python tests with requests to match against expected responses.
I get the whining, but teams need ways to share their complex workflows, and teams are where the money is for all dev focused software.
That's who pays for all your tools to have free versions.
People who use make and curl to jury rig some unshareable solution together that no-one else in their company would even bother trying to use aren't worth any money to companies.
???
Mash 'em, boil 'em, put 'em in git, next to your code?
Teams that are knowledgeable jury rig their own custom solutions without all the enterprise cruft. They make solutions that fix their problem and they do it faster than the teams who use bloated enterprise solutions.
I am tired of seeing over engineered enterprise solutions that that are implemented and never used because they can’t be integrated into the dev workflow easily. Simple bash script that does the task it was designed to do beats any enterprise crap.
Those of us who can survive without desperate monetization plays are worth quite a lot, actually. They say 'jury rig', we say 'engineer'.
Also I am not counting that Insomina won't follow the same footsteps as Postman.
There are several FOSS command line tools that can do this easier, e.g. https://httpie.io/cli
Git is pretty good at sharing you know
Complacent corporate teams. Agile teams need to simplify their workflows, and know that a Makefile can be better than some closed down, Cloud-first tool.
>That's who pays for all your tools to have free versions
Nah, we have free versions for stuff without enterprise editions too.
>People who use make and curl to jury rig some unshareable solution together that no-one else in their company would even bother trying
It's that "no-one else" that doesn't bring value.
Apps like Postman are the wrong tool for this purpose.
If you want to share workflows, let alone complex workflows, any automated test suite is far better suited for this purpose.
We are in the age of LLMs and coding agents, which make BDD-style test frameworks even more relevant, as they allow developers to implement the workflows, verify they work, and leave behind an enforceable and verifiable human-readable description of those workflows.
Bash and Perl scripts run, truly, everywhere - so you get real collaboration. I can share it with anyone on my team and they can use it.
Connecting to a license server is pretty much standard.
For Postman it is annoying because it was never explicitly stated and it seemed like they are cool kids making nice helpful app. But really they are in for money. Which is not bad have to say but the way they did it is bad.
But the UX is just terrible (for me) or at least has been every time I've tried to start using it more.
I mean, come on, the most basic use of creating a request goes like this:
1. Sorry, can't let you create a request before you create a collection.
2. Sorry, can't let you create a collection before you make a decision on in which path you will be storing all your collections.
3. Sorry, can't let you create a request before you think of a good name for it.
etc.
Like what the heck? This should be just one click to create a new untitled request then fill in the URL and send.
At first I thought this might be growing pains since it was new but every year I try it and it hasn't improved.
it might have changed now but it did not support grpc endpoints, which was a dealbreaker for me. but definitely appreciate the project and i hope it reaches core feature parity soon.