4 ms·
Brian's conclusion seems to be that Facebook is failing at something. I think the more proper conclusion is that Facebook's audience doesn't care about this st
by jfarmer 18y ago
Brian's conclusion seems to be that Facebook is failing at something.
I think the more proper conclusion is that Facebook's audience doesn't care about this stuff.
Facebook is still growing at a break-neck pace. Why should they dedicate resources towards speeding up their site unless there's strong evidence it will help them achieve their strategic goals?
- bkrausz 18y agoThe problem is that they are just now beginning to focus on their overseas presence, with translations and such, and statistically there are many more people with slower internet connections over there. It's safe to assume that anyone at a university has a broadband connection, but that is no longer who they are targeting.
- blader 18y agoJust asked somebody at Facebook who works on this stuff - apparently they do care and it is a balance between a giant freaking download or increasing HTTP requests. There is also the issue of redownloading a giant file whenever a small piece of JS changes on the site, which can happen quite happen. They've also profiled the browser performance itself and found that loading all their JS in-memory is actually a performance issue. So I guess the answer is that they've really thought this through and came up with the best solution that works for them.