Sign in

Michael Frieze

@frieze.dev
103 followers 148 following 85 posts

Web developer based in Metro Detroit 🧑‍💻

PostsRepliesMedia
Michael Frieze @frieze.dev · 26/06/2026
Awesome!
100 0
Michael Frieze @frieze.dev · 30/09/2025
I find it hard to believe this is about money. Maybe he knows something I don't, but this seems like a bad business decision to me. IMO, this is more ideological.
000 0
Michael Frieze @frieze.dev · 30/09/2025
It's going to be a lot more difficult to get the motivation to help people with Next or to defend it. I can't believe he would do this. I feel bad for Vercel employee's.
160 0
Michael Frieze @frieze.dev · 12/08/2025
The inconsistent data in Next hasn't really been a problem for me yet, but it would be nice to have.
120 0
Michael Frieze @frieze.dev · 12/08/2025
The prefetching in Next uses the Convex usePreloadedQuery hook and the prefetching in Start uses react query hooks like useSuspenseQuery, so I'm not sure how difficult it would be to implement this in Next with Convex hooks.
120 0
Michael Frieze @frieze.dev · 12/08/2025
Yeah, prefetching Convex queries in TS Start loaders came to mind while reading this article. I've been working with Start and Convex lately and loving it. I think prefetching Convex queries in Next RSCs still has this issue with inconsistent data. Do you plan on using a timestamp for this as well?
110 0
Michael Frieze @frieze.dev · 12/04/2025
I hope you feel a little better talking about these things on bluesky where it's not so bad. I know it’s tough to filter out the negativity, but a lot of people really value what you have to say. I definitely do. I get that you've got the team to think about too, though.
040 0
Michael Frieze @frieze.dev · 12/04/2025
I think a lot of people assume RSCs generate HTML and it causes this confusion. I see it all the time on reddit. That's why they think of it like SSG/SSR.
190 0
Michael Frieze @frieze.dev · 30/03/2025
What do you mean by #4?
100 0
Michael Frieze @frieze.dev · 16/02/2025
Me and my partner have the flu! She's a teacher so we can't avoid it. It's pretty awful.
010 0
Michael Frieze @frieze.dev · 15/02/2025
I don't care about the part of your post that makes assumptions about what the react team actually believes instead of what they say in the docs. You don't have to use RR7 or RSCs. You can build however you like, with a framework or create your own framework. Up to you.
110 0
Michael Frieze @frieze.dev · 15/02/2025
react-router will support RSCs soon. You will be able to use them in a SPA without a server.
110 0
Michael Frieze @frieze.dev · 15/02/2025
Interesting. I wouldn't have expected that. I assume you can disable it right?
100 0
Michael Frieze @frieze.dev · 15/02/2025
So you believe they shouldn't recommend using a framework until they have their own framework? Also, they are recommending react-router as a "framework". They are even recommending to use it to build a SPA.
110 0
Michael Frieze @frieze.dev · 15/02/2025
I don't think they are saying a SPA is an unusual constraint. They are recommending react-router to build SPAs. It seems they think of react-router as a framework since it allows you to opt-in to framework features.
110 0
Michael Frieze @frieze.dev · 15/02/2025
I think react-router is CSR by default and it's recommended in the docs as a framework.
100 0
Michael Frieze @frieze.dev · 15/02/2025
They are recommending react-router as a framework. Most react apps will need a router. react-router allows you to opt-in to framework features, so I assume they consider it a "framework".
010 0
Michael Frieze @frieze.dev · 15/02/2025
I don't think React was ever MVC. It was inspired by XHP.
140 0
Michael Frieze @frieze.dev · 12/12/2024
This confirms it, Devin really is going to take my job.
050 0
Michael Frieze @frieze.dev · 05/12/2024
Are you arguing it's possible to use RSCs and increase bundle size more than the same app without RSCs? I imagine it's possible, but do you have an example? Also, I don't think that's what people mean when they say RSCs don't send JS to the client. The JS in the component doesn't go to client.
200 0
Michael Frieze @frieze.dev · 05/12/2024
With RSCs, you are just executing some of the components on the server instead of all on the client. But, RSCs also get sent to the client twice. Once as HTML from SSR and again in the .rsc payload. React needs the .rsc data to know where hydration should occur.
200 0
Michael Frieze @frieze.dev · 05/12/2024
Yes, I often see this criticism that a "double fetch" happens when using RSCs in Next. But this is how things worked before RSCs. In pages router, the client gets HTML generated from the components markup using SSR and components are also hydrated / rendered on the client, so they are in the bundle.
100 0
Michael Frieze @frieze.dev · 05/12/2024
The .rsc payload contains no JS. It contains the element tree for RSCs, "holes" for client components, serialized props, and URLs to scripts for client components. That doesn't mean no JS is being sent to the client, but it's definitely less JS since RSCs don't execute on the client.
200 0
Michael Frieze @frieze.dev · 05/12/2024
As someone that grew up poor in rural Ohio, it's difficult for me to say "yes". I couldn't imagine paying that much money if I was just starting out. So, it depends. It's a great course. Maybe you can get an employer to pay for it.
010 0
Michael Frieze @frieze.dev · 05/12/2024
RSCs are rendered on the server, so JS isn't sent to the client for those components, reducing bundle size. The .rsc payload is serialized into a JSON-like format and included in the HTML payload. Sure, .rsc payload has a cost, but is this really an echo chamber issue?
110 0
Michael Frieze @frieze.dev · 04/12/2024
I don't think much is going to change in a year when it comes to RSCs. My guess is that Next will continue to be a popular framework and more Next projects will be using App Router. Also, other frameworks will adopt RSCs and make it available even for SPAs. They aren't going anywhere.
010 0
Michael Frieze @frieze.dev · 02/12/2024
I didn't realize the react native app I am typing this on is slow and terrible.
030 0
Michael Frieze @frieze.dev · 02/12/2024
I see criticism about React all the time and it has always been controversial. I honestly don't care to see more of it. There is always Primeagen for that. With that said, if there is a new criticism that doesn't seem to have an answer yet, I say share it.
010 0
Michael Frieze @frieze.dev · 02/12/2024
Josh's CSS course is one of the best courses I have ever taken.
110 0
Michael Frieze @frieze.dev · 02/12/2024
- followed you on twitter - I just saw you in replies
110 0
Michael Frieze @frieze.dev · 02/12/2024
I occasionally enjoy it, as I like talking about stuff and helping others. The next subreddit is generally a good community. There are many new developers asking questions and looking for assistance, but I don't mind that. The react subreddit is usually insufferable though. Both require patience 😅
100 0
Michael Frieze @frieze.dev · 02/12/2024
Using Next, we have Partial Prerendering which means we can get static parts of an app using SSR from a CDN.
000 0
Michael Frieze @frieze.dev · 02/12/2024
Also, I am not entirely sure what RSCs in a SPA looks like yet. In a SPA, we can get everything from a CDN and I think ReactDOM handles .rsc and can start committing it to the DOM right away. So I don't think you would have to wait on react to render client components to see content. Maybe?
200 0
Michael Frieze @frieze.dev · 02/12/2024
I don't know. I think it might be "faster" when a user gets HTML from SSR first. Streaming and suspense helps too. The initial RSC content is included in the HTML payload.
200 0
Michael Frieze @frieze.dev · 02/12/2024
On the initial page load, SSR generates HTML from the markup and sends it to the client. Post-hydration, the app is CSR. Changing routes will make requests to the server, but it doesn't always generate HTML from markup.
020 0
Michael Frieze @frieze.dev · 02/12/2024
SSR in Next/Remix is generating HTML from the markup, so I think SSR fits. I also find it more intuitive to view SSR in react as a CSR pre-render since it puts more emphasis on the CSR.
120 0
Michael Frieze @frieze.dev · 02/12/2024
With RSCs, you are just executing some of the components on the server instead of all on the client. But, RSCs also get sent to the client twice. Once as HTML from SSR and again in the .rsc payload. React needs the .rsc data to know where hydration should occur.
100 0
Michael Frieze @frieze.dev · 02/12/2024
I often see this criticism that a "double fetch" happens when using RSCs in Next. But this is how things worked before RSCs. In pages router, the client gets HTML generated from the components markup using SSR and components are also hydrated / rendered on the client, so they are in the bundle.
100 0
Michael Frieze @frieze.dev · 02/12/2024
I see it all the time on Reddit.
120 0
Michael Frieze @frieze.dev · 02/12/2024
by "another machine", I mean by something other than the client where client components get rendered. RSCs can be rendered at request time on a server or at build-time on a developers machine. I should have said "server" just to keep it simple.
030 0
Michael Frieze @frieze.dev · 02/12/2024
RSCs and SSR are two separate things and RSCs don't require SSR. RSCs can be used with SPAs as well.
010 0
Michael Frieze @frieze.dev · 02/12/2024
The .rsc payload is used to reconcile the server and client component trees. React then uses the "holes" and URLs in the .rsc payload to render the client components.
120 0
Michael Frieze @frieze.dev · 02/12/2024
The .rsc payload gets sent to the client and contains the serialized result of the rendered RSC, "holes" for client components, URLs to scripts for client components, and props.
120 0
Michael Frieze @frieze.dev · 02/12/2024
SSR is generating HTML from the markup in components for the initial page load. RSCs are react components that actually get executed on another machine. They don't generate HTML like SSR. Instead, we get an object representation of the element tree.
230 0
Michael Frieze @frieze.dev · 02/12/2024
We are talking about SSR in React.
120 0
Michael Frieze @frieze.dev · 02/12/2024
I mention snow in Michigan one time and blueskyroast made it a part of my identity.
010 0
Michael Frieze @frieze.dev · 01/12/2024
Sometimes feeds struggle.
010 0
Michael Frieze @frieze.dev · 01/12/2024
When it comes to SSR, I think of SSG as a kind of SSR that happens at build-time. So, statically exporting a Next app is kind of like SSR, but you don't need a server if you are only pre-rendering on a developers machine. Apparently, you can even use Next to build a SPA but I haven't tried that.
010 0
Michael Frieze @frieze.dev · 01/12/2024
Using RSCs isn't really an upgrade to use later. If you are statically exporting a Next app you can just use them and still host your app on a CDN or whatever you want. But, in this case you are only executing RSCs at build-time. If you want to run RSCs dynamically then you will need a server.
110 0
Michael Frieze @frieze.dev · 01/12/2024
But I get it that all the new tech is dominating the internet right now.
020 0