It is pretty obvious that platform-only approaches are riddled with problems that are unacceptable in professional environments that develop production-graded software. Polyfills and caniuse show one part of the problem, "your browser is not supported" and "designed for chrome" is another, etc. Only someone who is completely detached from professional settings would argue otherwise.
> If you know what you are doing it is far less effort.
Those who know what they are doing are knowledgeable enough to simply avoid the problems caused by platform fundamentalism. Not knowing this is a skill issue.
Again, this is only subjective reasoning without evidence. It’s just as correct as it is incorrect depending upon who you ask. The complete inability to perceive that subjectivity is a maturity problem technology cannot fix.
"Why does the page fail to work with this browser?"
That's rather obvious, isn't it?
> Again, this is only subjective reasoning without evidence.
It really isn't. While systems are designed around this problem. Even UI test matrices. How come are you spending so much time discussing an issue you're not aware?
All of these comments unintentionally make an important point about human behavior that screams so much out loud in a way that I alone couldn’t do justice to. That is why.
Those allow you write a template, and the UI is brought up to date with that template.
Tracking UI updates mentally is clearly harder, except in trivial cases.