Half of the article is just ragging on a specific subset of poorly designed SPAs (those that don't use HTML 5 history mode with proper server side routing set up), which the author acknowledges before finally moving onto other points.
The other half I'm not even convinced these are real problems:
A fantastic example of the problems created by the SPA approach is parallelization of work. If you have a team of multiple people, or God forbid, multiple teams working on the same SPA, you need to come up with a good way to support this. Instead, you can just have each of those teams build their own web application. Each of those applications can be connected to every other one built at the same time by the same organization (as well as to every other web application residing anywhere, if you want to) — in fact relying on the core strength of the web.
This paragraph I guess presents a problem and it's "ROCA" solution, but the solution proposed works for SPAs too. You can just make multiple SPA applications.
Comments
Half of the article is just ragging on a specific subset of poorly designed SPAs (those that don't use HTML 5 history mode with proper server side routing set up), which the author acknowledges before finally moving onto other points.
The other half I'm not even convinced these are real problems:
This paragraph I guess presents a problem and it's "ROCA" solution, but the solution proposed works for SPAs too. You can just make multiple SPA applications.