3 ms·
OO has been tremendously successful, it has allowed us to build systems that we wouldn't have dreamed of before. The Web was invented on a NeXT in Objective-C.
by mpweiher 12y ago
OO has been tremendously successful, it has allowed us to build systems that we wouldn't have dreamed of before. The Web was invented on a NeXT in Objective-C.
Reuse in UI frameworks has been great, and I've had similar success with custom frameworks.
However, success invariably contains the seeds of failure, because success means that we are taken to the limits of applicability. To me, those limits were visible in the 90ies when I wrote my Master Thesis[1], issues like the non-composability of frameworks, the runtime/compile-time, composition/inheritance dichotomies, architectural mismatch etc.
Alas, nothing really happened, and IMHO, things actually got worse. At the time, I had two candidates for "the future", one being AOP and the other software architecture. AOP was a dud, but I am very hopeful about better linguistic support for software architecture, so much that I am creating a programming language that has software architecture as its organizing principle, deriving other paradigms such as OO from this base [2].
Having been exposed to FP early on, I have to admit I don't understand the current hype, because it seems to primarily address issues of "programming in the small" (tight coupling), although some of the lessons (communicate using simple data) are applicable elsewhere, and have been discovered elsewhere. I don't see a large-scale distributed system like the WWW built in the FP-paradigm, but happy to be corrected!
[1] http://www.metaobject.com/papers/Diplomarbeit.pdf http://www.metaobject.com/papers/Diplomarbeit.pdf
[2] http://objective.st/ http://objective.st/
- judk 12y agoAOP isn't a dud. Google Guice is AOP.
- mpweiher 12y agoReally? Taking the definitions from "Software Architecture: Perspectives on an Emerging Discipline" [1], you have the following: - components - connectors - configurations (systems) Guice (and other dependency injection frameworks) clearly address the third part: configurations. AOP is, at best, an implementation technique. [1] http://www.amazon.com/Software-Architecture-Perspectives-Emerging-Discipline/dp/0131829572 http://www.amazon.com/Software-Architecture-Perspectives-Eme...