I would agree with the load time and I have previously used WA for more of my front end stuff, but DA has not, IMHO, held a candle to what one can do with ADDT in terms of back end management.
Given that ADDT is dying, even though mine if hacked for PHP 5.3, I have started working to build back-ends with WA. So far so good. I hope the issues with misplacing PHP code blocks when applying WA behaviors improves.
The big issue for me was the need to resort lists based on the users whim. That having been solved, (see the sticky post in the DA forum) I'm doing alright with WA and it is more customizable on the view end. It definitely needs more capability to manage based on recordsets as well as tables.
I still don't find the same power that ADDT's triggers and transactions offered.
I don't mean to complain about WA, I just want to see these capabilities added to the product's capabilities.
Lastly, I want to suggest, which was my actual purpose for coming to the forum tonight, that individual transaction wizards be added. I read the response about making a form and adding the behavior which is all well and good, but if I have been using the wizard and then need to add an individual transaction form, I want to be able to pick from the same style/design templates (get the same choices) that I had in the wizard. In addition, the wizard should be faster and I use the extensions to save time.
Oh and last lastly, I agree with the desire to be able to control what directories the includes go in or place them all in a an "includes" directory (call it WAincludes if you must). That would be cleaner.