One thing I am always sure to share with collegues when we discuss curl, is the fact from the command line you can generate the underlying C code.<p>This is pretty useful when creating a CLI for pretty much any app, and I've used it regularly to generate a CLI for an app.<p>My post on how to do it: <a href="http://austingwalters.com/export-a-command-line-curl-command-to-an-executable/" rel="nofollow">http://austingwalters.com/export-a-command-line-curl-command...</a>
Curl is alright, and congratulations on this massive and very impressive step forwards, but the CLI not exactly very user friendly. httpie[1] is a great tool if you find curl invocation somewhat arcane.<p>1. <a href="https://httpie.org/" rel="nofollow">https://httpie.org/</a>
For debugging on remote servers this is pretty handy (at least, one it makes its way into the server versions).<p>Now I have hope they'll put in a text editor that understands unix line endings.
> They ship 7.55.1, while 7.57.0 was the latest version at the time. That’s just three releases away so I consider that pretty good. Lots of distros and others ship (much) older releases.<p>Indeed. I am running latest High Sierra and:<p><pre><code> curl --version
curl 7.54.0 (x86_64-apple-darwin17.0) libcurl/7.54.0
LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0</code></pre>
On a side note, for all my daily download tasks (other than debugging some web API) I've settled with aria2[0]. It seems to support every protocol used in modern Internet and has plenty of flexibility (connection multiplexing, bandwidth control etc.). It can even serve as 24/7 torrent client managed via remote API.<p>0. <a href="https://aria2.github.io/" rel="nofollow">https://aria2.github.io/</a>
BTW another program (and a library) that should, IMHO, be made a standard component of every modern OS (except those that would choose to exclude it for a practical reason, e.g. some of extremely-lightweight and heavily specialized embedded ones) is SQLite3
Cool. I've been installing wget on every Windows PC in my authority since the days of Windows 98SE. Every net-enabled operating system is to have such a tool installed by default.
Cool, now I don't need to remember the arcane incantation to download a file with Powershell.<p>Do you think we'll see things like the good old "curl <some url> | bash" for Windows now? They still have no package manager worth using.
Either the Curl developers are at fault somewhere, which I somehow doubt, or distributions are really special snowflakes, which I also doubt, or software distribution in the Open Source world is, in my opinion, flawed:<p>> Finally, I’d like to add that like all operating system distributions that ship curl (macOS, Linux distros, the BSDs, AIX, etc) Microsoft builds, packages and ships the curl binary completely independently from the actual curl project.<p>Why would <i></i>everyone<i></i> rebuild it? There are some security considerations (matching source and binary; disabling "dangerous" stuff) and some feature considerations (disable stuff you don't need to reduce resource usage - maybe), but conceptually this seems so wrong to me.<p>Conceptually I'd want downstream packagers to talk to upstream developers so that upstream has reasonable defaults and settings and I'd want packagers to just <i></i>package<i></i> and make the package follow distribution conventions. But rebuild seems overkill.<p>Maybe I'm missing something obvious?