Depends how comfortable you are with curl and your workflow. I'm much more productive using curl vs any GUI you give me. Still have OpenAPI specs in my projects but curl is much faster initially.
It falls apart instantly when you need to pass data from one endpoint to another or add any sort of logic like filtering through data - so any time you have non-trivial workloads where you don't want to spend half your time fighting against jq or shell.
`curl ... > out.json` then `curl ... -d out.json`. Wrap it in a shell script for quick iterations.
> filtering through data
`curl ... | jq | grep`. I don't know of any tool that will find what I'm after faster than the shell.
For bootstrapping and quick experiments curl is right there at my fingertips, no need to spin up an electron app, make a bunch of definitions and all that. When I want something more usable OpenAPI serves as stateful and interactive test environment and documentation at the same time.
I do agree curl can get a little verbose but create an alias: `alias jc='curl -H Content-Type: application/json` and using it is as simple as `jc $URL` for GET or `jc -X POST -d '{ ... }' $URL` for the rest of the methods.
I really recommend getting comfortable in the shell, it's amazing how productive it can be and becoming a bit of a lost art these days. All the tools are composable and working together it's so zen.
You don’t have to fight tools if you learn them, but I understand— as a fellow programmer— that you don’t always have time to learn them. However, it’s pretty easy to use pipes and tools like jq to do complex stuff.
While jq is powerful and I use it in scripts, it's one of the least intuitive languages I use, to the point I have to look up basically everything non-trivial.
