True for this decade, but in the previous decade it was very much the opposite. Before you used any kind of browser api or nice language feature you would feature-detect it:

    if (typeof Array.prototype.includes === ‘undefined’) { …

And if it wasn’t there you would define it yourself, it was called “polyfilling”. This was so commonplace that we built significant tooling like babel to standardize feature detection tests and fallback implementations - for a few years you could write

    request.then(response => response.json())

And behind the scenes the Rube Goldberg machine would turn this into something that would run in a JavaScript environment that had neither arrow functions nor promises.

> Web devs are used to their target being evergreen

I would think/hope web developers are used to “just give me what you got”. Any other mindset leads to “you must install <browser> to see this site”.

It’s Electron devs that are used to that.

> Web devs are used to their target being evergreen

Since when? The browser landscape is much better today than 10 years ago, but no web dev worth their salt assumes anything about the user agent.