3 ms·
Looking for some informed opinions here. I’ve been building web applications for over 15-16 years. Graphql was introduced a few years ago and I’ll admit, I have
by geuis 6y ago
Looking for some informed opinions here. I’ve been building web applications for over 15-16 years. Graphql was introduced a few years ago and I’ll admit, I have a default anti-Facebook derived tech opinion. I’m biased against anything that comes out of Facebook. The one exception to that is React. I’ve learned to use it extensively and while I’m not a huge fan, it does get the job done well enough.
When looking into Graphql, and having toyed with it a little, it’s never made sense to me. Always has come across as an extra layer of obfuscation and complexity when dealing with the data access later. You have to write backing sql/db queries anyway to support the Graphql layer. More efficient use of time to just write good db queries.
Is there something I’m missing here or is the world finally catching up to reality?
- tango12 6y agoWhen you say GraphQL hasn’t made sense to you, do you mean as a api consumer / frontend developer or do you mean as someone who has to build The graphql api? The benefits for api consumers and frontend developers are quite clear. Easier ergonomics to explore the API and ability to collocate data fetching alongside UI components to automatically have a graphql api client optimise the data fetching required to load a screen/page itself itself. The benefits of building a graphql api/service do seem harder to evaluate.