I haven't looked at capnproto recently, but just because it solves a similar problem doesn't mean there's no room for a different system. The bespoke endpoint

I haven't looked at capnproto recently, but just because it solves a similar problem doesn't mean there's no room for a different system. The bespoke endpoint thing is a big part of what GraphQL avoids. It gives you something explorable, but as a team, you can decide how comprehensive you want it to be. If you have a monolithic database, you can use SQL to explore it, but GraphQL often sits in front of a service layer, which connects to my next point. GraphQL's mutations often map to entire processes, which might change a data store, like a DML SQL operation, but also have other sorts of effects.