The article talks about how GraphQL is "flexible" a lot, but I kind of wish they'd spend more words talking about why that matters. Eg, if you're working on a

The article talks about how GraphQL is "flexible" a lot, but I kind of wish they'd spend more words talking about why that matters. Eg, if you're working on a new product, the odds are very good that your front ends will change pretty rapidly. At the very least, we're way more likely to A/B test application features than we are API schemas, regardless of what methodology or technology our APIs are using. Because that's why I would pick GraphQL. It's a choice that reduces the barrier to rapid iteration in the clients, but it does add backend and infra work to support it.