You mean that a company that employs 10 devs for 60k (way below real salary of US companies - that the pledge is focused at the moment) which is 600k is not able to pay additional 20k to various maintainers, that will not even get entire 20k just just a small percentage?
In context of APIS, "async" communications means event notifications and message queues: Amazon SNS/SQS, Amazon Kinesis, Azure Event hub, Kafka, RabbitMQ etc. Anything where you send a message and don't wait for a response, unlike http.
Minor correction to what I said. Async means we do not keep someone/something waiting for response. There are so many options on the implementation as you described.
OpenAPI can be used to describe the vast majority of extant APIs in the wild today. It was build to describe APIs. AsyncAPI, like GraphQL, imagines a new ecosystem. This article constructs straw man arguments against OpenAPI without making a particularly concrete case for AsyncAPI.
The vast majority of extant public APIs in the wild today. Internally, people write a lot of services that process records from Kafka topics, SQS queues, emails, file uploads, etc. The ecosystem already exists and is in need of tooling.
> This article constructs straw man arguments against OpenAPI
I don't see that at all, and why would they? AsyncAPI is leveraging OpenAPI's status as a de facto standard tool for synchronous REST APIs to promote itself as a complementary standard tool for async APIs. It wouldn't benefit them to denigrate OpenAPI.
Noone is against OpenAPI, definitely on the author, thing is that OpenAPI is just not for everything and AsyncAPI complements the rest. AsyncAPI doesn't have to imagine anything, ecosystem is already there :) MQTT,Kafka, Websocket and others were there long time before AsyncAPI. I recommend you look at the article once again.
very depends on your use case and what you want to achieve in the end. Code gen? types gen or entire app? docs only? discovery? It always all depends :)
Can you share how many spam PRs did you have? I thought to check here https://github.com/chartjs/Chart.js/pulls on my own but unfortunately you did not mark those with invalid or spam labels. For such a popular project like yours, did you get many? Was it overwhelming?
To be honest, I was expecting a lot worse. There were a few that we allowed in that were in a grey area though. 3 or 4 small PRs fixing typos in the docs that really should have been a single PR, but since it was actually improving things I let it slide.
we should also take into account that world is huge and English is used by many people around the world, non-native like me and they make mistakes not because they want to do it but because they just happen. And yeah, I wrote the title with a spelling mistake, without checking it as I was sure it is written properly and my Grammarly plugin doesn't support checking the title of the submission.
So don't overcomplicate things :) and sorry for the mistake, I'll do better next time.
