11 ms·
I see entire massive threads requested and responded in a single compressed call to /api/graphql/xxx/TweetDetail Loading an entire next page is also a single c
by ev1 4y ago
I see entire massive threads requested and responded in a single compressed call to /api/graphql/xxx/TweetDetail
Loading an entire next page is also a single call to the same endpoint. There is nowhere remotely that I see the mobile client even making a hundred gql calls for tweets.
Is there something I'm missing or is he misusing "app" when he means backend service to service GQL calls?
- nuc1e0n 4y agoWould the UX concept of a 'next page' even make sense if the content doesn't get read by the end user? What would an app that's mindful of the unavoidable technical limitations look like I wonder? I'm not familiar with the specifics at hand or what Musk can see, but from my perspective he has first hand knowledge of web dev and is smart enough to not be blinded by buzzwords and dogma. He seems to have earned a decent living from his approach don't you think?
- nuc1e0n 4y agoIf there's a problem sending too much data between back end services, perhaps there's just more data being sent than necessary. Perhaps there's some data usage costs or introduced latencies involved somehow?