4 ms·
I've been using https://github.com/bayne/dot-http https://github.com/bayne/dot-http but https://hurl.dev/ https://hurl.dev/ seems more full featured.
by dylanowen 3y ago
I've been using https://github.com/bayne/dot-http https://github.com/bayne/dot-http but https://hurl.dev/ https://hurl.dev/ seems more full featured.
- smt88 3y agoNeither of these have the convenience of the original Postman GUI and aren't really alternatives.
- sphars 3y agoBruno seems like a good up and coming candidate. Found about this one after all the insomnia drama a couple weeks ago https://github.com/usebruno/bruno https://github.com/usebruno/bruno
- dylanowen 3y agoFor creating requests the GUI of postman is way over the top. HTTP is so simple, why not just write that directly in a literate format you can checkin to a repo? For actually running the requests though I agree a gui is nice. I actually use dot-http as an embedded tool in a browser extension. They're still alternatives, just not in the style you're used to.
- smt88 3y ago> HTTP is so simple So is email. The simplicity of a protocol has nothing to do with the complexity of the workflow that produces it. > why not just write that directly in a literate format you can checkin to a repo? Because nothing I work on in Postman is something I need to check in to a repo. I need to test HTTP requests, and I've never worked with a code base that had raw HTTP requests in it. > They're still alternatives, just not in the style you're used to. The "style" is different enough that entire use cases become impossible. Let's say I want to copy HTTP response headers out of a log in JSON format. In Postman, I can paste JSON (and various other key-value formats) into the headers field, and it automatically parses it for me. There are a hundred little conveniences like that that require a good GUI.
- dylanowen 3y ago[dead]