I want to add my 2cents to that topic:
Similar to Jan, I am most likely to use foundry for everyday work, because it is just the easiest way to achieve great looking results whithout getting stressed by zillions of options. it just works out of the box!
Every now and then I stumble upon a detail where I think “why can I not do this”, “why is foundry setting this limit”, why isn´t there an option for…“
But that is part of the magic, I guess. And I have tons of respect towards adam, because he keeps on track with his philosophy to keep things simple, although it might be seductive as a developer to „collect features” in his products just to satisfy the yelling user-base.
On the other hand I am blown away by the detail-ness and unlimit-ness that BWD stacks often offer to RW web design - although I hardly understand half of what the available stack settings are good for
Sometimes it´s just frustrating that something that should work does not work as intended, just because it is too complicated to set it up correctly (missing checkbox marked, wrong option in a pull down etc.)
maybe that is just the nature of the BWD stacks, maybe it´s because english isn´t my mother tongue, maybe it´s because the BWD documentation is not as well prepared than the documentation that adam delivers with his product (again: simple and clear)
for me, the conclusion is: we as designers should be really happy to have the best of both worlds at our hands: the eazypeazy-thing and the nerd-thing.
I encourage Adam to always take care of keeping the balance between features and simplicity, as well as Andrew shall always focus on giving us the extra little bit fine tuning capabilities.