My point was to be a counterpoint to what you were saying, which is why I focused on the reasons why being a stickler for legacy browser support isn't a great p

My point was to be a counterpoint to what you were saying, which is why I focused on the reasons why being a stickler for legacy browser support isn't a great policy either. To me, it's meaningless to say something like "X is important." Important to whom, for what end, relative to what? Nothing is important in a vacuum, when there's limited resources you're always choosing between several "important" things. Supporting old browsers is a tradeoff, not just for saving developer time, but also for the user. For instance, do you care about internationalization? A lot of browser internationalization APIs don't work or exist in old browsers. Sure, you can make them work by bloating the payload that you send to a user on an antiquated browser. So what's more important to your users - accessibility for an old browser, or accessibility for a spotty internet connection, or accessibility to people who speak different languages? My point about web apps is that it's often impractical to support extremely old browsers because they often lack the APIs, the users, nor the OEM support that make web apps worthwhile.