3 ms·

This sounds like web.dev are advocating devs don't do feature detection and progressive enhancement, and adopt a "don't use a feature until it's in all browsers

This sounds like web.dev are advocating devs don't do feature detection and progressive enhancement, and adopt a "don't use a feature until it's in all browsers" mindset. I mean, you should detect support regardless just in case, but if you approach building apps with a more "I'll use whatever the user has available" way of thinking you can deliver better experiences (in my opinion), even if it makes a dev's life a little harder in some cases. It's a surprising move from the web.dev team to say the least. If I was being cynical, and I am, I'd suggest this move is designed less to be 'helpful' and more to highlight how far behind Chrome other browsers are. It's like lots of pages are saying "This is a lovely feature, but don't use it because of clunky old Firefox" rather than saying "This is a lovely feature, and here's how to use it, including a polyfill/workaround for browsers that don't support it yet."

Thorrez 3y ago
What's the relationship between web.dev and Baseline?
- andreban 3y ago
  Baseline is being discussed and defined in the WebDX Community Group: https://www.w3.org/community/webdx/ https://www.w3.org/community/webdx/. It's not a created by web.dev or Google, but there are people who work on it who are part of the W3C Community Group.
bruce511 3y ago
I kind of find it useful in the other direction. If I find s feature I want to use, and it's baseline, then I can just use it without worrying. If its not baseline I can head over to caniuse and see coverage, add progressive enhancement, find polyfills and do on. It that context it saves me worry, and also creates a baseline of things I have yo document as being "browser dependant".
- andreban 3y ago
  And that's exactly the goal. There's no recommendation against using features that are not in Baseline - and there is a superset of features that are progressive enhancement or polyfilllable, but those are much more use-case dependent - Progressive Enhancement frequently depends on the use case, and Polyfills vary the impact they have on performance, so need more care.
magicalist 3y ago
> This sounds like web.dev... This post is on mdn.

Thorrez 3y ago

What's the relationship between web.dev and Baseline?

andreban 3y ago
Baseline is being discussed and defined in the WebDX Community Group: https://www.w3.org/community/webdx/ https://www.w3.org/community/webdx/. It's not a created by web.dev or Google, but there are people who work on it who are part of the W3C Community Group.

bruce511 3y ago

I kind of find it useful in the other direction. If I find s feature I want to use, and it's baseline, then I can just use it without worrying. If its not baseline I can head over to caniuse and see coverage, add progressive enhancement, find polyfills and do on. It that context it saves me worry, and also creates a baseline of things I have yo document as being "browser dependant".

andreban 3y ago
And that's exactly the goal. There's no recommendation against using features that are not in Baseline - and there is a superset of features that are progressive enhancement or polyfilllable, but those are much more use-case dependent - Progressive Enhancement frequently depends on the use case, and Polyfills vary the impact they have on performance, so need more care.

magicalist 3y ago

> This sounds like web.dev... This post is on mdn.