Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TanStack Start Now Support React Server Components

tanstack.com

Post reply on HN
Print view View original

71–79 of 79 posts

Re: TanStack Start Now Support React Server Components

#71

Post by nfw2 »

gherkinnn wrote: post #51
nfw2 wrote: post #20

Earlier quoted context omitted.

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 pa…

Is serialising a model and building JSON that much more expensive than rendering HTML?

It is less expensive?

Re: TanStack Start Now Support React Server Components

#72

Post by nfw2 »

_heimdall wrote: post #63
nfw2 wrote: post #9

I still don't get why RSC is better. This post takes things for granted that don't seem obvious to me. Why would I want heavy rendering tasks to all be done on my wimpy aws box instead of the clients macbooks and iphones? Shipping moment for dates is a pain sure but that can be chunked and cached too? It's hard to imagine the benefit of reducing bundle by X kbs could really be worth doing a roundtrip to server whenev…

Just because data can be rendered to DOM on the client doesn't mean it always should be. I'll try to render HTML wherever the data is stored. Meaning, if the data lives in a hosted database I'll render on the server. If data is only stored on the client, I'll render there. Its less about bundle size in my opinion and more about reduced complexity and data security. That said, I've never been a fan of RSC and don't se…

There is no additional data security if you are sending a rendered version of it to client instead of raw version.

Data that will be rendered on the client generally should be sent to the client in my opinion because you can easily determine if bugs are a rendering problem or a data problem without sifting through server logs.

Re: TanStack Start Now Support React Server Components

#73

Post by _heimdall »

nfw2 wrote: post #72
_heimdall wrote: post #63

Earlier quoted context omitted.

Just because data can be rendered to DOM on the client doesn't mean it always should be. I'll try to render HTML wherever the data is stored. Meaning, if the data lives in a hosted database I'll render on the server. If data is only stored on the client, I'll render there. Its less about bundle size in my opinion and more about reduced complexity and data security. That said, I've never been a fan of RSC and don't se…

There is no additional data security if you are sending a rendered version of it to client instead of raw version. Data that will be rendered on the client generally should be sent to the client in my opinion because you can easily determine if bugs are a rendering problem or a data problem without sifting through server logs.

There absolutely is. I can fetch a full user record from the database and use it to render on the server, not ideal but still secure. Send the full user record to the client and that data is now more at risk.

Re: TanStack Start Now Support React Server Components

#74

Post by troupo »

nfw2 wrote: post #70
troupo wrote: post #45

Earlier quoted context omitted.

"I'd rather base my opinion on my own personal anecdote than based on stats". My "they are" was referring not to your specific Motorola, but to the "bottom barrel". Which, while improving, still doesn't even remotely justify the bundle sizes or "fat networks". --- start quote --- The median mobile page is now 2.6 MiB, blowing past the size of DOOM (2.48 MiB) in April [2025]. The 75th percentile site is now larger tha…

Ask any ux specialist, observing base reality (observe someone using x) gives a better impression of usability than any statistics will

So please do observe reality. Even high end phones (and desktops) often struggle with the bloat and inneficiency of modern software.

Lol. My high-end gaming computer spins its fans like craze just scrolling through Twitter ffs.

Re: TanStack Start Now Support React Server Components

#75

Post by troupo »

zarzavat wrote: post #67
troupo wrote: post #46

Earlier quoted context omitted.

> It's not 2010 anymore. Client compute is fast. It's not: https://infrequently.org/2025/11/performance-inequality-gap-...

Yes it is. Even a cheap Xiaomi is fast enough to render any application you can think of. React is not the bottleneck. The bottleneck is all the bloat in the application code. Webdevs act as if optimization isn't a thing and the only solution to any performance issue is to add more hardware. This explains the popularity of server-side rendering: it's a way of solving a performance issue by "adding more hardware" to t…

You... sort of re-iterate the article I linked

Re: TanStack Start Now Support React Server Components

#77

Post by 0xblinq »

vixalien wrote: post #58

Am I the only one that despise TanStack docs? most of them seem AI-generated, incomplete and repetitive.

You’re not alone. They are terrible. For some reason they want them to look like an “app”.

It was even worse a few months ago when the background was constantly changing colors. Fortunately enough people complained and they removed it.

Re: TanStack Start Now Support React Server Components

#78

Post by bodash »

gherkinnn wrote: post #11
hliyan wrote: post #6

Can we please go back to template-based server rendering (e.g. JSP, PHP, ASP, Handlebars/Mustache) and use JS for user interactivity only? Tired of seeing this cycle play out with a new framework every 5-6 years.

JSX is easily the most productive templating language out there, I fail to see your point.

Astro might be the closest option here. JSX can be used as a templating language for it, and devs can still opt-in for full clientful islands.

Re: TanStack Start Now Support React Server Components

#79

Post by abraj »

vixalien wrote: post #58

Am I the only one that despise TanStack docs? most of them seem AI-generated, incomplete and repetitive.

To tell you the truth, I first landed on TanStack Start docs page a few times earlier. But somehow just couldn't get past their Getting Started page because of the annoying Partner Logo Ads on their docs pages. Tho, I really like their apprach to RSC and therefore am surely giving TSS a try.

I know that a company needs to make money to grow the team and build good software. It's just that it would be really great if the Ads were not so intrusive! I kinda believe Docs pages hold some kind of sanctity in devs' minds, and frankly I initially (and my bad - incorrectly) judged the team who is willing to 'pollute' this place with such banners on "all" of their docs pages.

Post reply on HN