In big and complex programs OO makes even less sense, and causes even
more harm, the difference is that in the mist of so much complexity it
is less obvious that OO is totally worthless, when in the case of a
really simple program, it becomes painful self evident that 90% of the
complexity comes from OO and there is no other scapegoat to blame.
Peace
uriel
On Tue, Sep 15, 2009 at 9:33 PM, markus schnalke <meillo_AT_marmaro.de> wrote:
> [2009-09-13 23:34] Amit Uttamchandani <atu13439_AT_csun.edu>
>>
>> Just curious as to the arguments against OO programming. All the classes
>> I have taken in uni always trumpet OO.
>
> The problem of discussions with most people about OO is that they
> simply have this different POV. They have their many-thousand SLOC
> large code blocks in mind.
>
> OO becomes senseless when your programs are small and simple.
>
> You have the separation in the operation system then. Single
> independent programs take the place of classes. You can combine them
> to larger programs.
>
> Then you have real reusability!
>
>
> But most programmers don't reach this POV, hence they keep coding fat,
> bloated software crap.
>
>
> meillo
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFKr쀮騖陾忚脡ဥ溠ਈ娴튯嘦送ϡ斪框蛂첮憠ৣ�
> E73zjU12wkhGHuKBZMFI4Kg=
> =1UfQ
> -----END PGP SIGNATURE-----
>
>
Received on Tue Sep 15 2009 - 20:03:56 UTC
This archive was generated by hypermail 2.2.0 : Tue Sep 15 2009 - 20:12:03 UTC