1. 26
  1.  

  2. 3

    Can any lobsters using HTTPie explain what drew them away from curl or what about curl pushed them to HTTPie?

    1. 8

      I haven’t been using it for long but for me the nicest thing so far is being able to see the whole response: headers, body, and all of it syntax-highlighted by default. The command-line UI is a little nicer as well, more clear and intuitive.

      It will probably not replace my use of curl in scripts for automation, nor will it replace my use of wget to fetch files.

      Now if someone took this and built an insomnia-like HTTP client usable from a terminal window, then we’d really have something cool.

      1. 1

        I’m guessing you mean this Insomnia. Looks cool. Good example of an OSS product, too, given most features people would want are in free one.

      2. 4

        I use both depending on circumstance (more complex use cases are better suited for curl IMO), but the significantly simpler, shortened syntax for HTTPie as well as the pretty printing + colorization by default for JSON APIs is pretty nice.

        1. 3

          I wouldn’t say I’d been ‘pushed away’ from curl, I still use curl and wget regularly, but httpie’s simpler syntax for request data and automatic coloring and formatting of JSON responses makes it a great way to make quick API calls.

          1. 3

            I like short :8080 for local host syntax.

            1. 3

              It’s all in how you like to work. Personally I enjoy having an interactive CLI with help and the like, and the ability to build complex queries piecemeal in the interactive environment.

              1. 3

                Sensible defaults and configurability.

                1. 2

                  I need a command line HTTP client rarely enough that I never managed to learn curl command line flags. I always have to check the manual page, and it always takes me a while to find what I want there. I can do basic operations with HTTPie without thinking twice and the bits I need a refresher on — usually the syntaxes for specifying query parameters, form fields or JSON object fields — are super fast to locate in http --help.

                  1. 1

                    curl is the gold standard for displaying almost anything including tls and cert negotiation. i use bat mostly now though for coloured output and reasonable json support. https://github.com/astaxie/bat