Re:Websites have evolved back to static HTML/CSS/JS files
by chrysoprace on Sunday March 08, 2020 @07:22PM
(#22521397)
No, it doesn't need to be, but it is nicer. There's quite a lot of complexities to my country's tax law (as with any country's tax law, really) and it's heavily simplified by giving you highly dynamic choices. Trying to use my country's immigration site, which has some JavaScript sprinkled on but is largely static, is a largely inferior experience.
[ Parent
| on HN ]
Re:Websites have evolved back to static HTML/CSS/JS files
by ShinTakuya on Sunday March 08, 2020 @11:44PM
(#22522823)
There's no reason you can't query a backend for the complexities and present those dynamically to the user. For instance, quite often an SPA might ping the backend for a list of states or provinces once you've selected a country.
Re:Websites have evolved back to static HTML/CSS/JS files
by chrysoprace on Monday March 09, 2020 @12:02AM
(#22522901)
Sure. It's up to the engineer implementing said app to determine the best fit for the project.
At the end of the day, you have to choose what's right for your users; whether that's a seamless experience with no full page reloads, or the occasional full page reload.