GraphQL: making the impossible stuff hard, and the easy stuff impossible … 🤦

My team wants to use it for EVERYTHING. It's disgusting.

Problem isn't GQL itself, it's that they're trying to solve for a problem with the wrong solution.

graphql - cause we don’t know how to normalize our data and how model in mvc works 😅

GraphQL, just like WSDL, is a great idea that just got conceptualised horribly, AND implemented horribly.

i can, in theory, see the benefits over REST, but i've so far not encountered any project where those benefits would matter - the point where you actually want to query your backend data _that specifically defined_ is the point where "bandwith" is usually not a limitting factor at all.

Many implementations of GraphQL are tragically confusing... for everyone.

@fzammetti I believe which NoSQL has its place but when I was forced to code by hand RDBMS feature on a greenfield project which used a NoSQL DB because the management wouldn’t provide a goddamn SQL DB I wanted to kill.

I‘m working with GraphCMS and at first it looked kinda nice. Querying is ok-ish. But data upload with create/update/upserts is just horrible. Huge mutation queries noone understands, totally inconsistent, tacked-on localization support.
And the worst, no real java framewort that just gives me pojis to fill and send.
It‘s so horrible to use.
I wished they‘d have a good REST interface. Things would be so much easier 😭

@fzammetti what’s “flex”?