> It's literally the same thing as asking application-oriented developers to code and test their apps for every major compiler out there. No, the end user is n

> It's literally the same thing as asking application-oriented developers to code and test their apps for every major compiler out there. No, the end user is not usually in control of their compiler. It's closer to making sure thatthe program works on every screen size or OS you're targeting, because these are the thing the user controls directly. > We can't be the responsible for making every webpage compatible with every browser. Not directly. You can do that by coding to the standards that all browsers support. To extend the compiler analogy, if your customer is in control of their own compiler, then you don't code to MSVC or GCC, but you code to C89 or C++03, knowing that the standards-compliant compilers are able to support that. The burden is definitely on the coder there. You might argue that you need the newest standard, and then I agree that part of the responsibility is on the browser vendor, but I still hope that you're going to implement graceful fallback.