What is interface bloat?

Question

Can someone explain to me which interface is bloated in OOP (preferably with an example).

Answer 1

G'day

Assuming you mean the API, not the GUI, for me, I / F bloating can happen in several ways.

• The API simply continues to expand and expand with new features without any form of segregation, so you end up with a monolithic header file that becomes difficult to use.
• Functions declared in an existing API continue to add new new parameters to their signatures, so you need to continue updating, and existing applications do not support backward compatibility.
• API , , .

, :

• API , , . , , . wibble.h, API, shozbot.h.
• API , , . , . API, our_api.h, , , SOA, our_api_soa.h our_api. .

Answer 2

OO, Object, . .

Answer 3

Microsoft?

, , . , - , , Basecamp 37signals. .

bloat (, Javascript) , , .

Answer 4

- , , , , , .. , . , , iTunes. , , , (iTunes DJ, Coverflow, Genius).

Answer 5

, :

( , Firefox, )

, " ", . . , - , , . .

Answer 6

:

http://img46.imageshack.us/img46/5127/ofilematrix.png

Answer 7

An extreme example of an interface bloat that will be used by most C ++ programmers is this std::basic_string. Page up and down pages of member functions with slight variations, most of these functions were not supposed to be member functions, but could be free functions in the string library.