Frameworkism is not delivering. The answer is not a different tool but the courage to do engineering. Over the past decade, the author has worked on building web products and witnessed many performance and accessibility issues caused by modern frontend frameworks like React. React is considered legacy technology but still appears in new projects.

• The Rule Of Least Client-Side Complexity: Code on the server can be fully costed and its performance and availability are under control. Client-side code runs on the Devil's Computer with limited developer control. Declarative forms generate more functional UI per byte sent. React and other legacy frameworks tend to have bloated bundles. Tech leads should break this spell and forbid React in new work.
• OK, But What, Then?: The "what then" question has two forms. Teams can do objective bake offs to determine alternative technologies. But many teams don't have good reasons to stick with client-side rendering. Frameworkism insists that problems will be solved by using more tooling, but the only thing that makes web experiences good is caring about the user experience. Realism requires measuring user experiences and using data-driven baselines to make decisions.
• And Nothing Of Value Was Lost: Prohibiting React is a cost savings and helps reorient teams towards user delivery. The broad answer includes user focus, evidence, guardrails, and bake offs. Product managers must define a product thesis and commit to user success.
• Vignettes: Different application classes have different requirements. Informational sites should use semantic HTML and progressive enhancement. E-commerce sites should use server-generated HTML and progressive enhancement. Media sites can use progressive enhancement and islands. Social media apps can use hybrid approaches. Productivity apps may benefit from SPAs but need to manage performance. Other app classes need careful evaluation.
• References: Essential guides for frontend realism include those from the UK's Government Digital Service, Github alumnus Mu-An Chiou, Cancer Research UK, and others. These pieces emphasize looking for oneself and measuring.

In short, teams should avoid starting new projects with React and focus on user needs and data-driven decisions.