None of my projects want to be SPAs
Back when I was doing React, what pulled me in was that it WASN&#x27;T a framework for SPAs. What I got from it was the ability to build UI widgets (components, in React terms) that worked within a page, and were composable with other UI widgets.<p>With that approach, you really wanted to keep every component self-contained. That meant a lot of bookkeeping with passing events back and forth between parent and child widgets, but while it was a lot of typing, it was all fairly easy, and if I wanted to change how an event was handled, it usually only involved a component and MAYBE the components immediately above or below it in the component tree. Data passed further than that was generally wrapped in objects and therefore didn&#x27;t require code changes.<p>Then introduce Redux and similar frameworks, and I totally lost interest. It&#x27;s as if the entire React community forgot all the lessons they learned writing Python and C programs in college and went back to creating global state. What in the actual hell? I wrote a good amount of code in Redux, too--I worked on teams that used it--so this wasn&#x27;t just pre-judgment. These frameworks add a huge amount of hidden global complexity just to avoid having to pass parameters to components, which is the simplest thing to do.<p>And once you&#x27;re doing that, you HAVE TO write an SPA, because any part of the page you want to be interactive gets pulled into Redux and your JS eventually eats the whole page. It&#x27;s an infection.<p>When writing JavaScript now, I sometimes end up rolling my own version of the component style. It&#x27;s an effective design pattern for UI widgets. But it hasn&#x27;t been worth it to use React for a while now because the tooling and tutorials are all too conflated with Redux and similarly awful tools. And on a team, there&#x27;s always the worry that someone on your team will infect your code with Redux and it will grow and consume your entire site. It&#x27;s a real shame.