The article is talking about art in promo material.
Think about it: whenever you see a piece of production art featured in a social media post or a press release or a game announcement at a big televised showcase, all you ever see is the art. You never know who made it, whether it was created by an individual or a small team (or even a studio).
Two different concepts.
You're talking about work slowing because of increased overhead from more people needing to communicate and make decisions.
The OP is talking about the"bus factor". How many people can leave the project unexpectedly and still have the project survive. E.g. if only one person has access to merge changes, the bus factor is 1 regardless of how many people actively contribute.
(another pet peeve of mine is "rest" APIs that use 200 response codes for everything)
Yup, also some APIs use GET for everything. It's a pain. And it means that filtering by verb only helps if you're intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you're developing the API yourself.
It's hard to prove the blanket statement, "there are no good reasons to have a private jet." But it's easy to prove, "one overpaid person taking a private jet to commute 1000 miles is frivolous."
No. As a general rule with all software, you purchase a license to use the software, not the actual software itself. That being said, GOG and Itch.io can't yank games that you've already downloaded. I don't know if Steam does or not, but it probably can.
The only one I think is reasonable is GraphQL. But that isn't rest, and HTTP is just one of the transport layers it supports.
For anything claiming to be RESTful, it's a crime.