"The future of the Web is what suits our business model" /s
But in all seriousness, the web has websites, it has apps, it has games. Pick a tool that's appropriate for the job and forget about what is the past/present/future.
But in all seriousness, the web has websites, it has apps, it has games. Pick a tool that's appropriate for the job and forget about what is the past/present/future.
For example, my app has a main screen that needs to be client rendered. It also has a user settings screen that could be implemented as a traditional server rendered page with no JavaScript, except it's a lot more practical to build everything inside the same project and technology. Apps and their marketing pages are often put on different subdomains for the same reason.
Metaframeworks that blend rendering modes help users get a lighter page load where appropriate, with less developer effort.
I just learned about Astro the other day. It allows you to blend components from SPA frameworks together. Is that what you mean?
They're sometimes called stuff like "a React framework", depending on whether the speaker considers React a library or a framework.
https://example.com/app might be a SPA and https://example.com/profile might be server rendered and https://example.com/blog might be a static site. And that's great!
Pick the right tool for the job :)