None of my projects want to be SPAs
whatisjasongoldstein.com
None of my projects want to be SPAs
1–10 of 362 posts
Re: None of my projects want to be SPAs
#2Re: None of my projects want to be SPAs
#3Wtf is an SPA?
IE. Purely JS driven, no browser-page loads after the initial page has loaded.
Re: None of my projects want to be SPAs
#4Wtf is an SPA?
Re: None of my projects want to be SPAs
#5Wtf is an SPA?
Re: None of my projects want to be SPAs
#6Wtf is an SPA?
Re: None of my projects want to be SPAs
#7A lot of the "modern" toolsets just aren't worth the extra fluff they add.
Writing SPA's in React, Angular, etc. tend to result in a very heavy first page load, then api calls with poor UX for all actions.
Re: None of my projects want to be SPAs
#8React is about components and you can use React in something like NextJS which is not a single page app but a server rendered pages.
Also, SPA itself is getting outdated concept, now most apps are hybrid of initial bundle followed by a dynamically imported modules. Finally, MVC is a pattern for web pages, the complexity in the client side because what is the being shipped to the browsers are a client side apps with their own router, render functions, state management and APIs.
Re: None of my projects want to be SPAs
#9Once a SPA is loaded you can send tiny crumbs of data faster than any significant SSR.
Re: None of my projects want to be SPAs
#10Why do people insist on comparing the initial frontload of a SPA to the page load of every page in their SSR web app? Once a SPA is loaded you can send tiny crumbs of data faster than any significant SSR.
Because a user doesn't care if it's the initial frontload or not.