pull down to refresh

136 sats \ 1 reply \ @ek 8h \ parent \ on: Stacker Saloon
I agree that it could be nice for rapid development in an ecosystem around a central service - iirc that's what FB developed it for
Yes, and I think they also developed it for mobile because GraphQL also improves bandwidth since you can select exactly what you need, not more, not less. I think I heard that in here:
It's also funny that the caching is killing my experience with this particular web-ui because I need to literally hit refresh when navigating (using in-app navigation) to see new state on an issue - so in this instance it's also kind of awfully implemented.
yeah caching is hard for real haha, we also had many issues with our caching, but maybe it's just a "skill issue"
write
preview
0 sats \ 0 replies \ @optimism 17m
since you can select exactly what you need, not more, not less.
That's a benefit; there is something similar in bitcoind for getblockstat.
maybe it's just a "skill issue"
I don't think so. Cache expiry / cached state transition is hard and really easy to get wrong, I can't remember a single instance where it was easy to make it smooth - and then I'm talking about back-end caching, which is easier than on the front-end.
I think that caching is hardest to consistently deliver when you are still rapidly adding or refactoring features/API, but you could design to overcome that by abstracting the mechanism.
reply