How Svelte and RSCs are Changing Web Development with Rich Harris, Creator of Svelte 

I enjoyed the discussion. One suggestion though, it'd be good to work on the introduction more. It looked really awkward for the guest to be asked to introduce himself and then him later having to ask for a question to get started with on rsc.

Cheddar cheese is/was British and named after an English village 😅 (which is equally famous for its caves where the cheese was matured)

Blazor also has "server components" and it's very clever, but the absolute enforced typing for frontend is a bit annoying a lot of the times And also the difficulty of adding/configuring Tailwind and Scss makes it very whack Interop with client-side javascript is also very convoluted; Though some things about the DOM can be solved directly in C#, using native JS libraries is kinda painful But I really enjoy the Blazor ability to have "fully server-side controlled rendering" in a way that I can dispatch updates using global-static objects, a reference to the component and a call to "state changed", it's very neat

Miller Dorothy Martinez Donna Thomas Sandra

Is there any movement in microfrontends? Or is this abandoned. Sure, we do not want 10 frameworks running on a page, but at least when you have big app, you can always try new stuff as web world evolves. I heard qwik is supposed to make them easier, but for me the gluing part was always the biggest challenge

Sveltekit feels amazing, especially after working with React for years

Am I insane for listening to this for the third time?

I don't understand the reason why frameworks do not take advantage of Service Workers but instead focus on RSCs

rich🎉🎉🎉🎉🎉❤❤❤ genius man