OOP – Mutant offspring of Language Design?
When you start to define programming as the job of developing and implementing elegant languages for expressing domain intent, you see both the strengths and weaknesses of OOA&D. Objects as nouns with methods as verbs is one quite useful approach to language design, but there are clearly languages that are not most elegantly expressed using that kind of grammar. From simple utilities (which should really be language extensions) for creating structures or operating on collections to imperative flow driven requirements (like workflows), OOP provides the best single structure for simplifying language design to date, but the future of programming must support a wider range of concrete syntaxes for expressing language design.
Really just a random musing, but I have a feeling that some interesting concepts may come out of pondering this further. Is that making sense to ANYONE out there?! :->
It just gets very interesting when you come from a LOP (Language Oriented Programming) approach. Suddenly we're just all in the busienss of designing languages and writing parsers/generators/methods to implement them. Then you can start to develop heuristics for representations to use for different classes of languages and create tools that are a little more usable than what Metacase or Microsoft offers, more flexible than what OMGs MDA provides and a little more AVAILABLE than Simonyi's stuff.
Just have a feeling this could be cool if I could just pull it all together . . .
Or maybe I just can't be bothered to finish up a project and I'm procrastinating . . . who knows :->