[hinkley]

I did for a while when CSS3 was new.

Big problem with evergreen standards: if you try to come back to a standard that is now twice as big but still has the same version number, there is nobody writing books to teach you what you missed out on. Want to come from CSS2 to 3? They got you. Want to do backend development for five years and then get a summary on what you missed? Go fuck yourself.

[tombert]

Yeah, that's the thing.

I'm not saying that this is a "bad" thing, but the last time I did any significant amount of frontend stuff was back in ~2014, and it was AngularJS, which was considered pretty ok at the time I think. I left that job and started doing almost exclusively backend stuff for several years, and when I looked back, the entire world had switched to React and transpiling JSX and a lot more CSS than I was familiar with.

It seemed pretty intimidating to try and pick that up again, so I never really left the backend stuff, and now I've managed to even avoid web stuff for awhile, because I kind of hate web programming.

[hinkley]

Today's example:

Forgot that you can nest CSS now without Less or SCSS. Luckily my CSS has just barely tipped over into 'hot garbage' when I figured this out instead of in another four weeks.

[DicIfTEx]

FWIW you're not alone in thinking that: there's a W3C CSS4 Community Group[0] now, and you can find more detail on their proposal at https://github.com/w3c/csswg-drafts/issues/4770 and ongoing CSS[3|4|5|Next] categorisation work at https://css-levels.netlify.app/

[0]: https://www.w3.org/community/css4/