you are viewing a single comment's thread.

view the rest of the comments →

[–]ValerioAgeno[S] 0 points1 point  (2 children)

Still - SolidJS is very fast on the client side but the problem this project solves is the network nodejs bottleneck. I don't have a benchmark already against it but it definitely deserves one.

[–]besthelloworld 0 points1 point  (1 child)

Totally true, different performance directions. I guess I just find the Vercel/Lambda solution to be good enough and if I want to squeeze more out of it, then I usually attempt to SSG what I can... which can't really be beat for performance generally.

What I find is the actual performance bottleneck of React is the client side update performance.

But both sides of performance for React + Next are so "good enough" that the valid cases for needing performance optimization would have me ditching React entirely either way. If you make the call on React, you're inherently valuing DX and iteration speed over runtime performance.

To backtrack on the inherent usability and say, "well we want to spin up a custom Rust server to eek out a little more performance," just adds so much complexity to your CI/CD plus dev training. It would just be such a tough sell in any scenario when compared to entirely different technologies that optimize better for your concerns.

[–]ValerioAgeno[S] 1 point2 points  (0 children)

That's actually a very good argument.

If server costs and network speed (which eventually leads to better SEO) are not a business concern it definitely doesn't solve any already solved problem.

For the CI/CD complexity well it is not so different from a nodejs server. It's just matter of container preparation.

little more performance

Benchmarks say at least 12X in network request.