This is a great thread, thanks for bringing it here. As someone who's built a CSS3/DOM animation tool these posts were very interesting to me (Edit Room - link

This is a great thread, thanks for bringing it here. As someone who's built a CSS3/DOM animation tool these posts were very interesting to me (Edit Room - link and info in profile). My philosophy is that keeping a semantic DOM HTML structure and setting those elements up for animation is the way to go, for accessibility, focusing on content first, mobile first, etc. To those asking why not just use SVG or Canvas - including SVG and Canvas for the things they are good for, (vectors / filters / generated graphics) plays to each technologies' strengths. Getting a release out the door is something we all aspire too, and it looks like support for those are coming as well. If they are smart, they will keep the DOM animation as well - it's a great common baseline, can be extended into the past with javascript (like they are doing now) It's fine, there are tons of animation tools cooking out on the web as well - if this doesn't fit with some people's workflow, then other tools will. Thanks to Adobe for moving the competitive landscape forwards.