| I find it funny that article argues SPA frameworks were pushed with cargo-cultism without evidence, while making proclamations of doom and being fairly light on substance. I think the author has some valid points. I agree vanilla JS and SSR is a better fit for a lot of situations. (I will admit some bias as someone who's mainly worked in Angular-Typescript) AngularJs started gaining traction around the rise of "apps" and the iPhone. SPA was a way to have an "app" in the browser with all the complexity that went with it. It also was a way to share an aritecture with mobile apps -- the browser is a client which calls the same public API as mobile devices. Obviously you can call the same public API with SSR, (though it might have been more tricky before the rise of microservices), and not all webpages need to be "apps", but I think this was the argument at the time. I think a lot has changed in 10+ years and those architectural decisions make less sense. With static data and a form or two, SSR and vanilla JS is perfect. Resume-padding engineers might try to make it more complicated than it needs to be, but they're wrong. I would not like to work on a complex web app with 10 other engineers that does not have some kind of component architecture. |