Honestly I wouldn’t take that too seriously, I think the whole triplet “not A, not B, not C” has been extremely common when talking about problems people are passionate about, and it’s a shame that crappy AI prose has trained people to treat it as a marker of AI. But it’s a exactly because that was effective in popular texts that AI has picked it up.
As long as the post isn’t this repeated 15 times like an AI would, just write how you want to write and most people will like it just fine. It’s a shame that we have to tone ourselves down nowadays.
This looks super cool, I’ve played around with making custom API clients/executers in multiple teams now and am glad to see something that I might actually use instead of re-rolling my own each time.
One thing I’ve previously found very useful is the ability to select multiple ‘environments’ at once (I’ve previously split this in to e.g. environment+session or environment+user before). The ability to merge a set of variables together lets you define variables for _where_ I’m calling (local, staging, etc), but also who/what I’m calling (specific users, types of profiles/packages (how does this api behave if I switch between a free vs paid licence), etc).
Also echoing another comment, the blog linked gives me a 404 page now. Additionally, the GitHub for this projects seems have a ton of blank issues saying “help yapi made me too productive”? Rather odd, I probably won’t be running this project directly anytime soon…
The EV cert system is truly terrible on Windows. Worst of all, getting an EV cert isn’t even enough to remove the scary warnings popping up for users! For that you still need to convince windows defender that you’re not a bad actor by getting installs on a large number of devices, which of course is a chicken-and-egg problem for software with a small number of users.
At least paying your dues to Apple guarantees a smooth user experience.
Honestly whilst the docs make the review process sound complicated, I went through it a few months ago and it ended up being super simple. Just follow the instructions to create the new formulae PR (and look at other recent ones) and then you’re all done. Updates are handled by a bot they run automatically when you make a new GitHub release, so you don’t even need to interact with the homebrew repo after setup.
You do have a naming conflict though unfortunately so I’m not sure how you would deal with that.
As long as the post isn’t this repeated 15 times like an AI would, just write how you want to write and most people will like it just fine. It’s a shame that we have to tone ourselves down nowadays.