3 ms·
Those two things sound like backend capacity issues, rather than frontend. The frontend as I understand it is almost all static HTML/JS. So they may be having
by mnutt 15y ago
Those two things sound like backend capacity issues, rather than frontend. The frontend as I understand it is almost all static HTML/JS. So they may be having capacity issues, but that would be true whether they stayed on the old twitter or moved to the new twitter.
- corin_ 15y agoI'm not sure what the cause is exactly, but back when they let you chose between new and old, I found that it was always slower and less reliable on the new version of the site. And it hasn't got any better since they killed off the old version.