91–94 of 94 posts
Earlier quoted context omitted.
It's a pretty simple library, does it need commits every month to prove that you should still use it?
code rot is a thing
Oh great, an ad that covers the entire page on mobile. Guess I'm not reading this article then.
I didn’t want to start the meta-whine about the reading experience, but as you’ve been so kind, I’ll chip in. I’m an Australian. I’m currently on holiday in Girona, Spain. Holy shit how do you people deal with these cookie notices all day?! Techcrunch covers the entire screen with something you have to click [0], and it’s hardly alone. This is insanity . Who was this meant to benefit? [0]: https://share.icloud.com/ph…
https://eu.shreveporttimes.com/story/sports/outdoors/2015/06...
Earlier quoted context omitted.
> I haven't seen a single backend framework which doesn't actively encourage an N+1 problem on any query which returns multiple objects of data Well then you haven't really looked :) https://join-monster.readthedocs.io/en/latest/ https://github.com/graphile/postgraphile https://www.prisma.io/ https://subzero.cloud/ These are all examples of tools/libs that implement a graphql api without a N+1 issue
Those are great resources. But all of them appear to be tightly coupled with a SQL storage backend. That's valuable, but what I believe the ecosystem needs is a generic system which can "pre-compile" a GraphQL query into a backend language data structure which the developer can then transpose into a database query. I think Facebook's Dataloader is more close to a solution.
OData did exactly this years ago, and got heavily criticised for giving too much querying power to the client side, as (without expert usage on the server side to whitelist the query) a client could run queries that would overload the server.
You're damned if you do, and damned if you don't.
Are there good alternatives to Apollo at all?
I write native iOS and Apollo code generation can be quite hit and miss.