Regardless of how perfectly formed and well-written your code, sometimes things break through no fault of your own, even in modern browsers. If you’re not actively testing your site, bugs are more likely to reach your users, unbeknownst to you. Rather than transpiling and polyfilling and hoping for the best, we can deliver what the person came for, in the most resilient, performant, and robust form possible: unadulterated HTML.
Great post on how IE is hanging on and making developers’ lives harder.
I dunno if I’ve just been swimming in different waters lately, but I feel like the old conversations of progressive enhancement seem especially quaint right now. There’s so much momentum around JS frameworks where everything gets shoved into <div id="app" />, and no one seems to be batting an eye about it all. Sure, it’s possible to build server-side, “isomorphic” JavaScript applications, but the teams I work with don’t seem to be doing that work to build with progressive enhancement in mind. That of course makes me sad. There’s probably more to say on the subject, but I’ll leave it there for now.