"Why do I need a 4Ghz quadcore to run facebook?" This is why. A single word split up into 11 HTML DOM elements to avoid adblockers.pic.twitter.com/Zv4RfInrL0
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
36K functions would be better?
A competent programmer wouldn't need a gazillion lines of code to implement FB functionality. A client app for sharing pics and messages is NOT ROCKET SURGERY.
A competent programmer wouldn't blame a programming paradigm.
That's an odd way of looking at it. Why should the paradigm be above criticism?
I don't see any criticism, do you?
Bram opened the thread by criticizing OO. Since then, precisely zero details or facts about paradigms have been discussed. So I agree, I see no criticism, just a bunch of empty snark.
You are quite right, of course. But the "detail" I highlighted was that OO *can* get you in a situation where a client-side social media app ends up with 18K classes. So I see this as an *example* where OO is the enabler for overly complex engineering.
All the paradigms can be used to create horrible things and it would still not be the fault of the chosen paradigm. This is not an example, 18k classes can be explained in dozens of ways, and your single bet is on the OOP because you don't like it. #StopRacismAgainstOOP /s
Ok, so this was a knee-jerk, and I blamed it too easily on OOP. Like others commented, those 18K classes are most likely not authored, but the output of code-gen. Still, for the mobile version at least, I think those 18K classes have something to do with perf of the client.
Doesn't really mattet what language type you use when you have to overcomplicate everything, don't clean up code and obfuscate every little detail with ten times more code than originally
The programming paradigm chosen has little to do with this... It's the project management paradigm, not the programming paradigm.
Stop putting blame on OOP. Simply put they're just trying to be a superapp for everything.
LoL. That was arguably the most irrelevant piece of nonsense I’ve read recently.
it's not "because OOP," it's "because Facebook's business model"
This isn't the fault of OOP - OOP is just a tool, like any other. This is insane usage of the tool by people who don't understand HOW to use it. I bet you could refactor 85% of those objects out.
Because 18k class instances are operating on the stack at once 
I don't see how their poorly designed software is the fault of OOP?
Lol don't try to blame this on OOP, man. You can write just as shitty code with FP or whatever your favorite paradigm is. Don't be so naïve.
I have a CS degree and also have a strong distaste for OOP but you're really off the mark here. JS is prototype-centred OOP. There is no clear distinction between classes and instances in JS as there would be in, say, Java.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.