Live data from Hacker News

Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

apiparrot.com

41–50 of 122 posts

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#41

Very 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

I agree, people don't realize the value of not depending on a single company to do their work. We can see this problem even more with LLM code generators.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#44

Earlier quoted context omitted.

Not sad at all! Mac has excellent hardware, excellent reliability, excellent day to day performance. Im not a fanboy, but it won for (IMHO) clear and obvious reasons. Of course folks want a mac app. No comment on the “harm” bit.

It is always amazing to me people who will chastise people for using Macs. It is by far the most robust hardware and 15 years later Windows laptops may finally be catching up. My first programming job was LAMP so I had a Linux desktop and loved it. Later I got a new job that gave us laptops, but they were quite beefy. I had a Dell laptop with an Nvidia GPU and an Intel iGPU... After updating my OS my gpu was the only…

Macbooks have been nice since M1 era, but the Intel Macbooks between years 2013-2020 were hardly robust. My partner's 2014 MBP Retina's screen plastic film started peeling off, which was a known design flaw of those models. Later the ones with butterfly keyboard were notoriously unreliable, with keys getting stuck.

Personally I haven't had much trouble with Linux on modern Thinkpads. Very little to configure manually, as long as you pick the right distro. Even a Dell laptop at work with Linux isn't causing me much OS-related issues, although battery life sucks.

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#45

Very 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

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?

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#48
post #38

How 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

#49

Earlier 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?

When you write web code you should never have to worry about that. Actually, if you write any user space code, except drivers, you shouldn't have to worry about that. If you have to worry about it, reconsider your tooling very seriously

Re: Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs

#50

Earlier 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?

Yes, when you write web apps in x86 assembly, it gets tricky.
Post reply on HN