This single comment absolutely confirms that point of view: https://github.com/rails/rails/issues/25208#issuecomment-222...
I think you're seeing the web through SV tinted glasses.
http://www.amazon.com/gp/help/customer/display.html?nodeId=2... (notable exceoption for IE8, would love to know the reason)
I honestly can't believe a back end framework has minimum supported browser requirements that are basically "use the latest or GTFO".
Most web apps are only tested on the latest browsers anyway, even if they claim to support older browsers. This is true unless you have a very popular app and a very large team.
I've worked in web/related fields for about 10 years now, and I've never worked on a project where "fuck it, the latest will do" has been acceptable.
Or you have very important and lucrative clients in government, healthcare, or some other crusty large organization with horribly dated browsers they're not going to replace any time soon. That quickly makes you throw away the latest React-* solution and reach for jQuery, however much you rage inside.
And when some library fails in an old browser is always something so small that I end up making a PR and getting it fixed the same day.
HN discussion: https://news.ycombinator.com/item?id=11757993
For me, it was the amount of magic involved in everything. I'm just glad I gave up and moved onto other things.