Tom MacWright

Second-guessing the modern web

https://macwright.org/2020/05/10/spa-fatigue.html

[…] there is a swath of use cases which would be hard without React and which aren’t complicated enough to push beyond React’s limits. But there are also a lot of problems for which I can’t see any concrete benefit to using React. Those are things like blogs, shopping-cart-websites, mostly-CRUD-and-forms-websites. For these things, all of the fancy optimizations are optimizations to get you closer to the performance you would’ve gotten if you just hadn’t used so much technology.

• older link:
  How I'm teaching the kids coding for the web
• newer link:
  Modified machete

---

Related contents with similar topics

1. 

   Taylor Hunt

   Routing: I’m not smart enough for a SPA

   • Nicolas Hoizey
   • 20 April 2022
   • WebPerf, SPA, JavaScript
   • 5 reactions

   Here comes Taylor's 4th article in his great "Streets" series about web performance and front end architectures. Overall, SPAs’ reliance on client…

2. 

   Jeremy Wagner

   React Bias

   • Nicolas Hoizey
   • 18 January 2021
   • React, JavaScript
   • 9 reactions

   The juxtaposition of The HTTP Archive’s analysis and The State of JS 2020 Survey results suggest that a disproportionately small—yet exceedingly vocal…

3. 

   Michael Scharnagl

   Loading and replacing HTML parts with HTML

   • Nicolas Hoizey
   • 4 January 2021
   • HTML, JavaScript, SPA
   • 6 reactions

   I really would like HTML to be more powerful, and I think showing other content without a full page reload is something people wanted for decades…

4. 

   Kitty Giraudel

   N26 and lack of JavaScript

   • Nicolas Hoizey
   • 9 March 2020
   • JavaScript, React, progressive enhancement, User-Agent
   • 2 reactions

   Great article where Kitty shows how React helps providing N26 clients the features they're looking for even if they unfortunately have JavaScript…