Ha, I almost said trunk ;) Completely agree though. I’m currently on a project that using a JSON response hit the max response size limit regularly (this was a while ago). We have to transport a lot of data in a live environment, so we ended up dropping the JSON aspect and went to a direct binary connection from the client to a Graph database. I suspect we could have survived with a GraphQL implementation. “trimming the fat” is a great way to put it. And it’s one of my passions on every project I work on. “Can this be smaller/tighter/faster?”
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.