It's all a bunch of bored engineers looking for ways to be clever but without anyone to take ownership of the codebase.
There is absolutely no reason for the Facebook app to be so large and have so many classes. The app itself doesn't do that much.
There is absolutely no reason for the Facebook app to be so large and have so many classes. The app itself doesn't do that much.
So yeah, it's probably all dead code that's still there.
You couldn't think of a more charitable interpretation? I'm not one to care about rules but the hn guidelines on commenting are important for making sure the community doesn't eat itself alive like reddit did/does.
>The app itself doesn't do that much.
Right, but in the presentation he made it clear that it was less about what the app does and more about the number of engineers making changes to it. Given the size of their teams all making their own changes to the iOS codebase, doesn't it make sense to modularize it so they aren't tripping over each other breaking the application constantly? They don't have a dedicated iOS team and having one would bottleneck the other teams.
Well if it doesn't do that much, why are so many engineers working on it? Perhaps they have so many people working on it because they are all redoing the same stuff and not working together?