Live data from Hacker News

Postman Now Supports gRPC

blog.postman.com

21–30 of 216 posts

Re: Postman Now Supports gRPC

#21

I have a meta question to ask, in threads like these where big products announce new features or big funding I always see commentors lamenting bloated software or it having too many features, not doing the one simple thing you want it to do, etc. To me it seems the only trajectory of developers building products is to add new features, its how we justify keeping ourselves around most of the time. So what my question…

You can't win. Most features added is because someone wants them. One person's bloat is another person's long sought feature.

Like a quote about Microsoft Office: A user only ever uses about 10 percent of the features. The problem is that all users use different 10 percents.

Re: Postman Now Supports gRPC

#22
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'm building a desktop app that lets you query HTTP APIs but also databases and files. So definitely something you can use as a simple curl GUI. The big benefit of this tool though is that you can script and graph results as well.

Always happy for any feedback!

https://github.com/multiprocessio/datastation

Re: Postman Now Supports gRPC

#23
post #18

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.

It seems pretty easy with Firefox - there's "Edit and resend" in the context menu of every request.

Re: Postman Now Supports gRPC

#25

I have a meta question to ask, in threads like these where big products announce new features or big funding I always see commentors lamenting bloated software or it having too many features, not doing the one simple thing you want it to do, etc. To me it seems the only trajectory of developers building products is to add new features, its how we justify keeping ourselves around most of the time. So what my question…

Things can be feature complete, and they often are at many businesses.

You need to build a solution to problem x. You do that and then the project is over. Outside of maintenance work it's a stable code base and you the developer move onto a new problem.

Examples of this in my mind are things like uBlock Origin. I'm not getting bombarded with updates on that project. It does the job it sets out to do, and it does it well.

Re: Postman Now Supports gRPC

#26
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.

Same story here. Postman just got too feature-rich for my blood.

curl + bloomRPC + graphiQL covers all my bases nowadays.

Re: Postman Now Supports gRPC

#27
post #18

Earlier quoted context omitted.

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.

It seems pretty easy with Firefox - there's "Edit and resend" in the context menu of every request.

And then you accidentally refresh or close the tab and everything is gone. I usually use specific requests over many days if I'm reverse engineering something so having these available, sorted in folders for me is important. Of course for other uses cases it might be fine to have them live in the browser.

Re: Postman Now Supports gRPC

#28
post #8
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.

It is also buggy, resource hog and instable. I use it on Ubuntu and os x m1 and I often have to kill it because it stops accepting any inputs or it ate all memory (and cpu after that when you click anything). Hoppscotsch and others are better now: I guess they wanted way too much too fast (I did not check but I suppose they got VC money?)?

Can confirm. Unfortunately, Postman is too resource-hungry (on Ubuntu). Launching is taking a while as well.

I have to admit I'm quite surprised that VS Code (which is also an electron app) is relatively fast and resource-sensitive. Having open a few applications in my daily workflow, moderate resource consumption is getting an important selling point for me.

Re: Postman Now Supports gRPC

#30
post #9

Earlier quoted context omitted.

Try Insomnia or Hoppskotch.

How is Insomnia any different? It's basically an OSS carbon copy of Postman.

I switched to Insomnia about a year ago for two main reasons:

- Didn't choke when having ~50 request 'tabs' open

- Didn't try to sell me shit

Granted, Postman had quite a lot more tools in its box for scripting, testing, sharing etc. but I didn't need those.

Insomnia has got a bit fatter since then, but it remains more responsive than Postman was.

Post reply on HN