Comment by nicce
7 days ago
How would you say that this solves the similar problems as React Server Components?
E.g. yesterday's discussion - https://news.ycombinator.com/item?id=43929054
Basically, how do you remove the gap (network implementation) between back-end and front-end, so that you don't need to think about the difference. You define the components in same place, and can add dynamic features for client-side when you need them, but the rest of the code can be even compiled to static in a seamingless way.
Without solving this, I wouldn't really use a new framework that doesn't challenge the similar problem.
The challenge is that there is a difference. Client is "reactive" and server rendering is static. The SSR output needs to be some sort of hybrid, which Hyper is absolutely going to tackle. This is another area where simplicity shines. Hyper components renders exactly the same on server and client, but when SSR detects a dynamic piece it renders a "stub" to be filled by the client part.