- From: Lazar Ljubenović via GitHub <sysbot+gh@w3.org>
- Date: Sat, 29 Feb 2020 10:23:37 +0000
- To: public-css-archive@w3.org
First it's decided that CSS will not be versioned as a whole in order to allow separate specifications to grow independently, and not wait for one other. Now we'll have "CSS Grid Level 7 is part of CSS 5"? Sounds like a great idea! Let's confuse everyone! Why? So a bunch of recruiters could update their job offers from meaningless HTML5/CSS3 to a meaningless HTML5/CSS4, and so web designers on LinkedIn can get endorsement for a new trending CSS4. Just drop the numbers already. It's CSS, an evergreen language. When someone asks you what's your primary browser, you say Chrome, not Chrome79. Your library of choice is React, not React16.3. The version number is useful for developers. It's a technical detail. After GitHub added actions, they were still GitHub, not GitHub4. When they update an internal library, they're still GitHub. CSS is like a monorepo of modules. They advance through levels separately. That was the whole point of that decision. What exactly is the problem with it? If I understood correctly (I obviously didn't read everything in the thread), basically the ain driving force behind this idea is "previously the name HTML5 helped push browsers". Yes, it helped push browsers from dark ages of ridiculous inconsistencies and lacks of specifications. Now we have specifications, and almost every browser is "evergreen", always updating and always growing. So what exactly are you solving with incrementing a number which we previously agreed to get rid of so the language can advance faster? -- GitHub Notification of comment by lazarljubenovic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4770#issuecomment-592929898 using your GitHub account
Received on Saturday, 29 February 2020 10:23:38 UTC