Our major clients have IE6 as their standard corporate browser. It’s one thing to fix IE6 bugs in our own code, but if the bugs are in the framework and I’m not supposed to edit the framework files, then I’ve got a problem…

We’ve had so many issues supporting IE6 (including a few awkward moments with clients), that I’m pretty sensitive to IE6 support and don’t take chances with it.

I’d rather give them a higher estimate/bill and develop with a tool like Flex where it may take more time, but I’m guaranteed that it will work everywhere when I’m done.

That said, I still see where 4DAF is useful and intend to try it out when I get an appropriate project. The sooner you fully support IE6 (or at least clearly define what I shouldn’t use in the framework if I want IE6 support), the sooner one of those projects is likely to come along…

As far as 4DPartners.com - You’ve done a good job thinking about the site from the user’s perspective, but it would help to also think about the site from the perspective of a search engine spider. Currently fewer than 300 pages on the site are indexed - I’m pretty sure that’s a small fraction of what it should be. I can suggest a number of ways to fix that problem - contact me directly if it’s something you guys decide to work on and we can discuss it more fully.