A lot of “CSS is not real programming” arguments are a basic misunderstanding what CSS is there to achieve. If you want full control over and interface and strive for pixel perfection – don’t use it. If you want to build an interface for an inclusive and diverse web, CSS is a great tool.
Christian does a good job of describing the much-misunderstood declarative nature of CSS.
Also:
In any case, belittling people who write CSS and considering them not real developers is arrogant nonsense.
So instead of asking yourself, “How can I write code that does what I want?” Consider asking yourself, “Can I write code that ties together things the browser already does to accomplish what I want (or close enough to it)?”
A great talk by Matthias on what you can do with web standards today!
CSS wants you to build a system with it. It wants styles to build up, not flatten down.
Truth!
It’s like CSS exists in some bizarre quantum state; somehow both too complex to use, yet too simple to take seriously, all at once.
In many ways, CSS has greater impact than any other language on a user’s experience, which often directly influences success. Why, then, is its role so belittled?
Writing CSS seems to be regarded much like taking notes in a meeting, complete with the implicit sexism and devaluation of the note taker’s importance in the room.
Here’s a taste of what Rich will be delivering at Patterns Day on Thursday—can’t wait!
Defining the inputs instead of trying to control the outputs.
A language so powerful that we have to stop ourselves from using all its features.
HTML. JavaScript. Why not both?