What are some pros and cons of Single Page vs Backend Heavy apps?

Prahlad Yeri - Jul 13 '19 - - Dev Community

Currently the webdev world is in a kind of flux. The "FE Way", as some would call it, involves some mix of libraries like angular and vue for things like browser based routing (using hashes) and creating an MVC, plus some other libraries like react, material-ui, prime-ng, etc for handling the views. The backend is just a REST API and free to be implemented in any language you want.

The "BE Way", on the other hand, involves some old (but still proven and stable) libraries like jquery, bootstrap, etc. coupled with a backend language like php or python for handling web requests and HTML templating.

Which of these two ways is your preference and why?

The fe-way appears cool because you've separated your backend logic entirely into a REST API, now it doesn't matter whether its python or php, django or laravel. In a sense, its future-proof, isn't it?

Yet, I don't see many people moving to the fe-way, they are still using laravel, django, flask, etc., so what's holding them back still in the be-way? Is it just fear of the unknown or are there any genuine concerns with doing things in fe-way? Some basic issues I can think of are browser incompatibilities, lack of a robust and stable framework (angulars & vues keep coming and going, or keep reinventing themselves), npm problem of too many packages, etc.

If these issues were resolved, I don't think there'll be any major bottleneck for moving towards the fe-way.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player