Don't CORS restrictions basically render this whole tool useless?
[deleted]
Show HN: I created Postwoman, an online, open-source API request builder
11–20 of 110 posts
Re: Show HN: I created Postwoman, an online, open-source API request builder
#12> I use a low-end PC and can't possibly afford to run another Electron app
> That's why I created my own API request builder with pure JavaScript (I used Vue.js) + HTML + CSS
So... the only differences are not running this as a separate process and NIH?
Re: Show HN: I created Postwoman, an online, open-source API request builder
#13Earlier quoted context omitted.
It seems the user created this because they thought that Postman required too many resources as an Electron app. I'm not sure why they didn't just use a commandline tool (e.g. httpie [1]) that would work with any API, rather than just those with permissive CORS headers. [1]: https://httpie.org/
So Postman used to be a lightweight Chrome plugin. Then its developers turned it into an electron app with lots and lots and lots of features. They did this as a vehicle to begin offering paid features and enterprise plans. To your second point, despite years of writing Curl some times its nice to have an interface and for some people that is their personal preference.
Another reason why they moved to Electron may be that Google announced [0] in 2016 that they will discontinue Chrome Apps (outside of Chrome OS).
[0]: https://blog.chromium.org/2016/08/from-chrome-apps-to-web.ht...
Re: Show HN: I created Postwoman, an online, open-source API request builder
#14> I use a low-end PC and can't possibly afford to run another Electron app > That's why I created my own API request builder with pure JavaScript (I used Vue.js) + HTML + CSS So... the only differences are not running this as a separate process and NIH?
Presumably lower memory usage due to not running in a separate process. On a low-end PC this is a completely valid concern. Chrome is memory hungry. Running one instance might be viable. Running 2, 3 or 6 probably isn't (and you can always choose a less memory-hungry browser).
Re: Show HN: I created Postwoman, an online, open-source API request builder
#15> I use a low-end PC and can't possibly afford to run another Electron app > That's why I created my own API request builder with pure JavaScript (I used Vue.js) + HTML + CSS So... the only differences are not running this as a separate process and NIH?
Presumably lower memory usage due to not running in a separate process. On a low-end PC this is a completely valid concern. Chrome is memory hungry. Running one instance might be viable. Running 2, 3 or 6 probably isn't (and you can always choose a less memory-hungry browser).
If performances are a concern I would build it in QT, not Javascript. Just opening Firefox eats like 400 MB ram on my PC !
Re: Show HN: I created Postwoman, an online, open-source API request builder
#16Re: Show HN: I created Postwoman, an online, open-source API request builder
#17Opening the link I was hoping that this would be a postman with better support for file uploads. I have a long lived desired to be able to have postman request which embeds a file to upload. I really like postman features and UX but when I need a test suite for a file upload endpoint it doesn't match.
Tried several hacks to achieve to embed files but none worked. If the endpoint supported Content-Transfer-Encoding it would be kind of easy to do.
Re: Show HN: I created Postwoman, an online, open-source API request builder
#18Opening the link I was hoping that this would be a postman with better support for file uploads. I have a long lived desired to be able to have postman request which embeds a file to upload. I really like postman features and UX but when I need a test suite for a file upload endpoint it doesn't match. Tried several hacks to achieve to embed files but none worked. If the endpoint supported Content-Transfer-Encoding it…
If you're on macos, you want https://mmattozzi.github.io/cocoa-rest-client/
Re: Show HN: I created Postwoman, an online, open-source API request builder
#19Earlier quoted context omitted.
Presumably lower memory usage due to not running in a separate process. On a low-end PC this is a completely valid concern. Chrome is memory hungry. Running one instance might be viable. Running 2, 3 or 6 probably isn't (and you can always choose a less memory-hungry browser).
If performances are a concern I would build it in QT, not Javascript. Just opening Firefox eats like 400 MB ram on my PC !
It makes me question, is there any way to run a slim browser for these kind of tools?
It would be cool to have a tool that would: * run a very slim browser tab for each tool * I cloud load/save sites into tools (So I can really run them offline) * Could have a shortcut or a starting page that's just links to my saved tools
Re: Show HN: I created Postwoman, an online, open-source API request builder
#20I'm just a user of this, but if anyone is looking for a truly native MacOS version of Postman, you should take a look at Paw.