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

I don't necessarily disagree with @rickgregory sentiments. I do however, think it is perhaps idealistic. 

That approach was largely the way CSS3 went down. And it was not without problems.
The state of things being 'ready' or not was no different when we were all saying 'come and try CSS3'. You still had to check support, weep, and create workarounds for any semblance of cross-browser compatibility — and deal with vendor prefixes for extra fun  ;) 

Perhaps I am being overly cynical but saying it is CSS4, CSS5, CSS2020 etc is unlikely to change the reality of how these things are implemented. Stick what you want on a roadmap and give it a name. Even get all browsers to agree to it, but I don't think it is going to change the way 'the sausage gets made'. If a feature suits the business needs of one browser but not another, you aren't going to see it implemented. And that leads to 'CSS4' failing in the eyes of devs because 'you can't use it yet'. 

I'm not saying that's good but I don't think it is the reality we live in.

Things from the W3C side already get announced and updated on the W3C CSS homepage: https://www.w3.org/Style/CSS/Overview.en.html

There is an [RSS feed](https://www.w3.org/Style/CSS/Overview.atom) too that's worth subscribing too. I know it's not widely circulated but there are means to stay officially up to date from a W3C point of view.

If you want more noise making about it then we all need to start making books with 'CSS4' in the title ;)

-- 
GitHub Notification of comment by benfrain
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-597340879 using your GitHub account

Received on Tuesday, 10 March 2020 22:06:47 UTC