This kind of app might be fine on the platforms where it's tested, but tends to have severe performance problems for others. Many of us have had our computers bogged down by very resource-intensive web apps, and this "Do everything on the client" philosophy is a common culprit. Exchanging ~50 ms on the server for ~250 ms on the client can become really user-hostile as you get further from the best-case scenario.
No matter which side of the fence you develop on, if you have a page that is not performing, you have a usability issue and it needs to be addressed. This is less of an issue with the technology and more of an issue with how the technology is being uses or rather misused.
I understand that people are dogmatic about this subject and that is why I received the downvotes, but to ignore the fact that it is the way the web is moving is to ignore a massive trend that is well underway.
I have the impression though, that a single page app will reveal problems like increased memory usage where in the classical way of writing webapps would be hidden by the constant page reloads (where hanging objects would get GCed anyway).