Two thoughts:<p>Firstly, when you provide a normative assertion, at least couch it in positive terms.<p>“<i>If</i> you want X, <i>then</i> you should do Y.”<p>That way people at least know the tradeoffs you’re opting them into. I really can’t tell what trade offs the author is proposing are better for me.<p>Secondly, if you can’t build a system that actually decouples the frontend and the backend, that’s a “you” problem, not a technology problem. I have successfully designed and implemented many APIs that operated completely independently of the UI, allowing both the UI and power users to interact with our platform through a shared service.<p>I do get so tired of people presuming their specific issues are everyone’s issues. I have zero problem with the tooling of an SPA, my ability to customize is <i>increased</i>, not decreased, when I use an SPA, and when I’m working with other people, they often prefer not having to think about the whole stack, which makes them happier.<p>This is one of those articles you read that shows up “unplugged” from the culture in which it originated. The author demonstrates the value of talking to others in a given field, and the pitfalls that one can get trapped in when one doesn’t socialize enough professionally.