3 ms·
A couple reasons this happens in practice. OOP emphasizes encapsulation, decomposition, and dependency injection more aggressively than other paradigms. See SO
by paulddraper 3y ago
A couple reasons this happens in practice.
OOP emphasizes encapsulation, decomposition, and dependency injection more aggressively than other paradigms. See SOLID. [1] While not necessarily bad, it does result in more "pieces."
Java -- arguably holding the #1 spot for OOP popularity -- requires that each (public) class be in its own file. This results in a lot of files.
[1] https://en.wikipedia.org/wiki/SOLID https://en.wikipedia.org/wiki/SOLID