I would like to say I agree with the proposition of your post and your arguments, but as a web dev please don't mix the state of the web with what the median web dev considers a good UI/UX. We don't make the Jira tickets and if you have worked in a corporate environment you know very well that arguments like "but the UX/accessibility" hold very very little value in the context of most decisions.

On the other hand modern application of agile methodology is borderline ruinous for team productivity and most of the time exists for a specific stakeholder to feel less anxious rather than for a team member to raise a blocker or a dependency.

I work in a fairly big company and there is the notion of extracting people from their agile teams to have them work uninterrupted on large tech initiatives. Which is in my opinion a subtle way to signal that if you know what you want to build, agile methodology at least in the perverted way most companies apply it doesn’t work.

I think we should put behind us any discourse about companies risking their hiring pool by being hostile to the society or their own employees. People will definitely try to be hired at $company if it means six figure pay, doesn't matter the sector. We have plenty of examples for this.

They don’t know what they could have or why the new captcha is funny, thus they can never come up with a prompt that leads to them being educated on the matter. They would have to know that they don’t know and since there is no public discourse for such matters in their Facebook timelines, their thinly right wing digital news outlets and their Viber and what’s app chats they will never know that they don’t know.

Nobody argues what we currently have is great and that we shouldn't look to improve it. Reducing it to "JS developers bad" is an embarrassing statement and just shows ignorance, not only of the topic at hand, but of an engineering mindset in general.

Redux is boring tech and there is a time and place for it. We should not treat it as a relic of the past. Not every problem needs a bazooka, but some problems do so we should have one handy.

Given how FEs are re-written every 7-10 years there is ample room for other frameworks to knock React off its throne, but before asking "but why not X" you also have to consider that organizations by now have almost a decade of experience building React apps and this plays a major role when deciding on which UI framework to rely on.