3 ms·
I tend to agree. But in defense of the SPA, my experience is that over time, most screens accrete complexity. You start out with a simple content screen. Then
by christophilus 7y ago
I tend to agree. But in defense of the SPA, my experience is that over time, most screens accrete complexity.
You start out with a simple content screen. Then the client wants comments. Then they want richer comments. Then they want live comments. Etc.
Over time, most of my web applications tend to require richer and richer interactivity on each screen. As a result, it's nice to have started out with a client-side framework, rather than hitting some threshold where you suddenly need to switch things over.
- hombre_fatal 7y agoYour last paragraph summarizes why I default to a client-side framework if there's going to be much of any JS interactivity at all on a screen. Even something that seems simple like a search form can be surprisingly interactive.
- pier25 7y ago> As a result, it's nice to have started out with a client-side framework You mean like Angular or Ember? Because you can perfectly use Vue, React, Inferno, Svelte, Imba, etc, on a multiple-page application.