SPAs Were a Mistake (gomakethings.com)

Article summary

The article argues that Single-Page Applications (SPAs) are a mistake, citing the added complexity and fragility they introduce. The author claims that SPAs often attempt to recreate features that browsers already provide for free, leading to unnecessary code and potential errors. However, the article acknowledges that SPAs can be suitable for certain use cases, such as media sites. The author plans to discuss alternative approaches, like Multi-Page Applications (MPAs), in a follow-up article.

Main themes

• SPAs vs MPAs
• Caching and performance
• Offline support
• Complexity and fragility
• Network conditions and device capabilities
• Server-side rendering and alternatives

What commenters say

• SPAs are not inherently bad, but their application has been too broad and often misguided.
• The benefits of SPAs, such as caching and offline support, can be outweighed by the drawbacks, including increased complexity and potential performance issues.
• Properly implemented SPAs can provide a better user experience, especially in situations with poor internet connectivity.
• The choice between SPAs and MPAs depends on the specific requirements and constraints of the project, and a one-size-fits-all approach is not suitable.
• Some developers argue that SPAs are necessary for certain types of applications, such as those requiring offline support or complex client-side logic.
• Others contend that the benefits of SPAs can be achieved through alternative approaches, such as server-side rendering or caching, without the added complexity.
• The performance and usability of SPAs can be highly dependent on factors like caching, network conditions, and device capabilities.
• Developers should carefully consider the trade-offs and requirements of their project before deciding between SPAs and other architectures.