I believe the author when he says he feels gaslit into accepting JS SPA as the Only Way to Make Web Apps These Days. I have noticed a similar trend (though my p

I believe the author when he says he feels gaslit into accepting JS SPA as the Only Way to Make Web Apps These Days. I have noticed a similar trend (though my particular neurodivergences have likely shielded me from most of the impact those pressures might have had on me). That said, this whole JS SPA stuff in general and React in particular was not propelled solely by these gaslighting influencers. There was at least one other thing that helped them to their current dominance: it turns out to be a really good idea to represent an app (i.e. business logic + UI) as a just-in-time data structure that is incrementally recomputed in response to changes in state and is shaped like a tree so as to track state dependencies via parent-child relationships. This kind of “reactive state tree” approach is genuinely powerful and brings significant and real advantages over model-view-controller approaches. It’s like a web-flavored microcosm of object-oriented vs functional programming. JS SPA (e.g. React) had this and server-side (e.g. Rails) did not. That difference, _alongside a tsunami of bullshit_, drove React’s supremacy over Rails.