this post was submitted on 21 Oct 2024
61 points (89.6% liked)
Programming
17483 readers
199 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
By SPA I mean "single page application" it's currently the dominant approach and powered in a large part by technologies like react and node. I'm not certain when it started precisely... with technology it's more a case of "rising to prominence" rather than "first happened" I think it probably really started going around 2014 with HTML5?
SPAs are still pretty hot but they've waned in popularity due to overuse and general complexity. Essentially your website becomes a single page that just swaps out what's shown to the user as they "navigate" between different parts of the site. When well done this can make a site incredibly responsive, but it's often quite poorly done and responsiveness can end up blocked by server requests anyways.
Interestingly the pendulum is now swinging the other way. If you look at next.js for example, server generated multi page applications are back on the menu!
Yea, I don't want to totally shit on SPAs but server-side rendering has a lot of advantages and is so much fucking simpler.
I'm a PHP dev and DB specialist in my day job - there are a lot of good server-side tech options.