I have a Paw license and recently I started using Insomnia instead: https://insomnia.rest/ I find Paw's project management very annoying. It assumes that I am working on some project and wants me to organise everything like that. Fine, lets do it, so where are my projects? They are hidden in some dropdown that you can have fun finding. Insomnia is much cleaner and more to the point.
Paw – macOS HTTP client for testing and describing APIs
51–60 of 121 posts
Re: Paw – macOS HTTP client for testing and describing APIs
#52Re: Paw – macOS HTTP client for testing and describing APIs
#53I have a Paw license and recently I started using Insomnia instead: https://insomnia.rest/ I find Paw's project management very annoying. It assumes that I am working on some project and wants me to organise everything like that. Fine, lets do it, so where are my projects? They are hidden in some dropdown that you can have fun finding. Insomnia is much cleaner and more to the point.
Re: Paw – macOS HTTP client for testing and describing APIs
#54Re: Paw – macOS HTTP client for testing and describing APIs
#55Anyone have any experience with how this compares to Postman?
Check out this thread from one of the other times it was posted: https://news.ycombinator.com/item?id=12190047
Re: Paw – macOS HTTP client for testing and describing APIs
#56I have a Paw license and recently I started using Insomnia instead: https://insomnia.rest/ I find Paw's project management very annoying. It assumes that I am working on some project and wants me to organise everything like that. Fine, lets do it, so where are my projects? They are hidden in some dropdown that you can have fun finding. Insomnia is much cleaner and more to the point.
I was on the verge of buying a licence for Paw a couple of months ago, but discovered Insomnia, and been using that instead. (Formerly used Postman before that). To me, the functionality of Paw and Insomnia seem very similar, so the $50 licence price deterred me from purchasing Paw. If Paw was closer to the $20 mark, I might have still bought it to have in my arsenal of tools 'just in case'. My rationale is that if t…
Re: Paw – macOS HTTP client for testing and describing APIs
#57I have a Paw license and recently I started using Insomnia instead: https://insomnia.rest/ I find Paw's project management very annoying. It assumes that I am working on some project and wants me to organise everything like that. Fine, lets do it, so where are my projects? They are hidden in some dropdown that you can have fun finding. Insomnia is much cleaner and more to the point.
Re: Paw – macOS HTTP client for testing and describing APIs
#58For quick-and-dirty things I use cURL or httpie otherwise I use Paw (and have for about a year now). I had previously used Postman before that, but even then Paw was a better app—native app so it looked better + felt faster, nicer collections, better default shortcuts, etc. Paw has a lot of power behind it, otherwise if you're just doing basic POST requests, stick to httpie. The code generators and extensions are nic…
Just a cool feature I learnt recently.
Re: Paw – macOS HTTP client for testing and describing APIs
#59For quick-and-dirty things I use cURL or httpie otherwise I use Paw (and have for about a year now). I had previously used Postman before that, but even then Paw was a better app—native app so it looked better + felt faster, nicer collections, better default shortcuts, etc. Paw has a lot of power behind it, otherwise if you're just doing basic POST requests, stick to httpie. The code generators and extensions are nic…
Just to play devil's advocate: I do all of that in Postman, which for the last year or so has also been a native app - at least, in the sense of being non-Chrome, it's not using macOS UI elements. I think different environments is a recent feature too. It's free, and cross-platform. And the team sharing capabilities are cheaper than Paw's. It's odd that Paw seems to bill its single platform nature as a feature. There…
Re: Paw – macOS HTTP client for testing and describing APIs
#60Earlier quoted context omitted.
Just to play devil's advocate: I do all of that in Postman, which for the last year or so has also been a native app - at least, in the sense of being non-Chrome, it's not using macOS UI elements. I think different environments is a recent feature too. It's free, and cross-platform. And the team sharing capabilities are cheaper than Paw's. It's odd that Paw seems to bill its single platform nature as a feature. There…
Isn't Postman's "native" app electron-based instead of being the chrome packaged app from before? So they basically went from Chrome to Chromium and started calling it native...
Postman may or may not call it native, I did here, and then tried to clarify what I meant since I realised it's nativeness depended on context.