SebastianVerified account

@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.

@dan_abramov Data usage is not less on the initial page load when you're forcing me to download 200KB of frameworks.

@feross This is not an inherent fault of SPAs. It’s fault of code organization and lack of tools/culture of code splitting.

@feross Again, modern SPA frameworks let you render initial state into HTML. JavaScript code is an enhancement over that.

@dan_abramov I get that you can make things really nice with extra effort. But should this be the default recommendation for every app?

@dan_abramov Would you recommend that Wikipedia switch to React since you can do initial rendering in HTML and rehydrate it?