What Comes After GraphQL?

Рет қаралды 5,610

Күн бұрын

Пікірлер: 19

@zombiefacesupreme 7 ай бұрын

[0:00] Starting Soon... [2:00] Preamble [10:00] Why Are We Talking About GraphQL? [20:00] GraphQL's Allure & Ryan's History [36:00] The Normalized, Client-Side Cache [44:00] The Gap Between Promise & Reality [53:00] Why Not Just Use a Query Cache? [59:00] tRPC's Benefits & Limitations [1:08:45] Why Not Just Use a Page Cache? [1:16:00] RSC's & The Single Server Tree [1:23:45] Stateful Backends & Interactivity [1:32:45] What Value Do Server Components Bring? [1:46:15] A New Authoring Experience [1:51:15] Updating The SolidStart Notes Demo [2:00:15] Single Flight Mutations [2:10:30] How Is This Different? (Excalidraw!) [2:19:15] Reduced Bundle Sizes [2:26:45] Finding The Sweet Spot [2:32:30] Optimistic Updates [2:49:45] Conclusion: Improving UX & DX Together [3:07:30] This Week in JavaScript: Solid News [3:13:00] TWiJ: Link & Form vs. Composability [3:24:00] TWiJ: Web Components & React [3:30:15] TWiJ: Leptos Islands Demo [3:39:15] TWiJ: OpenSauced & bobaekang [3:48:45] TWiJ: Ryan Florence & Sunil Pai [3:51:45] TWiJ: Signals & Server Components [4:01:45] Conclusion: The Other Side of the Slope Happy Birthday, Ryan!

@magne6049 6 ай бұрын

It'd be nice if there was a point in the stream that explicitly tries to answer the question in the title: "What Comes After GraphQL?"

@xZodax 7 ай бұрын

Happy birthday Ryan! Thanks for being here for hours every week! 😆

@StingSting844 6 ай бұрын

This was a good stream 👏

@ArkDEngal 6 ай бұрын

Happy birthday. I like watching your streams, I feel like I learn a lot every time.

@danielnascimento7812 6 ай бұрын

Happy (belated) birthday

@spicybaguette7706 6 ай бұрын

Question: Since the client only knows it's being redirected when it gets a message from the server, it can only then start fetching Javascript for rendering, right? So even though the data is immediately streamed to the client, it must still wait a round trip if it hasn't cached the js required for the route yet. Of course, if it has the js in the cache, it can render immediately

@spicybaguette7706 6 ай бұрын

I guess then the main advantage is that with Solid Start's approach, you only fetch the markup once, and after that, just the data. While Next sends the entire markup every time, but has the advantage that it doesn't need another round trip on the first mutation

@ryansolid 6 ай бұрын

@@spicybaguette7706 Does Next know the client components for the next page until it has responded? I think it ends up being the similar if there are any interactive components.

@naveeng723 7 ай бұрын

Happy birthday Ryan

@rickyraihana5683 7 ай бұрын

Happy Birthday! Sirrr

@HerringtonDarkholme 7 ай бұрын

Happy Birthday!

@MaximSchoemaker 7 ай бұрын

Happy birthday! 🎉✨💖

@puchesjr07 7 ай бұрын

Happpy Belated Birthday!

@sushantjadhav1475 7 ай бұрын

I think 4 hour session is to big, try to wrap it in one hour

@ryansolid 6 ай бұрын

Honestly it would be much more time consuming for me. I give a lot of 20-50 min conference talks. To prepare a new one of those on average takes somewhere around 20-30 hours between research, slides, practicing (because usually usually I'm way over time until I get it slick). If I did that every week it would basically be my day job. 4-5 hours to give with no prep is way easier and valuable for me. And I use this as an opportunity to learn from guests and the audience. To test framings and to explore different angles. Some of my talks are based of topics I've done in stream before. This stream/channel is mostly so that I can learn and we can explore questions in a way that I'd attack them. This is probably not going to ever be terribly consumable without an editor, but that's not why it is here.