2 ms·
My aversion to SPAs is due to working with non-SPA tech in the past. While portal systems got by with little need for JS for anything other than client side val
by gadflyinyoureye 4y ago
My aversion to SPAs is due to working with non-SPA tech in the past. While portal systems got by with little need for JS for anything other than client side validation. The sever would work the business logic and render a view. This was fast, simple and understandable. SPAs require tracking state on the client side, and probably on the server side. Then you add SSR which often dictates your server side tech (mostly Node). Now I can’t use Go or Java.
As a result I have a complex build and deployment process (relative to templates packed away in a Jar) for little velocity benefit.