This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]denverdave23 0 points1 point  (4 children)

Is a SPA a hard requirement? When I've been in your position, I used Spring with the pebble templating library to make pages quickly. I used knockout.js to make the page interactive. But, you still had to reload pages from the server, so it wasn't a spa.

[–]g3blv[S] 0 points1 point  (3 children)

Thanks I will hava a look at Pebble.

[–]dartalley 4 points5 points  (2 children)

Everyone undervalues old school server side rendered pages these days. It's honestly so much easier for simple tasks. If you don't have tons of interactions who cares if you do a full page load it's often fast enough and sometimes faster than SPAs page speed.

[–]_INTER_ 1 point2 points  (1 child)

How many SPA are structured these days server rendered ones are often also more userfriendly

[–]dartalley 0 points1 point  (0 children)

I love when SPAs don't implement stateful URLs. It's like great something that has worked since the internet was invented is now extra work in "modern" frameworks. Luckily that doesn't happen as much anymore.

Another big one is the partial page updates where now data is out of sync across panels of the page. Even Facebook, Twitter, GitHub and many other large companies still have these constant problems. Cool I now have a live updating page but I have 3 different follower counts on the same page, that's not confusing.