To clarify: it's a CSR problem to solve, not Struts' (which, as you say, is not subject to). To answer your original question in a pragmatic way: people used t

To clarify: it's a CSR problem to solve, not Struts' (which, as you say, is not subject to). To answer your original question in a pragmatic way: people used to JS tooling, libraries, frameworks obviously want to continue using these, not revert to Struts. Plus, modern tooling facilitates mixing SSR and CSR, and switching between them as needed.