People don't write C++ and think about the standard, they write C++ and see if it compiles.
Should they operate this way? Of course not.
Are you going to change human psychology and cause this to happen anytime soon?
Nope.
If you want them to change, you'd have to provide a reason it matters, and very abstract long term notions of "goodness" are not gonna cut it for most developers, for better or worse.
But if that gets fixed, they go back to not caring... until/unless the pain rises.
But in general I agree with you.
> People don't write C++ and think about the standard, they write C++ and see if it compiles.
Yep, you not just have to provide a _reason_, you have to provide tools that fit into workflow as efficiently as conveniently as that. (Ideally, that's a (in this case) compiler that's standard compliant!)
Even if you develop for Chrome, Firefox and Edge you'll just end up building workarounds for all 3, not adhering strictly to the standard.
The standards are a single source of truth for your production, if you build solely to a single browsers quirks (in this case Chrome) then those quirks can change at any time.
I still fix FF bugs when they come in (it seems to be a bigger offender than IE recently) but developing for Chrome first is the only approach which makes business sense.
A web developer codes against real machines, not the imagined, idealized, and non-existent machines the specs describe.
And then what?
I just write standards compliant ES6 code, put it through a transpiler and some polyfills, and my code runs on every browser. I haven't had to think about which browser I'm targeting for years.
... but you can (and I'd argue in a lot of cases, looking around at the overly-complicated sites on the web, should) write a lot of fully functional web pages by keeping to the standard and trusting it's good enough. We are no longer in the bad old days where IE and other browsers deviated significantly---most of the browsers today adhere closely to the spec, and in the places they don't, it's often more like one browser handles a nasty corner case better than another because the browser built an optimization in for a critical path your page layout cares about.
Is there an "objective" test for standards compliance these days, like the good ol' acid test was for the box model? I agree with this sentiment, but only anecdotally - I'd like to see something concrete to back it up.
