Adobe recommends: Enhanced support for CSS3 in Dreamweaver CS5.5

Question

Over  the past week, we publicized some high-value content from adobe.com and other community sites. Hopefully you enjoyed these posts and found the resources useful. Today is our last day of the "Adobe Recommends" series.
Continuing our trip along the CSS highway, we now move to CSS3 with our next recommendation, by Preran Kurnool:
Enhanced support for CSS3 in Dreamweaver CS5.5
This blog post takes you through using box shadow, text shadow, border radius, and border image properties in Dreamweaver CS5.5.
Give it a spin and let us know what you think!
Previous recommendation threads:
Use Dreamweaver CS 5.5 to package your web application for iOS and Android devices
Customizing a Spry Menu Bar widget
Spry Menu Bar resources
Layout 101
CSS page layout basics
New CSS features in Dreamweaver CS5
Automatically attaching style sheets to new documents

Answer 1

Aegis Kleais wrote:
Sorry, Al, but I couldn't disagree more.  Where I respect the fact that, as coders, we're rather ingrained with our workflow processes and, at times, hesitant to change, I've found LESS' benefits to be very worthwhile.
No need to apologize. Preprocessing is a topic on which there are differing opinions. You have one. I have one. There are advocates:
http://blog.urbaninsight.com/2012/04/12/ten-reasons-you-should-be-using-css-preprocessor
There are those who are not sold:
http://blog.millermedeiros.com/the-problem-with-css-pre-processors/
http://www.skybondsor.com/blog/css-preprocessors
There are those mostly sold:
http://css-tricks.com/musings-on-preprocessing/
There are even those who have been converted (but who might reverse at some later point):
http://cognition.happycog.com/article/preprocess-this
Heck, even I might be converted someday - or not
Bottom line for me, right now? I know I can write CSS that is better than most, more efficient than most, and easier to follow than most, and a preprocessor would add unwanted complexity. But that's for me. For someone not able to be organized intutively, or for a large - but carefully coordinated - team, a preprocessor could be a positive.
But not for me.
There are evolving trends - popular aspects of the technology that may and should find themselves being adapted into CSS. But I've been around this business as long as CSS has. I've seen buzzwords and trends and I've historically been spot-on in predicting the one that will stick. I think preprocessing will stick - but only insofar as it will be a catalyst for features in future versions of CSS. As a separate technology it makes no sense - to me