1. 4
    Announcing kurly v1.1.0 ☶ release github.com
    davidjpeacock avatar authored by davidjpeacock 8 months ago | cached | 7 comments
Announcing the public release of kurly, v1.1.0! New features include:
  • Resume transfer from offset
  • Cookie and cookie jar support
  • Send HTTP multipart post data
New installation methods include:
  • Linux via snap package
  • Arch Linux via Arch User Repos
Special thanks:

The following contributors made this release of kurly a success. This release would not be what it is without their help! Thank you! 👍

Binaries are available for the following platforms:

  1.  

  2. 5
    gecko avatar gecko 8 months ago | link

    This looks very cool as something close to a drop-in for curl. For interactive work, I’ve really enjoyed HTTPie, which breaks backcompat to provide a nicer overall experience (IMHO).

    1. 3
      apg avatar apg edited 8 months ago | link

      This is cool, and I am going to sound like a jerk, but, the big and really important aspect of the curl project is lib curl, not the curl command, which this doesn’t address. Given the choice of language, it doesn’t seem like you’re going after that which is a bit disappointing. Cool project, though! I’ll put it on my list of clients to mess around with.

      1. 1
        davidjpeacock avatar davidjpeacock 8 months ago | link

        You’re totally right; you don’t sound like a jerk at all. I keep thinking of how to address this massive short fall.

        I’m open to ideas and contributions too.

        Thank you, sincerely, for the comment.

        :-)

      2. 2
        colindean avatar colindean 8 months ago | link

        Aside from being written Go instead of ye olde C, what are the advantages of kurly over curl?

        1. 3
          gerikson avatar gerikson 8 months ago | link

          Sounds like they missed a chance to go with gurl instead.

          1. 3
            davidjpeacock avatar davidjpeacock 8 months ago | link

            Hah - that was indeed considered for a femtosecond or two. ;-)

          2. 2
            davidjpeacock avatar davidjpeacock 8 months ago | link

            Pasting from my answer to a similar question over on reddit, so I apologize for the slight redundancy, but…

            :-)

            Very good question; thank you for asking.

            A primary benefit is one of hindsight. kurly has the luxury of being a couple of decades newer than curl and as such has taken advantage of two core things.

            1. It’s written in a modern safer language, so hopefully won’t exhibit myriad memory safety security issues that curl is plagued with. 2) Doesn’t need to support as many legacy features such as FTP, Gopher, etc, that no one uses anymore. This reduces code complexity and of course less complexity is implicitly good.

            As stated on the README, this is an alternative to, not a replacement for, curl. :-)