I loved the article. First time I've understood what AOP is about (not that I have tried that hard).
At project start up the issues are always:
How do we do error handling
How do we do logging
How do we do internationalization
How do we persist data
How do we ensure it runs, and bounces back if it dies.
AOP can answer quite a few of these. However, the next concern is:
How do we make sure it works quickly and robustly.
And here I side with the red flag - I can't see the code, and I worry like hell that it will create far more trouble for me than doing it myself with simply high level language constructs that I know work.
So what if its a little extra typing, typing is easy.