>On the frontend, you have build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, srcset/responsive images... I remember when the biggest challenge was IE6 compatibility.

It is not necessary to do this. Server-side rendering is still a thing.

I still do a lot of my side projects in ruby on rails, which is maybe not fashionable these days but:

- no heavy js means speedy first paint

- I just use normal minified css, no sass or other junk

- partials means navigation is snappy

Plus it containerizes nicely.

▲

robertoandred 3 days ago | parent [-]

Build pipelines, bundlers, CSS frameworks with their own toolchains, progressive web apps, Core Web Vitals, SEO, layout shifts, and srcset/responsive images have nothing to do with client/server rendering.

	▲	stackghost 3 days ago \| parent [-]
		With server-side rendering you don't need a frontend framework at all, is my point. You also don't need a css tool chain at all, irrespective of whether or not you render on the frontend