Hi there, Apollo Client maintainer here!
Great to see more GraphQL projects sprouting out there :)
If I may ask, are there any things that are currently missing in Apollo Client to be a good match for Svelte or SolidJS? If there are things we can improve, I'd be happy to know!
Hi! Thanks for reaching out! Glad to see someone from Apollo. I don't have much experience with Apollo Client in web frameworks (I've mainly used it in Kotlin), so I can't speak to the Svelte/SolidJS integration specifically.
From my observation in the community, I think one challenge is that Apollo Client has a perception of being too enterprise-focused and heavy for beginners. This might make some developers hesitant to try it for smaller projects or when they're just starting with GraphQL.
Huh, that's an interesting take - honestly I don't really know what to do about that :/
It's definitely not our intention to send that message - Apollo Client should be a good fit for everybody.
The biggest adoption hurdle I could think of is that we only offer a normalized cache.
From what we're seeing everybody sooner or later has a good use for it, and switching from a non-cache solution to a normalized cache can cause a lot of pain when it's done too late, so we don't give people the "without" choice from the start.
That said, I've been looking at your docs, and you seem to make any kind of cache completely optional. That's a bold move the other direction ^^
I'll be keeping an eye out on how people start using that :)
Make sure to stop by the GraphQL Discord - most of the maintainers of the different cache libraries are over there and we're always up for a chat!
lead engineer of unchained engine here. still using apollo client for client projects but i stopped using apollo server because you guys started to put important security features behind your paywall for example whitelisting persistent queries (pql). that makes it difficult trust-wise.
Hi there, Apollo Client maintainer here! Great to see more GraphQL projects sprouting out there :)
If I may ask, are there any things that are currently missing in Apollo Client to be a good match for Svelte or SolidJS? If there are things we can improve, I'd be happy to know!
Hi! Thanks for reaching out! Glad to see someone from Apollo. I don't have much experience with Apollo Client in web frameworks (I've mainly used it in Kotlin), so I can't speak to the Svelte/SolidJS integration specifically.
From my observation in the community, I think one challenge is that Apollo Client has a perception of being too enterprise-focused and heavy for beginners. This might make some developers hesitant to try it for smaller projects or when they're just starting with GraphQL.
Huh, that's an interesting take - honestly I don't really know what to do about that :/
It's definitely not our intention to send that message - Apollo Client should be a good fit for everybody.
The biggest adoption hurdle I could think of is that we only offer a normalized cache. From what we're seeing everybody sooner or later has a good use for it, and switching from a non-cache solution to a normalized cache can cause a lot of pain when it's done too late, so we don't give people the "without" choice from the start.
That said, I've been looking at your docs, and you seem to make any kind of cache completely optional. That's a bold move the other direction ^^ I'll be keeping an eye out on how people start using that :)
Make sure to stop by the GraphQL Discord - most of the maintainers of the different cache libraries are over there and we're always up for a chat!
lead engineer of unchained engine here. still using apollo client for client projects but i stopped using apollo server because you guys started to put important security features behind your paywall for example whitelisting persistent queries (pql). that makes it difficult trust-wise.