you are viewing a single comment's thread
view the rest of the comments
[–] 75 points 8 months ago (15 children)
  • [–] 46 points 8 months ago

    This has been solved since 1999. Read the manual.

    The deeper I get into Linux, the more I feel exactly this about most software in general. We just love reinventing the wheel, don’t we?

  • source
  • parent
  • [–] 29 points 8 months ago (11 children)

    -Curl "https://justuse.org/curl/"

    -Returns a ton of html stuff

    Can't even comply with their own argument.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 12 points 8 months ago (9 children)
  • [–] 2 points 8 months ago (8 children)

    Follow redirects? curl -L

    still gives HTML

  • source
  • parent
  • hideshow 8 child comments
  • [–] 9 points 8 months ago (7 children)

    Yeah? That's what the response is. What do you expect?

  • source
  • parent
  • hideshow 7 child comments
  • [–] 4 points 8 months ago (5 children)

    I think they're point is that curl is great but then you have to have a way to render it to know if it's correct. With apis you can use jq, but yeah a dump of html isn't really useful to humans

  • source
  • parent
  • hideshow 5 child comments
  • [–] 18 points 8 months ago

    Yeah but we're talking about API tools, not web browsers. People are using postman to see JSON, XML, or whatever horrible format the devs on the other side chose to use, not to render HTML graphically. If you query an HTML page using curl, you should get the HTML back, I don't see what's the problem

  • source
  • parent
  • [–] 4 points 8 months ago* (2 children)

    Oh. Fair enough. The intent for curl is definitely to display the HTML as it's whole point.

    Anyways.

    curl -L -o "/tmp/your.html" https://justuse.org/curl && librewolf "/tmp/your.html"

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 8 months ago

    As much as I think that's correct a lot of the time, something like Bruno has value too. Implementing complicated auth for an annoying service once and reusing it across several pre-written requests, useful features like a GUI and history to see prior responses from an endpoint, being able to share the "collection" in the repo as examples/developer tools that's maintained alongside the code, writing docs with each request to explain its usage, this stuff does add value that isn't trivial to do with curl.

  • source
  • parent