3 ms·
I don't think it's fair yet to say that Twitter won't do these things. The first step was fixing the regression as fast as possible.
by gfunk911 16y ago
I don't think it's fair yet to say that Twitter won't do these things. The first step was fixing the regression as fast as possible.
- bretthopper 16y agoWell there's not much else to do. It seems other people did most of the work for them.
- jfager 16y agoAnd the second step was writing a highly-visible blog post slagging the free code they use in their many-million-dollar website before they actually understood the problem?
- weixiyen 16y agoExactly. It's not hard to pinpoint the exact line of code that is causing the slow down and come to a conclusion. This could have easily been fixed without reverting to jQuery 1.4.2 and risk breaking other things in the process (assuming they upgraded to 1.4.4 for a good reason). On top of that it was their own code which led to the slowdown. Passing the blame to jQuery seems wrong when it was their own mistake to disregard best practices. Here is where Twitter failed: 1) Need better testing when updating a version of the library. 2) Need to understand what the library you are using is doing and how to avoid performance bottlenecks. Basic stuff.