My problem with ADDT's trigger concept was always that it made it much harder to alter the code once the triggers were in place. Instead of PHP being a top-down language, the trigger method makes it more based on function and takes many of the possible alterations out of it.
Sure, the trigger method makes it easier if you are just making simple CMS inserts and updates, but many of my own projects for my clients require heavy alterations to code to perform tasks that no framework or functions does out of the box.
So in my mind - as an owner of both - WA has always been a better option. It does have a steeper learning curve but each component is more customizable.
I think the reality is that ADDT was a good concept but not very flexible as a framework. If the tasks were going to always be very simple content operations, than the trigger method deployed work. But let's not kid ourselves - ADDT's triggers are nothing in terms of flexibility nearly as usable as frameworks such as Rails, Cake, or Igniter.
