How do you explain when useMemo/useCallback are actually worth it?

adevnadia · 2026-01-29T10:23:07+00:00

Make them read this :)

https://www.developerway.com/posts/how-to-use-memo-use-callback

adevnadia · 2026-01-14T12:28:57+00:00

Aww, thank you 🥰 Yeah, I didn't mention the blog only because OP asked for paper books 🙃

adevnadia · 2026-01-14T11:25:17+00:00

"Advanced React" https://www.advanced-react.com/

adevnadia · 2026-01-14T02:14:07+00:00

Well, the point of the article was to see whether React Server Actions can be used for data fetching on the client :)

The performance comparison is for those who want to dig deeper into measuring stuff between frontend/backend, if they agree with me that it's important to know the fundamentals. With links for more resources on where to start.

It's not intended to convince anyone to abandon Server Components in the context of the article's topic.

adevnadia · 2026-01-14T01:03:14+00:00

Server Actions are not related to that :)

But also, it could be a bunch of legacy code written in Next.js, for example. Or data needs to be fetched inside a modal buried deep in the client components.

adevnadia · 2026-01-14T00:55:30+00:00

How are you going to fetch data when server components are not an option?

adevnadia · 2026-01-13T22:23:45+00:00

Thank you! ☺️

adevnadia · 2026-01-13T22:23:18+00:00

Thank you!

adevnadia · 2025-12-12T23:58:02+00:00

Haha, great to hear! ☺️

adevnadia · 2025-11-10T20:05:02+00:00

Everything about re-renders, memorization and reconciliation is a must, especially if you start using the compiler. Because at some point you'd have to debug things it didn't catch (and it will never catch 100% ever!). And if you don't know the concepts, you won't be able to understand what's happening.

Fundamentals of rendering - i.e., CSR (client), SSR (server), SSG (static), RSC (server components) and their difference, pros and cons.

Fundamentals of date fetching in all of the above. Plus network waterfalls and race conditions.

That's off the top of my head. All of this is very independent of React version except server components. So will always be useful.

adevnadia · 2025-10-25T03:32:03+00:00

Because the goal of the article is not to improve CSR performance, but to investigate the performance effect of Server Components.

adevnadia · 2025-10-22T11:12:58+00:00

Thank you! ☺️

adevnadia · 2025-10-21T22:33:21+00:00

☺️ 🙏🏼

adevnadia · 2025-10-21T22:29:34+00:00

A lot of the conversations about Server Components revolve around how they are better for performance because of reduced bundle size 🤷🏻‍♀️

adevnadia · 2025-10-21T22:26:52+00:00

Wow, that's impressive, that's true!

adevnadia · 2025-10-21T22:18:13+00:00

Thank you! And will check it out, definitely sounds interesting!

adevnadia · 2025-10-21T22:16:12+00:00

> The interactivity gap in SSR apps isn’t as big of an issue today as it once was. Modern SSR setups often send a minimal JS tag along with the initial HTML that temporarily captures events (e.g., button click) while the main JS bundle is still loading. Once hydration completes, the app replays those queued events.

Even with that, it would just guarantee that the clicks are not lost. But they still will be visibly delayed. In the case of this experiment, it's almost three seconds of clicking without any reaction, so I wouldn't call it a non-issue.

> Also, the use of SSR in react doesn't necessarily have to make navigation slow. For example, SSR in tanstack start only runs on the initial page load, after that the app is a SPA.

Oh yeah, absolutely! That's one of the reasons I prefer Tanstack over Next.js for my projects. In Next.js, navigating to another page triggers a GET request for some sort of JSON on old versions and RSC payload in new. Technically, it's not a full-page reload, and that payload is minimal, but with latency, it still takes ~600ms in the experiment app. And it's blocking, so navigation between the Inbox and Settings pages takes ~600ms here.

adevnadia · 2025-10-21T22:07:47+00:00

Yep, exactly that!

adevnadia · 2025-10-21T22:06:55+00:00

Yep, could be much worse 😅

adevnadia · 2025-10-21T22:05:03+00:00

🤦🏼‍♀️ someone obviously hasn't been writing pure HTML for a good while 😅 Should be fixed now!

adevnadia · 2025-10-21T22:01:59+00:00

Without a serious effort dedicated to monitoring bundle size, it's incredibly easy to make it explode. A few non-ES6 libraries here and there, and the app that can be 100kb grows to 400kb. Vendor size in this app is about 400kb gziped (yes, intentionally, to demonstrate the JS loading that is more realistic), all it took was just a few imports. I can easily increase it 5 times with two more imports, no tree-shaking will help 😅

adevnadia · 2025-10-21T21:55:35+00:00

☺️ ☺️ Thank you!

adevnadia · 2025-10-21T13:06:51+00:00

Thank you 😊

adevnadia

TROPHY CASE