---
title: "Comment by Tarun Sharma on \"Server vs Client Components in Next.js 16 (2026 Guide)\" | Hashnode"
description: "The \"children as a slot\" pattern for Rule 3 is the one thing I wish got taught earlier, most people find it by accident after fighting the \"Server Component bec"
url: "https://hashnode.com/posts/server-vs-client-components-in-next-js-16-2026-guide/6a794ea8be9071f95a2ac5ce/comment/6a84093bb659ca6422dbaa01"
---

[Discussion](https://hashnode.com/posts/server-vs-client-components-in-next-js-16-2026-guide/6a794ea8be9071f95a2ac5ce)

Comment [Server vs Client Components in Next.js 16 (2026 Guide)](https://hashnode.com/posts/server-vs-client-components-in-next-js-16-2026-guide/6a794ea8be9071f95a2ac5ce)

[Tarun Sharma](https://hashnode.com/@101beardo)

[Aug 18](https://hashnode.com/posts/server-vs-client-components-in-next-js-16-2026-guide/6a794ea8be9071f95a2ac5ce/comment/6a84093bb659ca6422dbaa01)

The "children as a slot" pattern for Rule 3 is the one thing I wish got taught earlier, most people find it by accident after fighting the "Server Component became a Client Component" error for a while. One case I'd add to the practical example section: useOptimistic paired with a Server Action for the AddToCartButton. Right now the button just sits in "Adding..." until the fetch resolves, but useOptimistic lets you flip the UI state instantly while the Server Action runs in the background, then reconciles if it fails. Feels like the natural next step once someone has the basic Server Action wiring down from this guide.

[Syed Muhammad Ali](https://hashnode.com/@s-m-ali)

[Aug 18](https://hashnode.com/posts/server-vs-client-components-in-next-js-16-2026-guide/6a794ea8be9071f95a2ac5ce/comment/6a84093bb659ca6422dbaa01#reply-6a8427712d1807c9898b1ec3)

That’s a really good addition. useOptimistic fits naturally as the next step after getting the basic Server Action flow working, especially for cart-style interactions where the UI should feel instant. I’ll definitely consider adding it to the practical example. Thanks for the thoughtful suggestion!

[Tarun Sharma](https://hashnode.com/@101beardo)

[Aug 18](https://hashnode.com/posts/server-vs-client-components-in-next-js-16-2026-guide/6a794ea8be9071f95a2ac5ce/comment/6a84093bb659ca6422dbaa01#reply-6a843452bd6db98e577fc121)

Nice, would be curious to see how you'd handle the rollback UI if the Server Action actually fails, that's usually the trickier half of the pattern.
