Security Nightmare Disguised As Optimization

GraphQL promised us a beautiful world of "ask for exactly what you need" and "no more over-fetching." Then you actually implement it and realize you've just traded REST's simplicity for a Frankenstein monster of resolvers, N+1 query problems, and a schema so complex it needs its own documentation. Sure, it sounds elegant in theory—one endpoint to rule them all! But in practice? You're writing custom resolvers for every single field, implementing DataLoaders to avoid turning your database into a smoking crater, and explaining to your backend team why they now need to understand your frontend's data requirements in excruciating detail. The real kicker? Half the time you end up fetching everything anyway because nobody wants to maintain 47 different query variations. Congratulations, you've reinvented REST with extra steps and a fancy query language.

Content H..He. Hel.. OMG! His first words. Hello World! Programmer

Content zirky 7h , 6 Awards read that he became a computer scientist after his time in the service. that means he feels it's more morally correct to kill people than program javascript Reply 4 6.5k J

Content When the employer wants you to have 6 yrs experience in Javascript, Python, Java, React, Vue, Laravel, Mongodb, Rails, MySQL, Greek History, Aerodynamics, human anatomy etc. just to manage their wordpress site.

Content MySQL OurSOL.

Content Forcing users to make their passwords longer Just switching to Webauthn-only login since basically everything supports it by now