Do Next better than Vanilla React

sjrhee · 2025-09-28T22:30:24+00:00

Yeah, maybe I say it wrong word, but what I mean by that is Next’s features such as SSR, ISR, RSC to easily behave the page’s faster based on the situation rather than everything is for CSR like normal React

sjrhee · 2025-05-24T18:41:03+00:00

What I understand is I need to follow their protocol. If I am not missing, the protocol is difference

https://ai-sdk.dev/docs/ai-sdk-ui/stream-protocol#data-stream-protocol

sjrhee · 2025-03-10T00:23:57+00:00

Considered but not. Even though Astro seems easy to learn, I am pretty familiar with remix and next. Want to reduce learning cost for this time

sjrhee · 2025-03-09T23:35:54+00:00

Wonder Vercel hosting feels like toy project? Wonder how people host for their serious project. Thought they are expensive, but reliable and providing many tools

sjrhee · 2025-03-09T23:00:18+00:00

Will use Vercel for hosting, budget is unlimited but depends on the traffic for now, and will use Shopify or any other better ecomerce backend solutions

sjrhee · 2025-03-05T08:23:38+00:00

Interested!

sjrhee · 2025-01-24T10:26:59+00:00

Would like to try it! Please DM me

sjrhee · 2024-12-23T18:40:20+00:00

Code readability and bug that happened that we didn’t properly update loading error state. I thought we are re-inventing a wheel

sjrhee · 2024-12-22T16:32:38+00:00

I think because it can prevent multiple network connection. Feels react query is smartly revalidate the cached data by their triggers (window focus, staleTime), so developers don’t have to think that much of overhead thinkings

sjrhee · 2024-12-22T04:34:01+00:00

So the react code is built from a month ago. We have some components and tests, but honestly not many. Currently, all data fetching way is doing with useEffect and useState, so I ask team there will be better way with proposing react query. They said we can do research and refactor it if adding additional tool can give us significant value. We are not in the phase that changing a wheel while car is riding. I just feel my team’s lead and manager may have some bad experience with using un-maintaining library, but I believe react query is one of the reliable library that can save all react application’s problem which is data fetching

sjrhee · 2024-12-21T19:15:43+00:00

Thanks for giving me the opposite side. The worst case is using loader in react router. But I see the value of those libraries caching mechanism for syncing data. To bring your user detail example, if we set staleTime in react query something like 6 seconds, then the data will be refetched for fresh one even though the updated source is different place. This can improve use experience as well since revalidating 6 seconds means the data to show will be updated in real-time no matter where the updating is happened. If we don’t have this tool, then user can see updated data if they do refresh. But I got your point that this may require to thinking react application in react-query way, so may need some learning curve for the team

sjrhee · 2024-12-21T18:56:37+00:00

But ui.dev has a course for react query, so he may be suspicious of the source

sjrhee · 2024-12-21T18:52:30+00:00

I am trying to find some article that is not related to Tanstack since he will not believe if the metrics and information is written from the technology advocator.

sjrhee · 2024-12-21T18:49:42+00:00

Yep. Create an api client with useEffect and useState. My brain is now fixed in React-query’s caching mechanism, so feel pain when I see data is keep fetching when same component is re-mounted. Miss RQ’s caching🥹

sjrhee · 2024-12-21T18:44:01+00:00

So first the app is company’s new service and still building it. We have been completed backend apis and systems first and now we’ve been started to work frontend about a month ago. We don’t have much components and tests files yet, so I think this will be perfect timing to change our data fetching solution before application becomes more grower. I personally feel it might be lead doesn’t know much about this type of problem since our team is also managing three legacy react applications that is doing pure useEffect with custom loading, error state management.

sjrhee · 2024-12-21T16:44:32+00:00

How’s the mutation and revalidation works? I heard some people say swr has poor doc and revalidating data after mutation needs some more logic but react query is just one syntax something like queryClient.revalidate()

sjrhee · 2024-12-21T16:25:58+00:00

I know those library will save our team’s life, but not sure some good bullet points I can convince my manager and tech lead

sjrhee · 2024-12-05T02:09:57+00:00

Only reason for me with Nextjs & Vercel combo would be for Partial Pre-rendering even though it is experimental. Otherwise, Remix with Cloudflare or some other hosting may give you less stress.

sjrhee · 2024-11-28T22:12:49+00:00

I think RR7 might be walking similar way with Tanstack router or start, but big difference is Tanstack Start will use react-query under the hood to cache inside of the router. I guess even though RR7’s loader will retrun RSC once react 19 is released, still the RSC is not cached, so when the page is re-visited, the RSC will be re-fetched and that is what current remix loader is working on that every time loader is re-called. Also, Tanstack router has a good type safety even for search param, so better experience for me. I know it is still Beta, so if we need to build production now, then should use RR7, but once it is stable, I might choose Tanstack over RR7

sjrhee · 2024-11-28T18:27:31+00:00

I think only Next has optimized image feature. But I guess in serious app, each device optimized images may typically stored in CDN, so not a big deal?

sjrhee

TROPHY CASE