Weird. Mine doesn't, and it's been 8 days since that post. I even checked for updates, and I'm up to date. Maybe they reverted their bone head move? (I don't use it daily)
One nice thing about FOSS CLI tools is they're easy to script. While it's pretty tough to script general cases, I often find my workflows orbit around a handful of commands, and scripting often can improve the UX by a large margin. It does require tinkering a bit though.
Seriously, python with the requests lib in a jupyter notebook is always a nicer user experience than any REST API GUI, most importantly once it's grown a bit.
I have found Bruno (https://github.com/usebruno/bruno) to be a decent basic alternative with a nice bonus of being version control friendly, keep in mind that it's fresh and relatively unpolished though - for instance it doesn't ask you to save changes before closing the app.
The one thing I'm afraid of is that it's a single maintainer project, and while they are active now, I'm not sure how this is going to fare in a few months or so.
Glad to see alternatives but disappointed that Bruno does not support OpenAPI specification.
At my company, we hand-edit OpenAPI specs in YAML and it gets consumed by many tools that generate types[0], static analysis and dynamic checks[1]. The OpenAPI spec itself is linted[2]. And of course, Postman consumes OpenAPI.
Tools that are built on open standards will naturally see greater adoption over those that use proprietary formats.
And yet it pretty much has 80% of the value that Postman provided to me.
There is some missing polish (like missing utilities in scripts or buggy drag-and-drop) and a couple bigger things like no authorization schemes or code export, but the killer thing it has over pretty much all the competition is the JS glue code AND first-class VCS support. Even insomnia had garbage-tier glue code support, something that was very much missing coming from Postman.
Yup, the JS glue code is something that I am very proud of. You can install any npm package via package.json. Require them inside your scripts and it just works.
In every other tool, they treat a collection like something that can be modified only via GUI. In Bruno, its more of a developer mindset. Even if you don't have Bruno GUI, you can open it in an editor and make changes to it - just like code
External npm package installation is unique to Bruno and afaik no other tool has this.
https://news.ycombinator.com/item?id=37680126
No reason to trust them at all at this point.