4 ms·

I see a lot of hatred in the comments towards GraphQL. Is someone forcing you to use it against your will? I've been using it for more than a year with TypeScr

I see a lot of hatred in the comments towards GraphQL. Is someone forcing you to use it against your will? I've been using it for more than a year with TypeScript types generation and couldn't be happier. All of my interactions with the server are properly typed and haven't had a single bug related to server/client missmatches.

serverholic 6y ago
There are a bunch of elitists on here who get off on hating popular things. I find it amusing that some of the comments are basically "Why use graphql when I can combine these 5 other technologies to do the same thing?"
- ehutch79 6y ago
  It's not graphql that's the issue. it's another tool. It's the fanboys, and more the people selling tooling. There's a guy who (was?) over at graphqleditor.com that was posting a whole bunch of articles, at least one of one said it was a mistake not to convert all your shit to graphql immediately.
tylerchilds 6y ago
> Is someone forcing you to use it against your will? I mean, kind of? My problem with GraphQL isn't necessarily GraphQL itself, but with the sprawl of things creeping further and further into client-side code. As companies are finding GraphQL to "unlock greater developer productivity", it's becoming more and more expected to have this in our toolkit as "front-end people". There's been a few blog posts recently that I relate to. I feel like I'm at a point in my career where I could "knuckle-down and get good" but I don't actually want to get good at more and more endless technologies. I'd rather be able to define my niche specialization and thrive within that space. [1]: https://bradfrost.com/blog/post/front-of-the-front-end-and-back-of-the-front-end-web-development/ https://bradfrost.com/blog/post/front-of-the-front-end-and-b... [2]: https://www.trysmudford.com/blog/i-think-im-a-design-engineer/ https://www.trysmudford.com/blog/i-think-im-a-design-enginee... [3]: https://notes.baldurbjarnason.com/2021/02/20/the-layers-of.html https://notes.baldurbjarnason.com/2021/02/20/the-layers-of.h...
deleted 6y ago
[deleted]

serverholic 6y ago

There are a bunch of elitists on here who get off on hating popular things. I find it amusing that some of the comments are basically "Why use graphql when I can combine these 5 other technologies to do the same thing?"

ehutch79 6y ago
It's not graphql that's the issue. it's another tool. It's the fanboys, and more the people selling tooling. There's a guy who (was?) over at graphqleditor.com that was posting a whole bunch of articles, at least one of one said it was a mistake not to convert all your shit to graphql immediately.

tylerchilds 6y ago

> Is someone forcing you to use it against your will? I mean, kind of? My problem with GraphQL isn't necessarily GraphQL itself, but with the sprawl of things creeping further and further into client-side code. As companies are finding GraphQL to "unlock greater developer productivity", it's becoming more and more expected to have this in our toolkit as "front-end people". There's been a few blog posts recently that I relate to. I feel like I'm at a point in my career where I could "knuckle-down and get good" but I don't actually want to get good at more and more endless technologies. I'd rather be able to define my niche specialization and thrive within that space. [1]: https://bradfrost.com/blog/post/front-of-the-front-end-and-back-of-the-front-end-web-development/ https://bradfrost.com/blog/post/front-of-the-front-end-and-b... [2]: https://www.trysmudford.com/blog/i-think-im-a-design-engineer/ https://www.trysmudford.com/blog/i-think-im-a-design-enginee... [3]: https://notes.baldurbjarnason.com/2021/02/20/the-layers-of.html https://notes.baldurbjarnason.com/2021/02/20/the-layers-of.h...

deleted 6y ago

[deleted]