Re: How's dot.net doing nowadays?

MM wrote:

And a non-OOP program can be a simple solution that works. That's how
many programs once were written. Successfully. No wonder most of your
developers have problems with OOP. OOP is a curiosity for the
laboratory only. It bears no resemblance to how humans actually think.
I take it your programmers are not daft? Then you have to answer the
question, WHY do they find it so arcane and non-intuitive? There has
to be a reason, and the reasons are, OOP is too up itself, too
obscure, too overblown, too excessively zealous, too inflexible.


I find the notion that OOP is too up itself, etc. to be odd, since it is you
that decides what classes to create and use. It is only as obscure, overblown,
zealous, or inflexible as you choose to make it.

Most five year olds grasp the concept of "toys", and can pick up their toys and
put them away. This requires recognizing that their stuffed bear, their fire
truck, their set of lego blocks (as a group), and their ninja turtle all qualify
as toys.

People are often frustrated when programs don't seem to recognize "what things
have in common". It would be far more difficult, for instance, if you needed a
separate Explorer for Excel files, Word files, VB6 files, etc., rather than
having a system that recognizes that they are all files, and that many
operations can be performed on any of them.

When it is used right, OOP greatly simplifies a task that would other wise
require many Select Case statements, to sort through various possiblities at
each step. It is functionally a way of automating that kind of process at the
compiler level, and produces about the same execution time when compared to a
Select Case + Call.

Certainly VB6 itself is written using OOP, as are most of the other substantial
programs you use. It is far more than a curiosity.



.

Loading