peggyrayzis

Congrats on the launch! I recently tried InsForge for a personal project a few weeks ago and thought the getting started experience was really smooth.

Which one do you continue to reach for the most? I was surprised to see Gemini so low on your list even w/ the long context window.

Hi from the Apollo team! We're not abandoning open-source software. Excluding our Federation 2 libraries, nearly all of the 100+ public repositories in the Apollo GitHub organization are MIT-licensed. Our most popular projects, including Apollo Client (Web/iOS/Android), Apollo Server, apollo-rs, and Rover, remain MIT-licensed.

Federation 2, the component of our platform that is licensed under ELv2, is most interesting to large enterprises. Apollo has built a successful business that helps developers at large enterprises adopt a unified graph at scale. These enterprise subscriptions fund the development of important open-source projects like Apollo Client and Apollo Server that benefit the entire graph ecosystem.

Hi from the Apollo team! We hired a mobile engineer who is starting within a few weeks. Keep your eyes out for lots of exciting improvements to Apollo iOS soon!

The normalized cache is the one of the main value props of Apollo Client. It optimizes reads, automatically updates queries without a refetch for some mutations, supports optimistic updates, and can also return partial data for large queries. If you don't need a cache, then you can use fetch, graphql-request, or even Apollo Link to fire off a simple GraphQL request. You also don't have to use our cache implementation (apollo-cache-inmemory) with Apollo Client. There are other implementations that make different tradeoffs.

For what it's worth, we are rearchitecting parts of the cache to support invalidation and garbage collection for Apollo Client 3.0. The only reason why we don't have it yet is because it's a tough problem to solve - one mutation could invalidate an infinite amount of queries. We're committed to solving this soon though because we know the community really wants it.

Thanks for the thoughtful response, this is all helpful feedback that I will share with the team.

It's been on my backlog for a while to rewrite the Apollo Client intro section to give developers the high level overview you're looking for. Now that Apollo Federation is out, I have some time on my calendar to do exactly that. :) Would you be open to reviewing the new section once it's done? If you're interested, send me an email at peggy [at] apollographql.com.

If it's still confusing after that, then we can chalk it up to a problem with the library. I suspect that it's a docs problem since the intro hasn't been overhauled since I joined the company almost 2 years ago.

Hi from Apollo! My team (Developer Experience) is responsible for making sure you can find what you need in the docs. What improvements would you like to see?

Hi from Apollo! We appreciate your honest feedback. Part of my team (Developer Experience) is responsible for our documentation. What features are inadequately documented? We'd like to fix that for you if we can.