Having done this recently, I think I can explain. For most techs the documentation or website for that tech explains the simplest use case. For graphql, from y

Having done this recently, I think I can explain. For most techs the documentation or website for that tech explains the simplest use case. For graphql, from your example, the guide for graphql is really clean and thorough and doesn’t depend on you knowing anything else. But it’s also completely useless when it comes to implemention for the average user, who probably doesn’t want to design a graphql server and frontend from scratch. Implementation is where the work is, and it can be very difficult to implement a working example in a real application (which often have more complicated things going on). With graphql, you won’t be able to experiment with it without both a backend and a frontend. By necessity that means you need a server (express or tails or whatever) and you’re probably using React or something similar in the frontend. JS in particular is also kind of a mess in terms of ecosystem. That’s a whole other can of worms.