91–100 of 154 posts
Earlier quoted context omitted.
Not to mention saving headers, tokens, doing multiple requests using the results from the previous, etc. This guy would say "just use bash" and ignore the average user experience.
You can do all that in a shell script though
_plz() {
curl [rest of common args]
}
_plz GET endpointEarlier quoted context omitted.
Yeah, hence why no one uses terminals for doing work with git, codex, claude-code, neovim and curl, everyone and their mother are using desktop GUIs for those things, clearly.
Inversely, plenty of people use GUIs for all of those things.
Curl's UX is very dated and I wouldn't recommend it to any new user. Use many alternatives like httpie [1] or something like curlie [2] which is just an UX wrapper around the same libcurl. Httpie also has a postman-like web interface. 1 - https://httpie.io/ 2 - https://rs.github.io/curlie/
curl may be outdated but at least it's a survivor. the alternatives (esp. the suspicious httpie grift) won't make it.
After decades it should have been obvious by now that the vast majority of users prefer GUIs.
Yeeeep. My response to this article is the same one I have to anyone out here screaming "it's so easy to just do it my way!": if it's so easy, then do it for me! The ffmpeg fans are the loudest screechers I've found, in this area. They'll point to the trainwreck of a UX that is Handbrake as an example of GUI for terminal commands. And, look - command line utilities are great and Handbrake is a super good product that…
Also they’re more stable than anything else. You can coast for decades on a script.
Earlier quoted context omitted.
Yeeeep. My response to this article is the same one I have to anyone out here screaming "it's so easy to just do it my way!": if it's so easy, then do it for me! The ffmpeg fans are the loudest screechers I've found, in this area. They'll point to the trainwreck of a UX that is Handbrake as an example of GUI for terminal commands. And, look - command line utilities are great and Handbrake is a super good product that…
You can’t compose GUI unless you go the emacs and smalltalk route (MacOS AppleScript is a very poor example). The one thing with CLI tools is how easy to compose them and have something greater. Also more versatile than a GUI app. Also they’re more stable than anything else. You can coast for decades on a script.
This is a very funny, love it ! every developer needs to know basics like such, I hope this site continues.
That was exactly what I needed this morning.
Earlier quoted context omitted.
For repeated commands, my projects have a Make/Just file that has cURL commands I wanna validate. Sometimes I even load JSON from a tests/fixtures/*.json file, that also can be reused for other non-E2E tests. Not sure how some developers could be so allergic to the terminal, don't you already spend a lot of time there?
> Not sure how some developers could be so allergic to the terminal, don't you already spend a lot of time there? Who says I'm allergic to the terminal? I already stated that I use curl. I could also ask why are some developers so allergic to any kind of UI. And they're very vocal about it. Just use whatever you want.
Preferring "a couple of clicks" vs "run one command" seems to indicate so, otherwise I'm not sure why'd someone would prefer the former instead of the latter.
I've been using curl, like forever. I don't understand the preoccupation for using postman, et. al. -- why pay for something that literally requires a little bit of light RTFM?
Using curl, how would I send a collection of frequently used requests to a coworker? Plain text file?
[flagged]
$ jo details[author]=Dickens details[age]=dead books="$(jo -a 'Oliver Twist' 'Great Expectations')"
{"details":{"author":"Dickens","age":"dead"},"books":["Oliver Twist","Great Expectations"]}