For Application Development Professionals

This is an excerpt

Executive Summary

There's a new idea in programming languages that is gaining in popularity among some Java language gurus. Aspect-oriented programming (AOP) is intended to address common problems that object-oriented programming (OOP) doesn't address well, plus some problems that OOP itself created. However, AOP is a risky solution: It is a very generic mechanism for solving some very specific concerns and has been likened to a kind of "GOTO" statement for OOP. Like GOTO, it can cause more harm than good. AOP will find some uses among authors of frameworks and other infrastructure projects, but for the needs of typical application developers, language gurus would do better to address the shortcomings of the Java language and of containers that make AOP appear to be necessary. AOP might seem like an esoteric debate among programmers, but it's not one that decision-makers can afford to ignore.

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.