Earlier quoted context omitted.
By now, making UI with (by now not completely) SPA frameworks specifically made for that task is just better developer experience. I won't go back to pretty much html string concation via templates. Why do people keep pretending it's better in any way is lost on me.
Yeah the backlash against SPAs doesn’t make any sense. Server side rendering is fine for documentation etc. but full applications don’t want to be simulated on a server, client-server makes complete sense.
Webservers shall create and provide the readily HTML so browsers can render the website without JavaScript. Actually text-browsers should render it and also allow disabled persons using it without hassle.
Instead SPA (or more direct JavaScript) is used to force the browser to assemble the HTML and it is slow and waste resources. Creating website which create load on the client-site is bad because we’ve power on the server dedicated for this task - not so on client.
Looking back web-developers need something imperative and more direct than CGI, PHP or JSP. The initial backslash against JS was right. I sadly shipped JS.
When a powerful application is needed? Make a native application and use an appropriate toolkit (Gtk or QT).