W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2020

Re: [csswg-drafts] Let’s Define CSS 4 (#4770)

From: awford via GitHub <sysbot+gh@w3.org>
Date: Tue, 10 Mar 2020 17:17:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-597207873-1583860656-sysbot+gh@w3.org>
For developers building internal web applications, we are frequently locked into much older browsers, meaning no need to frequently check for new standards. I stopped looking after CSS3 came out. With no version number to tell me something has changed I have no compelling reasons to look for a new standard. Too much to stay on top of. If a CSS4 book showed up somewhere I would simply know it was ready for study. I've seen many discount this as "marketing". What product isn't concerned with marketing? What is the point of putting all this work into new standards and features if there is no clear way of announcing their availability? For that matter, what is wrong with sub-versions? If 3.1 supports flexgrid and 3.2 adds in "gaslight marquees", that's definable.

Obviously, I'm not heads down in the WG, but to stumble onto this discussion  is both surprising and concerning. From the outside looking in it sure seems like beaucracy is winning what should be revision management 101. Maybe a new W3 standard for version control is what's called for instead, because this is the kind of mess a standards body was meant to avoid.

GitHub Notification of comment by awford
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-597207873 using your GitHub account
Received on Tuesday, 10 March 2020 17:17:39 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:02 UTC