yosh

@dan_abramov There are use cases for single-page apps, but they're SUPER overused today. And they're worse – buggy, slow, and finnicky.

@feross Can you say the same about native apps? Aren’t native apps “single-page apps” too, in a way? The problems are real but not inherent.

@dan_abramov Browsers are really good—and, most importantly, FAST—at rendering HTML. You lose a lot with SPAs on the web.

@feross What do you mean by “fast”? I can’t imagine serving HTML at 60fps.

@feross SPA doesn’t mean there is no HTML. You can render on the server and boot up from that on client once JS is loaded.

@dan_abramov If you're serving wikipedia, why do that? Why introduce all that complexity and tooling? That's the point I'm making.

@feross That SPAs require a lot of complex tooling is a problem we have today. Doesn’t mean it can’t be solved, or is not worth solving.

@feross If there was no complexity cost, SPA would have been a better choice because UX would be faster and data usage would be less.