About the server load, what you see as an advantage I see as a downside. The average phone price in the US is 200$, can that phone handle a 1000 rows of table manipulation? This is my problem with SPAs the most people don't get the price of JS. Don't get me wrong I am a JS developer, but I specialize on performance. What most people don't get is 500kb of images are not the same as 500kb of JS.
And the most common problem is SEO and analytics tracking. I implemented all the possible solution that exist by this days and either they make my team want to kill themselves because of the development complexities or they can bring same results as MPA.
Note: I don't hate SPA, on the contrary we use them but for a specific case where it makes sense like dashboards or apps like github. There is no advantage of using a SPA for a presentation, company or in most cases Saas sites
The average phone price in the US is 200$, can that phone handle a 1000 rows of table manipulation?
Totally get your point! The way I envisage things, the manipulation of rows will still happen on the backend itself through SQL queries (or nosql equivalent in case of mongodb, etc.). Where front-end can play a part is things like url routing and DOM rendering. Right now, these roles are also played by backend with frameworks like flask/laravel and template engines like jinja2/twig. Aren't you better off by moving all that logic to the client browser instead?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
About the server load, what you see as an advantage I see as a downside. The average phone price in the US is 200$, can that phone handle a 1000 rows of table manipulation? This is my problem with SPAs the most people don't get the price of JS. Don't get me wrong I am a JS developer, but I specialize on performance. What most people don't get is 500kb of images are not the same as 500kb of JS.
And the most common problem is SEO and analytics tracking. I implemented all the possible solution that exist by this days and either they make my team want to kill themselves because of the development complexities or they can bring same results as MPA.
Note: I don't hate SPA, on the contrary we use them but for a specific case where it makes sense like dashboards or apps like github. There is no advantage of using a SPA for a presentation, company or in most cases Saas sites
Totally get your point! The way I envisage things, the manipulation of rows will still happen on the backend itself through SQL queries (or nosql equivalent in case of mongodb, etc.). Where front-end can play a part is things like url routing and DOM rendering. Right now, these roles are also played by backend with frameworks like flask/laravel and template engines like jinja2/twig. Aren't you better off by moving all that logic to the client browser instead?