This is a gross exaggeration. More than not, random websites still work without JS for basic content but a few big ones don't.

The problem is that a lot of frontend web dev is driven by the React ecosystem which requires you to have SSR figured out for "no js on the client" to even partially work, which, if you ever tried to go all the way (e.g. RR v7 w/ full SSR) in a not-a-toy project, is not easy to set up and think about by any means, because your server has to be a js one at which point your entire server-side solution consist of node or node-like js server, postgres or mysql (with pooled connections through something like mysql2 and probably drizzle), something for caching like Redis, some complex process manager like pm2... i say complex because if you want to have a high performance fault tolerant gracefully restarting automatic new code deploying system ... and all of that with caching layer(s), Redis sending cache updates without you polling etc., you have to implement and test these yourself... Everything async and thinking in long term running processes and thinking about the async loop instead of a "php-like" model. Components being a potential source of memory leaks, thinking about components having to work on client and server environments, keeping SSR performance (in the sense of component rendering complexity) up etc.

This is not something just anyone is going to rush into. Bigger teams or js/ts evangelists will eventually arrive at that point if they're running something where no-js (really a side effect of seo goals) is important, but "normal people" will spend this time and engineering effort elsewhere.

I think the industry in general is moving past React, as now, and definitely in near future, the only thing that matters is ideas, the rest is for the LLMs to figure out, and so the "frameworks" are going to completely disappear from people's minds as "programming" essentially becomes "telling the AI what to do" and the AI writes asm or even binary. That is when, no JS, may become more viable again lol.

People, including me, resist it, but in the future "programming" is not going to be about writing code (or even checking it, we're way too slow and error-prone to do that), but about coming up with ideas of how to capture real world problems in an IT system, and how to solve those problems by existing (or novel) ways, picking the right tools for the job (say a statistician picking the fitting metric to capture some property of the system that will actually project meaningful observability improvements and not be "just a bunch of noise") and making the right architectural decisions in terms of correctness, performance, scope, taking into account deadlines and budget. And being the domain model glue. Everything else, all the nitty gritty we used to call programming, all the <insert a quadrillion of CS jargon keywords>, is going to be done by AI ... it's a mag 9.5 quake tsunami and it can't be stopped now.

This might completely wipe out things like React (which are largely made for humans writing the code, not for humans consuming the output of that code) faster than anyone thought possible.