twitter: how many levels of high-risk javascript bloat are you on? facebook: like,, about 240 meg and two subframes for the home page right now, my dude twitter: you are like a little baby, watch this twitter: <expanding a tweet from the main timeline locks up the tab>
-
-
honestly this conspiratorial mindset seems like the only sensible explanation that 10% of the time the tweet input will get so slow, presumably from memory leaks, that I'll have to refresh the page
-
at the least it's plausible explanation of why Twitter might not be prioritizing a bugfix: "we can't fix this known memory leak because our advertising analytics numbers will go down and management will think we screwed something up"
-
it kinda fits enough that I'm not 100% sure I'm just being paranoid. the other thing is it's probably relatively hard to fix, very multi-faceted problem touching a ton of code, and generally not worth it cuz page refresh is a thing so what's the problem really?
-
yes true. but we mustn't let those voices of sense in our heads win out!
-
I would never, lead with paranoia, renegotiate to reason only under duress.
End of conversation
New conversation -
-
-
smdh, that’s offensive
-
ok I don't know about the ads thing, that's me being paranoid and snarky. the memory leaks are real though.
-
it’s the memory usage I find most offensive. I’m old enough that a 16KB memory expansion cartridge was a big deal
-
we’ve got all these amazing resources thesedays and so much it gets pissed away
-
counterpoint: computer hardware and electricity and bandwidth are all relatively cheap. we could do better but there's not enough utility in actually doing better so we settle at this mildly-disappointing but high utility equilibrium point.
-
yeah, I know that’s how it is, but is still breaks my old-school heart
End of conversation
New conversation -
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.