hurl VS websocat

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

It's similar to running netcat in server mode, wrapping a script. It's even closer to doing that using websocat [1], whereby one does not have to do the websocket header juggling.

The main difference is that while netcat or websocat will spawn a new process for each connecting client, ScaleSocket has a concept of rooms (channels). For a room, a process is spawned once only. All clients connecting to the same room are routed to the same process. This is not straight forward to do using the forementioned tools.

There's a small comparison page [2] where I have mentioned some alternative tools.

[1] https://github.com/vi/websocat

one combination I came to really love this year is babashka (https://github.com/babashka/babashka) + websocat (https://github.com/vi/websocat). I wrote about a method of live web programming with this pair at https://github.com/whacked/cow/blob/main/a%20technique%20for...

babashka isn't strictly necessary; you can also pipe plain text, but pushing hiccup expressions to the browser DOM from the REPL with instant feedback has opened a new world of interactive programming for me.

No... the core of it is a django instance in the cloud with a Vue front end (what you're seeing in the screen shot). To push data in, the client connects to a websocket (using https://github.com/vi/websocat) and push key/value pairs in. I'm not in the middle of gameplay at all.

There's really nothing to this. I just have to provide the bus name and an optional pattern. Now using websocat, I get output like this:

Subscriptions is real-time streaming of data from server to client through WebSocket. You will need a constantly active connection to stream such events. You cannot use curl for this and have to use a WebSocket client like websocat if you want to access it via command line. Once executed, a stream of pending transaction IDs will start flowing in.