> Falling back to arguing about typing show me that maybe you are not aware of the many interseting ways you can get screwed or maybe you just worked on simple straightforward things.
Please provide a few examples of this.
Since I'm not going to type a novel here is an example: https://wundergraph.com/blog/the_complete_graphql_security_g...
Also look at hackerone:
> So in conclusion, you're moving the goalposts and asserting that everyone that has issues with the tech must be an idiot since it works for you.
That's not what GP asserted at all. You made some vague statements about gql, and they refuted with very concrete arguments.
Re:Migrating Netflix to GraphQL Safely
by hn_throwaway_99 on Sunday June 18, 2023 @02:49PM
(#36383124)
I didn't call anyone else an idiot. You don't actually seem to be open to hear about how people can use GraphQL, in production, to solve a host of thorny issues that "plain REST" APIs commonly have to deal with. Congrats on your intellectual superiority.
Thr fact that you're arguing that it should not be treated as a generic query language when it's in the name and this is how it's sold is hilaruous. Combinations of gql fronting rest services and dbs are even more hilarious.
So in conclusion, you're moving the goalposts and asserting that everyone that has issues with the tech must be an idiot since it works for you.