Dominic
1 min readDec 1, 2023

--

I really despise graphql. I've ripped it out of products I've joined on, and that hasn't been hard as it has harmed velocity so much in every instance. There are technical problems (websockets, authenticating websockets, Java implementation not being fully up to spec with client JS one, performance issues, a whole layer to scale and slow down requests etc). 99% of the time there is no use case for it. I knew it would die down/out eventually and I'm usually right about those hunches. I predicted Browserify would die to Webpack, Angular would die to React, Java would die to Go and Kotlin etc. What's next? C++ to Rust? C to Zig? React to Solid? I refuse to embrace tech just because it's the assumed thing, and if it's over engineered or poorly performing it'll usually get replaced. The best thing about GraphQL is a strongly typed contract, but I'd rather do that through something like Zod/Typebox etc if possible.

--

--

Dominic
Dominic

Written by Dominic

Tech fatigue? Nope. I love reading about new frameworks and languages and dabbling

No responses yet