- From: Natalya Shelburne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Feb 2020 17:39:21 +0000
- To: public-css-archive@w3.org
I am in favor of anything that makes the work visible and valued. Defining CSS4 can join the many other ways progress and stability are communicated to those without their eyes focused on the world of CSS. Anecdotally, I often find myself in the role of teacher and advocate for the new capabilities of CSS, and I am often met with either surprise or mild disbelief - more than a few engineers I work with feel concern that the new features in CSS might not really be production ready, and as a result, do not prioritize the time to delve into them. In a time-scarce world where things are being versioned with a vengeance, seeing CSS3 remain static sends a message. Designers and engineers constantly have to prioritize what to learn and what to keep up with. A clear and well defined list of "this is CSS4" would instead signal that these things are worth prioritizing to learn today, not later, and encourage trust so that the developers don't have to ask "but is it ready to use yet?" as the first comment on every blog or at every Q&A. A 'major version bump' so to speak, from CSS3 to CSS4, will get designer and engineer attention and send a clear message of progress and stability. My hope is that it will also help to add weight to folks writing job descriptions, deciding on frontend architecture, and shaping team roles. -- GitHub Notification of comment by tallys Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-585326989 using your GitHub account
Received on Wednesday, 12 February 2020 17:39:33 UTC