2 ms·
Having too many concerns involved with a piece of code is the problem. AOC doesn’t fix that, it makes it more likely to happen. In the time since AOP, a lot m
by hinkley 3y ago
Having too many concerns involved with a piece of code is the problem. AOC doesn’t fix that, it makes it more likely to happen.
In the time since AOP, a lot more API designs have sprouted support for closures. That’s “around” semantics and the degenerate cases of around are before and after, which covers most of the space. Async/await fills in some of the remaining gaps.
- kazinator 3y agoSpeaking of around semantics, which brings me to the CLOS topic, I first learned about AOP in 2005 at a live presentation by Kiczales. He made disparaging remarks about Lisp and said that CLOS should be pronounced "see loss". Remember, that's the author of the Art of the Metaobject Protocol, and of the Closette project (portable implementation of CLOS-like object system).