This twitter thread blew up on twitter yesterday and I thought I’d go over some of the author’s points in a longer format so we can clear up some misconceptions. Let’s go over them one by one…

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Twitter thread about GraphQL got a lot of attention yesterday. The author of the thread claimed that GraphQL makes your public API equal to a generic graph database. He also claimed that the amount of maintenance work is sky high and that leaving a GraphQL “open” results in infinite performance work.

GraphQL is a Trap?

Cool article resolving some misunderstandings of GraphQL, I like the points author is mentioning at the end to sum up it and the most important one is
<blockquote>
You don’t have to use GraphQL if you don’t feel the problems it was invented to solve.
</blockquote>

A reasonable explanation to the tweet that blew up well.