I think we can all learn from this. Next/React, server actions, sql, "use server", I get why we're confused. Hopefully this clears up a lot of that confusion.

SOURCES
https://x.com/t3dotgg/status/1799356056239472899
https://x.com/tomdoes_tech/status/1799559501915566472
https://x.com/AdamRackis/status/1717607565260124613
https://nextjs.org/blog/security-nextjs-server-components-actions

Check out my Twitch, Twitter, Discord more at https://t3.gg

S/O Ph4se0n3 for the awesome edit 🙏

T3Dotgg's resource offers insights, tutorials, and resources for gamers and esports enthusiasts. Readers can learn about gaming news, esports events, and professional gaming strategies. With articles, reviews, and interviews, T3Dotgg provides  guidance and expertise for staying informed and competitive in the world of gaming.

Theo - t3․gg

The post discusses the use of SQL code in React components and defends the flexibility and composable nature of the new model. It explains the purpose of the 'useServer' function and how concerns between the backend and frontend can be separated.

In Defense Of "SQL In React"

<p>Every technology has its use case. I believe useServer is quite beneficial for small projects or projects with a backend-for-frontend layer where frontend developers also work as full-stack developers, handling both backend and frontend tasks. However, in larger, more complex projects, frontend developers may become overwhelmed by managing both backend and frontend responsibilities. It is safer and more effective to separate these concerns, making it more affordable and easier to hire two specialized individuals rather than a full-stack developer.</p>
<p>But looking at the bigger picture, why should a frontend framework concern itself with these issues, it’s all about the direction and feature of React.</p>
