Never mind IE11. <a href="http://motherfuckingwebsite.com" rel="nofollow">http://motherfuckingwebsite.com</a> still works on IE6, and why shouldn't it? It's plain HTML with no CSS or JS.<p>There is no reason why any web document should not still be readable in Lynx, Mosaic, or even WorldWideWeb.<p>Web applications are a bit more complicated, but that complication is self-inflicted. We developers choose to to hijack users' devices for work that should be done on the server in the name of providing a better user experience, and we make our work harder in the process.<p>Supporting old browsers isn't that hard. Build a solid foundation of HTML, HTTP GET, and HTTP POST, even if it means doing full page refreshes. You can always layer your AJAX calls and such on top. It's called "progressive enhancement", remember?
As with all things it's a cost benefit analysis. It costs money to support old browsers and a lot of money doesn't come from them do do the math.<p>I was trying to buy movie tickets online the other day.I tried Firefox then Firefox without ad blockers, then ie, then edge, then chrome on two different desk top machines.<p>Then my gf bought them on her phone browser.<p>Thanks mobile first development. How much money must you be costing your adherents?