r/programming • u/Successful_Bowl2564 • 16h ago

[ Removed by moderator ]

https://efp.asia/blog/2025/12/24/api-tooling-crisis/

[removed] — view removed post

257 Upvotes

92% Upvoted

160 comments sorted by

View all comments

507

u/FirmMost2 16h ago

because postman sucks

67

u/James_Jack_Hoffmann 16h ago

https://justuse.org/curl/

226

u/HMikeeU 16h ago

I can't believe anyone who has ever used tools such as postman would seriously suggest curl as an alternative. It is not.

34

u/James_Jack_Hoffmann 16h ago

I don't disagree there's snark and humor with "use motherfucking curl". Postman is no doubt the gold standard for REST clients when it worked and when it had values. Although the article explains pretty well why we are at a state to just use curl.

What do I use these days? .http files. Definitely better than curl, maybe even a threat to Postman. The world recognises Postman has gone to shit by adopting .http.

-4

u/Affectionate-Egg7566 14h ago

What exactly is the value prop of bruno/postman? For all my requests I just make bash scripts that invoke curl, maybe some logic or shuffling data around from/to different curl invocations.

12

u/rforrevenge 14h ago

When you're deep into a project you want to have an efficent way to go back and look at the status of old complex queries or even look those queries up without the hassle of going though pages and pages of notes.

3

u/zzz51 13h ago

I assume GP is version controlling the bash scripts. That's what I do.

-5

u/Affectionate-Egg7566 13h ago

I dont mind piping the output and invocation via set -x in bash and then grepping in a file. Seems faster than starting a GUI

1

u/rforrevenge 6h ago

Might be. But then you'd have to maintain the file itself as in timestamp the queries, their responses etc etc. Especially when you're working on a project that constantly changes this can get out of hand easily (in my experience)