Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

After 6 years, I'm over GraphQL

bessey.dev

Post reply on HN
Print view View original

31–40 of 721 posts

Re: After 6 years, I'm over GraphQL

#31

Post by dgb23 »

romanovcode wrote: post #10
oksteven wrote: post #8

Earlier quoted context omitted.

agree, it solve problem at FB for sure, that is a good point.

Same with Redux. Solved problem in FB. Increases complexity tremendously for 90% of other websites. I remember seeing the tutorial being showed in Todo app and thinking "wtf is this garbage needed for here". I'm glad Redux hype train is over and nobody is using it on new projects no more.

I think the hype is mostly over because of useReducer. It's the simplest thing that lets you structure your code in the way you want if you'd had chosen Redux (or similar).

Re: After 6 years, I'm over GraphQL

#32

Post by RedShift1 »

jamesrr39 wrote: post #6

I agree with the article, and want to add on that the browser network debugging tools are a pain to use with GraphQL (every request to /api/graphql, can't even quickly filter by endpoint name). I landed instead on OpenAPI, which can feel like a bit of a hoop to jump through sometimes when writing endpoints (but then, so can GraphQL), but the result is equally nice. And it's much easier to get authorization right with…

For the browser network debugging tools: I'm using the Apollo GraphQL client and added a link that adds the operation name into the URL. So my URLs look something like "/graphql?op=getStuff" and my GraphQL queries: "query getStuff { ... }"

Re: After 6 years, I'm over GraphQL

#33

Post by 9dev »

tomlong wrote: post #21
UweSchmidt wrote: post #18

Earlier quoted context omitted.

What if Facebook wanted to open up parts of the site for users without an account, would that require a major reengineering? I've wondered why Facebook (and Instagram) are so strict about not showing anything to logged-out users, could technical reasons be part of that decision?

I think this currently exists in some shape or other, I don’t have a facebook account but I can click on profiles of businesses and get their opening hours and pictures of their menus or whatever. In think there must be some stuff with a public context.

My guess would be they SSR those pages and partially hydrate the page on the client if the user is logged in.

Re: After 6 years, I'm over GraphQL

#35

Post by ozim »

thom wrote: post #20

GraphQL always felt to me like it solved the easy part of the problem and offered nothing to solve the hard part. I have a similar response to things like Zanzibar. At the end of the day I want to go and get some stuff out of a database, and that complexity just ends up dominating everything.

That is for me gut feeling about AI .. but that is not discussion about that topic.

So in general had the same feeling about graphQL because I still had to write layer of code that gets stuff from database, get it limited or paginated. Maybe once you have enough endpoints then you can change your front end against already existing GraphQL - but for me that was never the case as 90% of work is adding new tables, new endpoints so graphQL feels like additional work with additional footguns for almost no benefits.

Re: After 6 years, I'm over GraphQL

#36

Post by SantiagoElf »

Never bothered to learn GraphQL - anything being pushed by big tech companies usually in 80% of the cases works for them, but its an overkill for smaller scale projects.

Stick to tried and true - monolith, asp.net, angular or blazor front-end, relational database.

Re: After 6 years, I'm over GraphQL

#37

Post by etimberg »

Aeolun wrote: post #29

Can only agree with author on all points. GraphQL was nice for the types, and precious little else. But we have better solutions utilizing just the types now, so it was still valuable.

IMO even the types are annoying because null is opt-out rather than opt-in

Re: After 6 years, I'm over GraphQL

#39

Post by FrustratedMonky »

lpapez wrote: post #25

Kudos to the author for reevaluating his opinion and changing heart on a technology he admits to have championed before. IMO GraphQL is a technological dead end in much the same way as Mongo is. They were both conceived to solve a perceived problem with tools widely adopted at the time, but ended up with something which is even worse, while the tools they were trying to replace rapidly matured and improved. Today Ope…

Curious, I hadn't heard that take on Mongo. Do you have a link to some more info on this.
Post reply on HN