3 ms·

> It's just one HTTP client. curl supports 28 transfer protocols [1] > There are better ones. curl has 60 language bindings, runs on 89 operating systems acr

> It's just one HTTP client. curl supports 28 transfer protocols [1] > There are better ones. curl has 60 language bindings, runs on 89 operating systems across 24 CPU architectures [1] So what is that mythical better client (that only does HTTP)? [1] https://daniel.haxx.se/blog/2022/11/25/89-operating-systems https://daniel.haxx.se/blog/2022/11/25/89-operating-systems

mgaunard 4y ago
a better HTTP client is one that does exactly what you want, nothing more and nothing less.
- dmitriid 4y ago
  Still no name or this mysterious better client. And what happens when I need something more, or something else? I need to find a different "better client"?
  - silon42 4y ago
    I still type wget when trying to download stuff... not sure if better, except for default behavior.
    - jabl 4y ago
      I usually use curl. wget does have one feature that curl doesn't (or at least I'm aware of), namely recursive downloading. So you can easily somewhat download an entire site.
    - dmitriid 4y ago
      I've run into weird situations where either curl or wget wouldn't be installed by default, so I use... whatever :) But usually curl.
  - mgaunard 4y ago
    I already explained, what's better is what fits your needs exactly. Without knowing your requirements it would be difficult to say. Say for example your main concern is latency, you only need support for MTU-sized payloads, you want ro guarantee that the TCP connection is always established ahead of time and your requests always follow the same pattern with a few bytes to tweak. You can easily write something that can do those things much better than curl in a couple of hours.
    - allarm 4y ago
      Oh right, and if your need is to open a specific site only, your best choice would be to write your own browser heavily optimized just for this particular site, instead of using Chrome. Nonsense.
- erinaceousjones 4y ago
  Yes, that's fine. cURL isn't a HTTP client. It's a command line tool and library for transferring data with URLs :-)

mgaunard 4y ago

a better HTTP client is one that does exactly what you want, nothing more and nothing less.

dmitriid 4y ago
Still no name or this mysterious better client. And what happens when I need something more, or something else? I need to find a different "better client"?
- silon42 4y ago
  I still type wget when trying to download stuff... not sure if better, except for default behavior.
  - jabl 4y ago
    I usually use curl. wget does have one feature that curl doesn't (or at least I'm aware of), namely recursive downloading. So you can easily somewhat download an entire site.
  - dmitriid 4y ago
    I've run into weird situations where either curl or wget wouldn't be installed by default, so I use... whatever :) But usually curl.
- mgaunard 4y ago
  I already explained, what's better is what fits your needs exactly. Without knowing your requirements it would be difficult to say. Say for example your main concern is latency, you only need support for MTU-sized payloads, you want ro guarantee that the TCP connection is always established ahead of time and your requests always follow the same pattern with a few bytes to tweak. You can easily write something that can do those things much better than curl in a couple of hours.
  - allarm 4y ago
    Oh right, and if your need is to open a specific site only, your best choice would be to write your own browser heavily optimized just for this particular site, instead of using Chrome. Nonsense.
erinaceousjones 4y ago
Yes, that's fine. cURL isn't a HTTP client. It's a command line tool and library for transferring data with URLs :-)