[tragic]

> Yes, I know some things simply can't be done without a JS webapp, but not all and probably not even a majority, so if HTML and CSS will do the job fine, then so be it; and even if it needs to use JS, it likely doesn't need to be latest-browser-only JS either.

Sticking to HTML and CSS won't necessarily get rid of this - new stuff is being added to CSS all the time, in particular. And browser support is just as patchy.

[soperj]

How much new css do you actually use though w/ patchy browser support?

[The_rationalist]

There are many essential css properties that Firefox doesn't support, e.g fit-content

[connicpu]

But when a browser doesn't fully support a CSS feature most of the time is your site just looks a little wrong. Unless it's a major feature, the site will probably still be functional to the user.

[deergomoo]

The flip side of this is that many new JavaScript features can be either transpiled to ES5 syntax, or polyfilled. It will be great when we don’t need to anymore, but I’m always pleasantly surprised by just how much modern JS can be used in, say, IE11, just by having Babel be part of the build step.

CSS unfortunately doesn’t work that way, so apart from graceful degradation you’re out of luck.