Re:GraphQL kinda sucks
by gabereiser on Saturday August 06, 2022 @09:32AM
(#32367938)
In order to build a properly implemented one, one must first learn to build one. I find most people jump onto graphql because they see the volume of work to create crud endpoints for all of their models and decided to punt.
Re:GraphQL kinda sucks
by legalcorrection on Saturday August 06, 2022 @09:37AM
(#32367978)
It’s a false promise. You’re just moving the complexity elsewhere, into wiring this ridiculous graphql infrastructure together and making it actually do what you want in all but the simplest/tutorial-like scenarios.
Seriously. I sometimes think I'm visiting a satirical alter realm when I see these obtuse systems that end up requiring more cognitive energy to glue together than the regular version in <lang of your choice here> being praised rather than derided.
Re:GraphQL kinda sucks
by lelanthran on Saturday August 06, 2022 @10:17AM
(#32368305)
> I sometimes think I'm visiting a satirical alter realm when I see these obtuse systems that end up requiring more cognitive energy to glue together than the regular version in <lang of your choice here> being praised rather than derided.
You're lucky, you're only visiting. I'm working in that alternate reality :-)
Okay, so don't make a poorly implemented one?
Also, no, it kind of won't. Let's look at what they are again
.
"It is actually a pain to use"
Not an API characteristic
.
"you'll have to manage two or more type systems if there are no code first generates in your language"
Not an API characteristic
.
"It doesn't support map/tables/dictionaries."
Not an API characteristic
.
"No clear path for Api versioning"
Not an API characteristic
.
Looks like it's actually zero for four