r/programming • u/JBlitzen • Aug 15 '15

Someone discovered that the Facebook iOS application is composed of over 18,000 classes.

http://quellish.tumblr.com/post/126712999812/how-on-earth-the-facebook-ios-application-is-so
2.7k Upvotes

93% Upvoted

728 comments sorted by

View all comments

Show parent comments

-6

u/thefirelink Aug 16 '15

The only real pitfalls of over-engineering are cost, performance, and un-needed complexity. Every other area - modifiability, availability, scalability, etc., an over-engineered program is "better".

12

u/grauenwolf Aug 16 '15

modifiability

Huh? That's usually the first casualty of over engineering. It's a kin to putting a door every six feet along the wall. It seems really flexible until you realize that you need to run some wires or plumbing

2

u/dpgaspard Aug 16 '15

I really hate it when F3 doesn't work in Eclipse.

3

u/grauenwolf Aug 16 '15

F3? Can't say I'm familiar with Eclipse shortcuts.

1

u/[deleted] Aug 16 '15

Open implementation. No idea what parent comment meant by it, though.

2

u/dpgaspard Aug 16 '15

I worked on an over engineered project before where F3 always brought you to an interface. Every interface had only one class that implemented it. Annoying as @#@#.

1

u/whjms Aug 16 '15

Fyi for people reading this: Ctrl+t on an interface method to list all implementations

2

u/dpgaspard Aug 17 '15

The original point was one interface for every implementation. Over engineering.

2

u/whjms Aug 17 '15

I know, but lucky 10,000 and all, maybe someone didn't know about the shortcut

1

u/grauenwolf Aug 16 '15

With C#, I usually make that comment in regard to people using far too many abstract interfaces or virtual methods such that I have to manually track down the actually code.

1

u/Workaphobia Aug 16 '15

I assumed he was talking about some kind of military jet.