hurl VS dive

I tried Hurl after Insomnia went the way of Postman. The highlights you list were the strong drivers for testing it out. Where Hurl fell short was composing requests. Example: X.hurl response has authToken. Y.hurl uses authToken. Z.hurl uses authToken. There's no import ability[1], so you've got to use other tooling to copy X.hurl into Y.hurl and Z.hurl.

Ultimately settled on Bruno. It's backed by readable text files[2] as well. The CLI works for scripting. And the GUI is familiar enough that I've managed to convert Postman holdouts at my dayjob.

[1]: https://github.com/Orange-OpenSource/hurl/issues/1723

[2]: https://docs.usebruno.com/bru-language-samples.html

I haven't used it myself, but maybe something like Hurl? It's not a GUI like Postman though

No, you got what's you write. If you want, you can see the run curl's command, save it in a script and replay it without Hurl. You can check the source code here [1]

[1]: https://github.com/Orange-OpenSource/hurl

You might check out hurl for a RestAPI tool replacement. There is also a vim plugin for it, although I have not used it. Someone already mentioned dadbod (which I think works great on its own), but if you are curious there is also a plugin to add a UI on top of it.

just write a simple frontend on top of https://github.com/Orange-OpenSource/hurl

We've a more "classic" changelog in GitHub [1], I see the blog post as an editorial view of the changelog: highlights of main features/changes with some context.

[1] https://github.com/Orange-OpenSource/hurl/releases/tag/4.0.0

I must say that the name is already taken by another tool language https://github.com/Orange-OpenSource/hurl which is a very good idea(similar to httpYac)

GitHub: https://github.com/Orange-OpenSource/hurl

That's why we have hurl

Dive is an open-source tool that allows you to explore the various layers of a Docker image. It shows you the content of each layer and helps you identify voluminous or unnecessary parts.

Dive is a great tool for debugging this. I like image reduction work just because it gives me a chance to play with Dive: https://github.com/wagoodman/dive

One easy low hanging fruit I see a LOT for ballooning image sizes is people including the kitchen sink SDK/CLI for their cloud provider (like AWS or GCP), when they really only need 1/100 of that. The full versions of both of these tools are several hundred mb each

This post is going to be shorter. I'd like to highlight a tool that I really enjoy working with called "Dive" It is an essential tool when working to build and optimize docker containers.

Whether you work with Docker regularly or even create your own Docker containers, Dive is a great tool for streamlining image sizes, potentially helping you save storage costs and speed up deployments.