I would sooner blame the management, that would even think of excluding “untested” or “unsupported” browsers, like some kind of technofacist dictator, instead of choosing a helpful “if you’re having problems with our shit site, use chrome” message… or even literally doing nothing… everything is broken these days, and a half-functional site is better than an intentionally-broken one.
The tools and knowledge exist to make building standards compliant web applications just as easy, if not easier, than chrome-only web applications. It’s not the responsibility of management to use those tools or acquire that knowledge.
Unless you’re using some fancy WebGPU shit. I don’t think we’re talking about some fancy WebGPU shit.
Because they hire cheap developers who don’t know what the fuck they are doing?
Is very possible to know exactly what should be done, but not have the time available to achieve it.
This is the correct answer
I would sooner blame the management, that would even think of excluding “untested” or “unsupported” browsers, like some kind of technofacist dictator, instead of choosing a helpful “if you’re having problems with our shit site, use chrome” message… or even literally doing nothing… everything is broken these days, and a half-functional site is better than an intentionally-broken one.
The tools and knowledge exist to make building standards compliant web applications just as easy, if not easier, than chrome-only web applications. It’s not the responsibility of management to use those tools or acquire that knowledge.
Unless you’re using some fancy WebGPU shit. I don’t think we’re talking about some fancy WebGPU shit.