[oweqruiowe]

I agree, but do want to say that server-side rendering is a lot more complicated than just "be able to render my app on the server as well". We went down that road with a large app and the team was stoked and promising how awesome it would be, but it turns out it just slowed down the experience and users hated it.

I'm a lot more hesitant about SSR now. Users don't mind spinning wheels as long as they can see something happening.

[couchand]

In a world faced with a climate crisis, client-side code faces the burden of proving that it is worth the value. Unfortunately, today companies are free to externalize their energy use by forcing users to run compute for them, in a significantly less efficient environment, and repeatedly. This insanity should not be allowed to continue.

A new language is in the perfect position to structure components so that they can be cleanly rendered on a server first, and rehydrated on the client as-needed. Trying to do that backwards will always result in less developer and user satisfaction. That doesn't mean it's right to just keep doing things the bad old way.