The funny part is that there are APIs to avoid caching... all of which are ignored by browsers. :p
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Well you know what they say about the 2 hard problems in computing, Im not sure I can name the other :)
-
That’s really the problem :)
End of conversation
New conversation -
-
-
Not really, it’s usually the fault of the backend honestly. There is cache headers and browsers adhere to them quite ok. Haven’t had a single time where it wasn’t something the servers messed up at least.
-
Credential cache is the new fun one. Have had it with o365 a few times that something dumb like OneNote refuses to open docs on onedrive to just clear the cache in IE and things return to "normal"
- Show replies
New conversation -
-
-
Or just "fix" web as an experience...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
But then they invent ServiceWorkers and now every web app is going to have new exciting cache bugs instead of the same boring ones you're used to. You're welcome.
-
Background processes are definitely one of the four horsemen of the platform apocalypse.
End of conversation
New conversation -
-
-
Developers developers developers
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The web architecture makes sense. It's simple, really. Just that most ("full stack, senior") web devs really don't understand their tools, and keep copying other people's mistakes
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.