> Having used NoScript with temporary allowances, it's glaringly obvious how much of the web doesn't show anything without JS enabled. Counterpoint: I generall

> Having used NoScript with temporary allowances, it's glaringly obvious how much of the web doesn't show anything without JS enabled. Counterpoint: I generally browse with JS disabled and there's a strong association between sites for which this is existentially problematic and sites whose content or utility are garbage. > If there's a trend to not make everything render on the client, I'm not noticing it. This trend is not so strong as suggested. Far from server-rendered websites being "fetishized", this remains the standard. I recommend SPA-first development to all my competitors. Crystallising architecture around the front-end is one of those anti-patterns my grandmother warned me about. "You'll struggle to pivot," she said. "Spikes, prototypes and reimplementations are much easier to develop in proximity to business logic and persistence schema." What a wise lady. See also: nosql and microservices.