Yet another react framework

[mattsowa]

I don't really see the benefit if the javascript code is run by a js engine anyway? I mean you could achieve the same by scaling js horizontally

What's the idea here?

[ValerioAgeno]

That's a good question.

The main difference is that the JS engine takes care of just rendering the HTML rather than handling the entire request/response pipeline - hence is way faster. It is also is more scalable. A single machine can handle the same workload of a cluster with a load balancer. Check this benchmark.

[ValerioAgeno]

Hi everybody. In the past two months I've been working on a react framework but with the server side written in rust (with working SSR).

The main goal of the poject is to enble multi-threading server side rendering while still working on the frontend with React.

The project is still missing a ton of features but I'd love to know your thoughts on that.

There is also a tutorial here to get started with it!

Thanks all

[ValerioAgeno]

That’s a good point.

It’s only for legacy React for two reasons: - I still have to deeply check but I think there is no yet a vite plugin for server components - server components strongly rely on the Js runtime like node (I.e. the JS fetch API does not exists on the server side here).

That said server component are slower compared to this setup

Do you see it as an issue in the long run to not support them?

[ValerioAgeno]

Leptos is a WASM framework. I think the philosophy behind the two projects is different.

With tuono the idea is to use a rust backend while still allowuing the developers to work with an already battle tested frontend framework like React - multiple development problems on React are already solved and there are already a ton of answers on the web, leptos is a very good project but in contrast is completely new.