It doesn't need to. The "everything must be a web app" mindset is completely unnecessary and actively harmful to accessibility. I've seen far too many "redesigns" turn a site of static pages or even forms into a horribly slow and buggy limited-browser-support SPA that excludes access for no real reason.
The information delivered is the author's philosophy on website design and implementation complexity.
I can easily tell that the author does not approve of overly complex websites, and thinks they lead to poor experiences for the developer and user.
Contrast this with a website for some hot new web 3.0 buzzthing, where "what is this thing" is not answered in lieu of presenting a shitload of "why we/this thing is so great". An example of this is npmjs.com. Nowhere does it actually state "this is a package manager for javascript", if you didn't already know it.
To its credit, at least npmjs.com is still readable without JS. However, it is lacking in terms of what it's about, and reminds me of GE.com - the latter maybe somewhat excusable because GE makes so many different things, but I don't think NPM is quite so large...