Quote:
Originally Posted by calvin-c
You've got the nutshell, including the *long* time it takes to develop adequate styles (or objects). FYI, object-oriented programming was developed in the early 90's-and is only new being widely used. And even then, most of the 'use' doesn't take advantage of object-oriented programming features-the programmers are doing the same old code in 'the new language'. This would be, I think, like writing HTML with CSS, but the CSS only contains a couple of the most common styles-everything else is coded inline.
I hadn't actually thought about having industry-wide consistency. Programming is, pretty much, company-specific so I just hadn't thought in those terms. I suspect you're right-centuries of experience will be needed for that.
|
I generally concur. But it's worse than you think: Object oriented programming was developed in the
mid-60's (do a search on "Simula" or "Simula-67"; or the history of SmallTalk, or...). It was popularized in the early '90s, and spent a solid decade as the software equivalent of 'I've got a hammer, so I'll treat every problem I encounter as a nail' -- even when the problem was a screw. We've not yet reached a point where OOP is used where it makes sense, but is
avoided where that makes better sense.
Xenophon
(speaking in my professional capacity, for once)