Live data from Hacker News

Bruno: Fast and Git-friendly open-source API client (Postman alternative)

usebruno.com

291–300 of 444 posts

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#291

Earlier quoted context omitted.

If you use IntelliJ based products, the builtin HTTP Client is awesome. https://www.jetbrains.com/help/idea/http-client-in-product-c...

If you use computers, Curl is awesome. https://curl.se/

For JSON based REST APIs httpie is somewhat easier to use.

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#292
post #288
post #286

Good to see some more open source competition in this space. SoapUI had most of those features some 15 years ago. I never understood why Postman became so popular, my current team even throws money at them.

Basically because of "blah but it is Java!" kind of argument. SoapUI is great.

And the "SOAP" part of the name is not helping either.

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#293
post #287

I find interesting on how on a startup related forum, anything related with not paying is always celebrated.

Generating revenue through the creation of value via innovation is great; using dark ux patterns to extract revenue from a captive user base, not so much.

I think in cases like postman, people don’t like when features they previously had used for free suddenly comes with a price tag; rather than innovate and create new value that is worth paying for, some companies are opting to take away features user previously had. Yes, they own/control the software and want to make money , which fine, but they created a dissatisfying user experience as they tried to coercively move users into their cloud offering, wether they wanted to or not, and regardless if it provided user value. After they did that, they shouldn’t be surprise a portion of their user base decide to ditch the product and complain about the experience. This is compounded by the fact that they leveraged the contributions of an open source community, and at the same time there are other options freely available that aren’t locked into a proprietary cloud login.

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#294

Lately Postman suddenly required creating an account to their cloud, to use my five different rest requests from scratchpad. I got annoyed so bad that deleted that piece of cr*p immediately. Never looking back. Then I found Bruno and fell in love. Thanks for the great work!

We used Postman but it got forbidden in our org for that reason, so no more.

Can't say I really miss it. I personally prefer just using a jupyter notebook for these kinds of tasks. With a custom tool like this it becomes a dead end with the data. Maybe you want to decode it if it is on a binary format. Or you want to plot some basic stats?

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#295
post #287

I find interesting on how on a startup related forum, anything related with not paying is always celebrated.

Great to see most people are smart enough to not apply same model on all problems in their life.

Productivity tools better to be lean, simple, free & open source in some cases. This is one of those.

Of course, you can keep throwing money at bulky software continuously making things slower and more complicated, just because you never have to worry about money thanks to the VC money. I’m old enough to not buy that this is how startups operate in general though.

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#296

Lately Postman suddenly required creating an account to their cloud, to use my five different rest requests from scratchpad. I got annoyed so bad that deleted that piece of cr*p immediately. Never looking back. Then I found Bruno and fell in love. Thanks for the great work!

We used Postman but it got forbidden in our org for that reason, so no more. Can't say I really miss it. I personally prefer just using a jupyter notebook for these kinds of tasks. With a custom tool like this it becomes a dead end with the data. Maybe you want to decode it if it is on a binary format. Or you want to plot some basic stats?

I've always preferred Insomnia over Postman. The interface fits me better. But now they also started requiring cloud login, so maybe I'll give Bruno a try if it degrades further

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#298
post #9

I myself use Paw [0] because it's native to MacOS, but I'm a little bit worried for it's longevity as it being supported by a SaaS business. But so far it's been great to document API for my personal projects. [0]: https://paw.cloud/

I’m envy? I’m hoping for a native GUI application for Linux. Electron looks ugly, it doesn’t integrate, fails to handle HiDPI usually, in best case it eats a ridiculous amount of memory (factor 5x compared to native) and in worst case it has security issues due to Blink and lot of JS. Electron is Flash for the Desktop.

I agree. Whenever I can choose between a webapp/Electron or a native app, I'll always go with the native app.

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#299
post #287

I find interesting on how on a startup related forum, anything related with not paying is always celebrated.

Once CEO asked me: "why are you spending months of your valuable time to create a tool to solve a thing, instead paying $10/month?"

"I know developers never pay, but why?"

Re: Bruno: Fast and Git-friendly open-source API client (Postman alternative)

#300
post #23

Can someone explain what Postman or Bruno is for? I know it's something for interacting with apis but why would i use it. I interact with apis a lot with curl or wrapper in my languages but never really needed something else?

To put it simply: Postman is for everything but what curl is for. Sure it also performs the actual request somewhere under the hood but that’s mostly irrelevant. Having a single integrated user interface (it could also be a text UI) to craft a request, sometimes sending JSON, sometimes a file, then sending it to inspect the result, then modifying the request then doing it again is very powerful. Not to mention OAuth/OIDC support and the like.

Sometimes, you have to find out how an API works, exactly. Sometimes you want to test your own APIs in ways the regular clients do not allow.

Post reply on HN