Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
51–60 of 122 posts
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#52How does it compare to mitmmitmproxy2swagger? https://github.com/alufers/mitmproxy2swagger
The first and immediate difference for me is the ability to recall the name. I can recall Postman/Insomina fine, and now for API Parrot. I'm never going to be able to recall mitmproxy2swagger. Unfortunately, names matter.
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#53Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#54Very sad half the comments are asking for MacOS app. The rise of development on MacOS for server development when the final target is Linux will cause long term harm to the newer generation of engineers
Besides, most devs doing web development on Macs are also using Docker, which is always Linux.
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#55There is also bunch of JSON schema stuff nowadays.
But yeah for a lot of people schema of API contracts feels like too much work and too much hassle.
JSON serialization doesn’t throw errors for new properties quickly added on sending side and receiving side can ignore stuff - well as long as API semantics allow but that’s generally going to be a hassle always even with LLMs somehow autofixing your „schema”.
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#56How does it compare to mitmmitmproxy2swagger? https://github.com/alufers/mitmproxy2swagger
The first and immediate difference for me is the ability to recall the name. I can recall Postman/Insomina fine, and now for API Parrot. I'm never going to be able to recall mitmproxy2swagger. Unfortunately, names matter.
It is a bit frustrating when a project on GitHub doesn't have good tags or searchable keywords, making it harder to find.
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#57Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#58Earlier quoted context omitted.
Why? I mostly code on Mac and deploy on Linux (or FreeBSD). Never really encountered a situation where programming a web app on Mac has caused issues when deploying to the server.
What about issues with CPU architecture?
My experience is that having a team with mixed platforms has helped reduce deployment woes, with the rare platform-specific bugs getting worked out beforehand.
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#59Earlier quoted context omitted.
The first and immediate difference for me is the ability to recall the name. I can recall Postman/Insomina fine, and now for API Parrot. I'm never going to be able to recall mitmproxy2swagger. Unfortunately, names matter.
Thanks 1a527dd5.
Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
#60Feedback: add a newsletter form to get notification when you will release the MacOSX version
I've added a newsletter sign-up form at the bottom of the webpage: https://apiparrot.com/#newsletter
Feel free to subscribe to receive notifications when we release the MacOSX version.