Follow

Being forced to interact with a GraphQL API as part of a task in my dayjob.

What. Is. This. Nightmare.

Problem: there are N standards for fetching data from APIs and they are all clunky and complex.

Solution: invent GraphQL

New problem: there are N+1 standards for fetching data from APIs and they are all clunky and complex.

@danirod GraphQL is horrible to use and implement. I understand the need for public APIs (asking the data you want and not making many requests), but in most cases it's misused

@danirod gotta admit the apollo graphql tooling is pretty great though. caching and subscriptions and stuff.

Sign in to participate in the conversation
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.