How Next.js is delivering React’s vision for the future (Sam Selikoff)

preview_player
Показать описание


Рекомендации по теме
Комментарии
Автор

Sam delivering the best presentation as usual!

voinbobar
Автор

Loved this presentation; just what I needed amidst all these new and shiny updates to build a mental model.

dawid_dahl
Автор

Love the new paradigm.

But would really prefer defining server/client components at the filename level: e.g. Modal.client.tsx, NewsStory.server.tsx.

"use" string directives just feel out of sync on how we write JavaScript

zalodias
Автор

Love your talk.
We used to have allergic reactions from people seeing html inside js, and css inside js, not anymore.
I always tell people stop breaking code up by their types, but their functionality.
Nobody writes button without styles, and nobody writes button without its corresponding js or form actions.
If then, why are we breaking up the code into different files? That is a code smell and its called fragmentation.
If we have a button that adds todo list (handled on the server), this button is useless without server action, then why not put them together in the same component? The only reason why we didn't do it before was because there just wasn't a good way to do it.

bosung
Автор

Can you unit test React Server Components, or would they only be tested via E2E tests? It's easy to test client components based on useSWR, because I can mount the component and mock out its network API calls to create any scenario my test needs.

benme
Автор

I wonder about security implications of third party packages. What if a <button /> from npm has a formAction in it that steals my server creds/data. How would I even track it and stop such an attack?

DivjotSingh
Автор

Looks like "good" old PHP :) let's mix SQL and HTML together... The presentation looks good, and the new tutorial too... But my feelings are quite contradictory until I've tested that by myself. Especially I am curious about some complex applications and how this thing will be tested.

janstrnadek
Автор

I understand the sentiment but couldnt we make formAction "use server" by default? seems like too much to write again "use server" inside a server component

viniciusataidedealbuquerqu
Автор

They guy at the bottom right was watching memes 👀

alansaldivares
Автор

Loves the new Next.ja features. However the example on server actions is a bit off and I don't really see the benefit of it other than Next.js keeping you locked in using Next.js actions.
So I would take Sam's words with a grain of salt, especially as he was paid to deliver this talk and basically sell it. 😉

ikusoru
Автор

15:44 🤯 I have 🫘 using SERVER ACTIONS, but I have 💭 that there 😯 only for from submissions. That is, a ‘<form>’ with a ‘“submit”’ button.

codefinity
Автор

Yes, after I saw the server component, i though, react is a lego. I feel like a lego owner who press a lego in night. Thanks you killed SoC.

MahmutGundogdu
Автор

that's a lot of technology and innovation for a basic to-do spa 😂

catalinim
Автор

A glimpse into React's origins:
It wasn't designed for data handling or retrieval.
Instead, React aimed to refine UI creation with one-way data binding, ensuring a seamless rendering flow.
Overengineering is the bane of elegant programming.

pbritotube