Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
retoor17533dDid you know that when @Lensflare was younger he thought everyone should do graphql? True story.
I stop trying to understand it, combining data trough some consistent interface is just our job as backender and it's weird if you have a magic query thing disabling rest and it's advantages to do with whatever you want. Let's forward an SQL with a join or something. My god. GraphQL reminds me to 1942 and German sheperds. -
@retoor tbf, I was only thinking that for a few days when I first learned about graphql and played around with it.
It’s still a good tool to know about and to have in your tool belt, but it’s widely misunderstood and not worth using for most projects. -
If this tool is used by someone who doesn’t understand it properly and doesn’t want to use it, you‘ll end up with a shit solution for everyone. A self fulfilling prophecy.
-
@Lensflare Isn't this for every framework /language in the world? If you are not doing it correctly, then it will be a pain in the ass to maintain it.
But I guess graphql is just largely misunderstood and an easy way to offload backend responsibility to the frontend. -
badger562d@antigermanist Fuck. Now my backend needs to be able to support arbitrarily complex data.
This was a bad idea. -
A 2h task for the rest of the week?
Thats what I like to call a MANDATORY BREAK.
'Hurry up and wait' might as well have told you 'take a nap at work.' -
retoor17532dWow, why had everyone 0 upvotes? Doesn't work trough the ssl-problematic version? Or is GraphQL a subject w'ere all devided on?
Related Rants

when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
I had yesterday a meeting with the backend-dev/manager. He at least mentioned that GraphQL was not the way to go and that he has no idea how to tackle certain requirements. He is planning to sit together with the internal future users to check what data is truely needed (fyi, he started the project 11 months ago).
So yeah, the project is now on hold and he assigned me a 2h task for the rest of this week; fun.
rant