title: Future of Aspect Oriented Programming
body: <p>I am a newbie in the area of AOP. The first time I coded something applying concepts of AOP, I was thrilled to understand how aspects eliminate cross cutting patterns in your application. I was overwhelmed by the thought of solving cross cutting patterns like security, logging, transactions, auditing and etc applying AOP.
  <br>
  However, when I first proposed usage of AOP to the client I am working for, I was told that they don't support it. I was told that AOP means more maintenance! Your pointcuts have to change if your code changes. Hence, you might have to analyze, change and test your aspects whenever you change the code to which they were applied? 
  <br>
  What do you have to say regarding this? Why are mainstream companies not open yet to extensive usage of AOP? Where is the AOP world going? </p>