I sometimes wonder if the Javascript world has some sort of divine significance, as though they carry the weight of all the developer sins in the world for some

I sometimes wonder if the Javascript world has some sort of divine significance, as though they carry the weight of all the developer sins in the world for some particular transcendental purpose. After all, Dante's nine circles of hell are insufficient for programmers who are able to recurse infinitely. How much further can we go? Consider the descent down, and the contradictions therein, considering JUST data concerns for brevity: 1. SPA ostensibly being marginally more data efficient by shipping the markup/interactivity first, and fetching only the data as needed. 2. REST being too inefficient and cumbersome in practice, the rise of GraphQL to minimize payload over the wire. 3. Lack of SSR impacting SEO, the need to render on the server and sending HTML over on initial payload. (which btw goes against (1) for first render) 4. Impedance mismatch creeping in, seemingly necessitating the need to send data along with the rendered HTML for hydration purposes (again, going against the idea of saving data over the wire) I eagerly await, from the sidelines, news from even deeper depths. Perhaps shipping the entirety of the server code that operates then against a local SQLite database? Which is then kept in sync with the authoritative copy "on the edge"? After all, if simple old SSR is beneath consideration, than we would do well to disdain the notion of a boring centralized database as well.