While it's a bit long and I don't agree with everything, the article raises important reminders for web development with empathy and accessibility. This part fe

While it's a bit long and I don't agree with everything, the article raises important reminders for web development with empathy and accessibility. This part felt especially relevant: "[Progressive enhancement] won't work with something like React though, and I don’t cry about that. This is a distinct robust design pattern, which we feel is durable and doesn't lock us into a limited-life framework that will get replaced by something else in a year or two." (emphasis mine) I imagine this last line gets some people reacting emotionally. I've spent the last few years in React-land (in addition to a soon-to-be-legacy stack slowly transitioning), and benefited much from the paradigm shift. It has moved the web (and web dev) forward in many ways, especially conceptually. At the same time, I can't deny that it will eventually get replaced, just like the rise and fall of jQuery. That means we must keep in mind not to be locked-in, to emphasize the core concepts which will outlive any framework du jour. Progressive enhancement is certainly doable with server-rendered React, but it does seem like the recent trends have favored developer experience at the cost of user experience.