|
|
|
|
|
by nfw2
64 days ago
|
|
1. Rendered content, if there is enough of it, will be more content to send across wire than a cached bundle. 2. Cached bundles are cached. Network doesnt matter when its cached 3. Even bottom of the barrel motorolas are not wimpy nowadays 4. The obvious reasons why I dont want my aws box to do rendering is because it will need to everyone's rendering, and how big "everyone" is in not constant. It's another moving part in a complex system that can break. Also because I have to pay for the box. 5. Fast networks are becoming more and more ubiquitous 6. The performance gains are for a static site, which won't necessarily be representative of typical saas. How do you measure the risk and cost of my site breaking because my date rendering server got overloaded? |
|
They are: https://infrequently.org/2025/11/performance-inequality-gap-...
That said, RSCs and the rest of the "let's render a static site but let's also send a multimegabyte bundle for 'hydration'" is still wrong