[not_your_vase]

Personal pet peeve: only the latest versions of browser are supported - in the moment some new css/html/js feature is available, it is integrated in the website at lightspeed.

On it's own, this wouldn't be a problem of course. My problem with this is that there is no website on the web today that was technically impossible 5 years ago. Still, a 5 years old browser is unusable today due to this. (thinking primariy about ipads, which come with not updateable browsers)

Not sure if this is knowledge gap, or just simply unwillingness to write code that works on the widest range of devices...

[basementcat]

I think this depends on who your customers are. If your customer is a regulated utility that may be required to use equipment that has been "licensed" for certain purposes, making sure websites work with older versions of browsers is very important. On the other hand, if you're targeting high-ish net worth end users who may be expected to always run the most recent browser version on the most recent hardware, then it would make sense to always target the most recent features.

[solardev]

> thinking primariy about ipads, which come with not updateable browsers

Wait, what? That's news to me. Their Safari doesn't auto update like other browsers do?

[not_your_vase]

Correct. Safari is baked into the operating system, like the Camera or Notes app. But unlike those, it becomes obsolete in the moment OS updates stop coming due to its secondary-OS nature. It has been like that since the very beginning.