Which is a better user experience:
1) Download an enormous framework that also runs slower and slower each year on constant hardware, because developers add more features?
2) Download a tiny page which hands heavy lifting off to the server (if you really do that the pages are only about 8kb plus images), and which requests an equally tiny page when the user does something requiring a server response?
It won’t be the same for every app, of course, but most of the content I see online doesn’t need or even benefit from JavaScript. I’ve literally turned it off by default and generally get a better UX… yes with a few exceptions, but only a few.