Why Twitter didn’t go down: From a real Twitter SRE

Re:Why Twitter didn’t go down: From a real Twitter SRE by mgkimsal on Tuesday November 22, 2022 @04:35AM (#33703841)

The other side of that is browsers. Even if you don’t change your code, the platform people are running your code in changes, automatically in many cases. New JS or CSS behavior in next safari or chrome? You need to patch/push to accommodate running environments that are outside your control.

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by christophilus on Tuesday November 22, 2022 @05:07AM (#33704071)

The old space jam site worked for ages, and would still work if they hadn’t taken it down. The web is pretty good about keeping backwards compatibility.

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by efreak on Monday November 28, 2022 @04:50PM (#33780326)

Except the original hamster dance, which doesn't display correctly

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by vasergen on Tuesday November 22, 2022 @09:05AM (#33705873)

JS in fact has very good backwards compatability, this is by the way the reason why "old stuff" are not removed and are still in the language.

[ Parent | on HN ]

Re:Why Twitter didn’t go down: From a real Twitter SRE by bdcravens on Tuesday November 22, 2022 @09:32AM (#33706180)

Sounds like a good argument for minimal Javascript.

[ Parent | on HN ]