W3C home > Mailing lists > Public > www-style@w3.org > January 2014

CSS priorities

From: Jens O. Meiert <jens@meiert.com>
Date: Mon, 20 Jan 2014 00:18:59 -0300
Message-ID: <CAJ0g8QQQe+gaU8p6FVPZGvQsgxCjQm1Q3q=6-e5Wz-5hX+Ff_Q@mail.gmail.com>
To: W3C WWW Style <www-style@w3.org>
Tab, Working Group members, could you comment on focus and what plans
you have with respect to curbing feature creep and spec fragmentation?

I had responded with the following to Daniel’s transitions email, but
predictably that wasn’t very useful there:

[…] my point here, or wish, is that it would be good to focus CSS more.

I’ve brought this up a few times in the past but I really think we
don’t do anyone a favor cramming, pardon a bit of judgment,
*everything* into CSS. Variables/constants are a great example: They
should not have become part of CSS, and that not just because authors
never optimized their CSS well enough to discover that they don’t need
variables to fight complexity, but simply because anything like PHP
would do for this [1].

Complexity then is hard to quantify but I think CSS complexity has
just exploded because anything that’s asked for and “sounds good” is
added. I’m getting a little cynical maybe but I don’t recall any
feature being *rejected* here for about ten years (with the exception
of obvious nonsense). Now we have 300 properties (up from 53 in CSS 1
[2]) and are about to make CSS a programming language.


[1] http://www.w3.org/People/Bos/CSS-variables
[2] http://meiert.com/en/indices/css-properties/

Jens O. Meiert
Received on Monday, 20 January 2014 03:19:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:38 UTC