3 ms·
SPAs are also useful even where they aren't strictly needed, which upsets the purists. Once you have decided that you orient your teams around SPA architecture,
by incrudible 3y ago
SPAs are also useful even where they aren't strictly needed, which upsets the purists. Once you have decided that you orient your teams around SPA architecture, going the extra mile for whenever an MPA might do things better (by some metric) becomes a tough sell. The things that web developers believe should matter to users don't necessarily matter to the business as a whole. This is another instance of "worse is better".
- zokier 3y ago> Once you have decided that you orient your teams around SPA architecture, going the extra mile for whenever an MPA might do things better (by some metric) becomes a tough sell. Another aspect is here is that if you have people split up (more or less strictly) in backend and frontend devs, then SPA kinda follows naturally
- onemoresoop 3y agoI understand the SPA team argument but keep in mind how much complexity SPAs add to projects and how much more resources those teams eat. As a dev I'm okay with this as this enables more work for us devs but having done work with simpler technologies that were easier to maintain, were simpler and so on I can't shake the feeling of wastefulness SPAs give me.