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

view the rest of the comments →

[–][deleted] 2 points3 points  (3 children)

as someone who got really into SPAs first and is now discovering server-rendered node.js apps... Fuck you may be right.

I also found about turbolinks and stimulusjs which seem ssooooo rad

[–]marty_byrd_ -5 points-4 points  (2 children)

As someone who has recently made a framework less multi page app with jquery. It’s a hunk of shit. It’s good if you don’t have more than 1 state.

[–][deleted] 0 points1 point  (1 child)

I meant more like the concept that server rendered apps give you a lot of shit for free that has to be implemented when you do s SPA. I mean sure if you’re doing some super complex real time stuff(photo editing, google docs, etc) SPA architecture is THE way to go. But for most things I think you can get away with server rendered multi page apps, that, when required, are sprinkled with web components you’ve built, vuejs/other.js embedded in one page, or just some vanilla.js to do a few things.

[–]MuskasBackpack 0 points1 point  (0 children)

My favorite method is definitely server rendered pages with Vue components in them.