Apollo Client 1.0: A flexible, community-focused JavaScript GraphQL client

Re:Apollo Client 1.0: A flexible, community-focused JavaScri... by daliwali on Thursday March 30, 2017 @06:10PM (#13999344)

This is not a knock on Apollo in particular, but I am wholly underwhelmed by what gets hyped up in this industry. There isn't anything novel here. A new generation of programmers rediscovers Remote Procedure Call (they call them mutations), schemas (NoSQL was so last year), and various older concepts and rehashes it while putting down a strawman they claim is Representational State Transfer (which if they read the thesis, they would realize that their concerns are nitty gritty details which are only tangentially related to the architecture described).

Also the community-focused angle is disingenuous. It's backed by venture capital of the Meteor Development Group and based upon a single vendor specification, GraphQL by Facebook.

[ Parent | on HN ]

Re:Apollo Client 1.0: A flexible, community-focused JavaScri... by ultimatejs on Friday March 31, 2017 @04:05AM (#14001924)

Many great open source products have huge commercial backers--the important thing is that there is a community, which is in fact very true with Apollo.

I get what you're saying and I'm sure there is lots of truth to it--that doesn't make what's going on now the best to ever do it (i.e. the fastest way to produce the most meaningful user experiences). If it wasn't the case, we'd be doing remote procedure calls in C or whatever.

Bottom line: ur point is one that should be heard, but there's a way more value could be added in how you present it.

[ Parent | on HN ]