4 ms·

Remember when they had to monkey patch the android runtime because their app had too many methods? https://www.facebook.com/notes/facebook-engineering/under-the

• saagarjha 7y ago
  Remember when reached the limit for __TEXT and had to put code in sections that weren’t really meant for it: https://blog.timac.org/2016/1018-analysis-of-the-facebook-app-for-ios/ https://blog.timac.org/2016/1018-analysis-of-the-facebook-ap...? Remember when they were taking to long to start up that they pulled stuff into a separate framework just so they could meet launch deadlines: https://blog.timac.org/2017/0410-analysis-of-the-facebook-app-for-ios-v-87-0/ https://blog.timac.org/2017/0410-analysis-of-the-facebook-ap...? Remember when the app had 18,000 Objective-C classes: https://quellish.tumblr.com/post/126712999812/how-on-earth-the-facebook-ios-application-is-so https://quellish.tumblr.com/post/126712999812/how-on-earth-t...? Facebook’s teams somehow cannot manage their bloat and they keep hiring people to hack the platform they're running on rather than fixing the actual underlying problem.
  • plorkyeran 7y ago
    The root cause of the problem is that they have too many people working on it, and that's obviously not a problem you can hire your way out of.
    • saagarjha 7y ago
      Perhaps they should hire engineers who have the explicit job of ripping out things that should not belong.
      • Apocryphon 7y ago
        Or if they must insist on writing more code than refactoring it out, perhaps they should build more products.