The balance has shifted away from SPAs (nolanlawson.com)

Article summary

The article discusses how the balance between Single-Page Applications (SPAs) and Multi-Page Applications (MPAs) has shifted, with MPAs gaining an upper hand due to recent browser developments. The author argues that new browser features, such as paint holding and back-forward caching, have made MPAs more viable. However, SPAs still have their place, particularly for applications that require complex interactions or offline support. The article concludes that the choice between SPAs and MPAs depends on the specific needs of the application.

Main themes

• SPAs vs MPAs
• Browser developments
• WebAssembly
• JavaScript frameworks
• Accessibility
• Application complexity
• System programming languages
• Frontend development trends

What commenters say

• Some commenters argue that SPAs are still the better choice due to their ability to provide fast and interactive user experiences.
• Others claim that MPAs are now a viable option due to improvements in browser technology, making SPAs less necessary.
• A few commenters believe that the choice between SPAs and MPAs depends on the specific needs of the application, with SPAs being better suited for complex interactions and MPAs for simpler applications.
• Some argue that WebAssembly will eventually replace JavaScript, making SPAs less relevant.
• Others disagree, stating that WebAssembly is not a silver bullet and that SPAs will still have their place.
• A few commenters mention that accessibility is still a pain point for SPAs, requiring extra work to ensure an accessible experience.
• Some argue that the size of JavaScript frameworks like React is not a significant issue, while others claim that it can be a problem.
• A few commenters believe that the trend towards using WebAssembly and system programming languages like Rust will continue, potentially replacing JavaScript and SPAs.