I might be wrong of course, but I understand what bfgoodrich is saying as follows: Back in the day, before we had all the build pipeline, npm, utility-first, e

I might be wrong of course, but I understand what bfgoodrich is saying as follows: Back in the day, before we had all the build pipeline, npm, utility-first, etc css people were already building websites and those also worked just fine. I sort of agree. There was very little you couldn't do that was a result of the tools to build the sites. The only real constraints were imposed by what technologies were in the standards and which were implemented by browsers. If you want to build a website today with what is 'normal' tech, you have to learn a whole lot more and people spend tremendous amounts of time in bootstrapping code in order to produce some JavaScript and CSS that in the end provides hardly any added value compared to server-side rendered views with sprinkles of JavaScript. Apps like Slack are probably an exception to the server-side rendered argument, but I think you'd be better off building those in non-web technology to begin with. Either way, if you want to spend your days building layers upon layers of abstractions in order to prevent having to fetch some HTML from the server, be my guest.