(1) because OOP is a theory of EVERYTHING, and every theory of everything is a theory of NOTHING.
plus it is plainly counterproductive. (a) it complicates development, makes it longer, and much more susceptible to errors. (b) it naturally conceals errors and carries them to later stages of development when programmers are strongly negatively motivated to fix anything, and it helps to conceal errors if programmers are willing to do so on purpose. (c) it resource wasteful (and it must be already known to you) (d) it is inconsistent in its own theoretical basis: every OOP language indeed FORCES you to violate "incapsulation principle" which is the most promoted "feature" of OOP. (e) it imposes very inadequate and counterintuitive data and process models.
(2) because of (1) every programmer each day must perform against common sense, and smile.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2014-05-23 11:24 pm (UTC)plus it is plainly counterproductive.
(a) it complicates development, makes it longer, and much more susceptible to errors.
(b) it naturally conceals errors and carries them to later stages of development when programmers are strongly negatively motivated to fix anything, and it helps to conceal errors if programmers are willing to do so on purpose.
(c) it resource wasteful (and it must be already known to you)
(d) it is inconsistent in its own theoretical basis: every OOP language indeed FORCES you to violate "incapsulation principle" which is the most promoted "feature" of OOP.
(e) it imposes very inadequate and counterintuitive data and process models.
(2) because of (1)
every programmer each day must perform against common sense, and smile.