3 ms·
>Apps, not sites. It’s even in the name, Single Page Application...you should probably build most apps as SPAs. The whole concept of Single Page Applications w
by unclebucknasty 4y ago
>Apps, not sites. It’s even in the name, Single Page Application...you should probably build most apps as SPAs.
The whole concept of Single Page Applications was misguided from the start, and the reason for that is even in the name. Pages and applications should never have been mashed together. The moment we decided we needed apps, we should have abandoned the static document-based "page" concept altogether.
We shoul've replaced it with a browser-hosted VM-based execution environment in which proper apps could be built.
It's never been a question of MPA vs SPA. The question has always been how do you build browser-based applications in a way that escapes the impedance mismatched document/html model?
- dsego 4y agoWe had that, remember flash and java applets? Well, it wasn't that great.
- unclebucknasty 4y agoSort of. But, was the problem the principle or the execution? Those "solutions" pre-dated the idea of building robust apps with native Web-idioms (e.g. SPAs). So, they tried to layer on an entirely different non-Web platform, including a completely new, non-browser native UI framework. And, we're now delivering entire frameworks to the browser to support, essentially, a kludgy VM-based approach that just shoehorns app concepts onto the HTML document model. So, what I'm suggesting is more of an in-browser hybrid. Assuming the only two approaches are Flash or React seems like an industry-wide failure of imagination.