Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Postman Now Supports gRPC

blog.postman.com

Post reply on HN
Print view View original

71–80 of 216 posts

Re: Postman Now Supports gRPC

#71

Post by bathtub365 »

kaszanka wrote: post #61
lucideer wrote: post #54

Earlier quoted context omitted.

I used to like Postman until it locked me out of my locally-stored data while I was offline (testing my own applications on localhost) for an extended period , I found out that it phones home constantly (cannot be disabled) & locks you out if it fails. The developers stating they had no intention of changing this for "security reasons" before closing the Github issue sealed the deal.

This sounds unbelievable but it seems to be true? https://github.com/postmanlabs/postman-app-support/issues/10...

I don’t see anything in this issue that I’d characterize as

> The developers stating they had no intention of changing this for "security reasons" before closing the Github issue sealed the deal.

The issue is still open with no response from the developers that mentions security reasons.

Re: Postman Now Supports gRPC

#72

Post by nerdite »

dewey wrote: post #18
sbmthakur wrote: post #15

Earlier quoted context omitted.

> I basically used it as a curl gui. I just use Browser's Network tab for that nowadays. CORS can be a trouble at times, but that can be avoided with a few tweaks.

I think the killer feature for these separate tools is usually that you can easily do a right click -> "copy as curl" in the network inspector, then import it in Postman/Paw and then tweak parameters / add headers there. This is not really possible in the browser network tools.

I take that curl command to https://curlconverter.com

And get Python that I can start iterating on. They have lots of languages.

I used to use Postman but the clarity of the code is so much easier to see what’s happening vs postman imo.

Re: Postman Now Supports gRPC

#73

Post by adam_arthur »

paozac wrote: post #5

I used to like Postman, when it was a simple browser extension. I basically used it as a curl gui. Now > Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster. I guess I’m no longer their target user. Back to curl/httpie.

The UX has gotten noticeably worse for me. Maybe I'm using it wrong, but now you have to setup a project and name things before you can actually start issuing requests.

And I found the whole experience a bit confusing in terms of user flow

Re: Postman Now Supports gRPC

#74

Post by judge2020 »

kaszanka wrote: post #61
lucideer wrote: post #54

Earlier quoted context omitted.

I used to like Postman until it locked me out of my locally-stored data while I was offline (testing my own applications on localhost) for an extended period , I found out that it phones home constantly (cannot be disabled) & locks you out if it fails. The developers stating they had no intention of changing this for "security reasons" before closing the Github issue sealed the deal.

This sounds unbelievable but it seems to be true? https://github.com/postmanlabs/postman-app-support/issues/10...

This is OP's issue: https://github.com/postmanlabs/postman-app-support/issues/38...

Re: Postman Now Supports gRPC

#75

Post by cloverich »

bathtub365 wrote: post #71
kaszanka wrote: post #61

Earlier quoted context omitted.

This sounds unbelievable but it seems to be true? https://github.com/postmanlabs/postman-app-support/issues/10...

I don’t see anything in this issue that I’d characterize as > The developers stating they had no intention of changing this for "security reasons" before closing the Github issue sealed the deal. The issue is still open with no response from the developers that mentions security reasons.

Its in issue in the sibling comment. The suggested work-around is to not sign in at all.

Re: Postman Now Supports gRPC

#76

Post by ironmagma »

paozac wrote: post #5

I used to like Postman, when it was a simple browser extension. I basically used it as a curl gui. Now > Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster. I guess I’m no longer their target user. Back to curl/httpie.

I’ve found Hurl to be quite usable.

https://hurl.dev/

Re: Postman Now Supports gRPC

#77

Post by judge2020 »

avel wrote: post #68

As I have also been frustrated with the direction Postman has taken, I have a great alternative to suggest, if the only thing you want to do is fire requests on demand easily and do not need automated testing. The VS Code Rest Client extension https://marketplace.visualstudio.com/items?itemName=humao.re... is great for testing and debugging APIs. You create a "my_request.http" file that contains something like POST h…

Can it do substitution with some sort of application-based KV store? The main reason I used a rest client like Insomnia is so that I can reference secrets like {{ client_secret }} or {{ api_key }} and have a change to the value in the KV store reflect for every request.

Re: Postman Now Supports gRPC

#79

Post by jonfk »

To add another data point, I also moved on from Postman a while ago. Similarly to several commentors here I had found it to have become bloated, slow and buggy imho. In my particular use case, I found the urlencoding when using oauth1 to be pretty buggy. It would sometimes not work on certain headers it generated.

My team ended up moving to Paw but that has been a bit problematic since it only supports osx, so some team members are also using insomnia which doesn't seem to be much better in my opinion.

I recently found httpyac[1]. It's a cli and file based http client similar to the IntelliJ HTTP client, but has plugins, hooks and allows scripting through javascript blocks. It seems to have everything I need but I haven't used it much yet. It also already supports gRPC.

One of the issues I found with http clients I looked into is that they often don't provide enough functionality to hook into the request process. Either before or after a request is executed to add to the headers or parameters of the request or getting the results of the request. Postman did provide some of that but that's one area I wanted more from any client I looked at. I could of course simply wrap curl in a script but at that point, I will be maintaining my own jerryrigged version of an http client for my team.

[1]: https://httpyac.github.io/

Post reply on HN