@@nonefvnfvnjnjnjevjenjvonej3384there is no modern future without a build step, learn to live with it, even c/cpp & java have one and nobody complains. The thing is no one forces you to use build steps, it is not a law or something you can stay in your build free stack.
@@nonefvnfvnjnjnjevjenjvonej3384 i don't have great react knowledge to fully grasp what happened here but don't the other frameworks also do this in a similar way. I think laravel with livewire does this too what he showed but i might be wrong.
@@hamm8934 its not really the same you have to make the trade off: do you want to handle the majority of the events on the client, or the server? There are benefits to both, & often both will work fine, but they are not the same & certain cases it just won't work. Eg. If you are doing frame-by-frame updates on mouse movement, I don't want to handle all those events on the server.
I'm just amazed at how server components, client components and server actions are blowing people's minds but, for me, it's just how I learned to code. 😅
yeah this is neat functionality, but why start the talk talking about trade-offs if you aren't gonna talk about trade-offs? You can't just say "your way of doing web dev is bad" and present React as a silver bullet without mentioning the trade-offs that you promised at the start.
Amazing talk Ryan!
Hands down, my favorite Ryan Florence talk
Elixir mentioned
From what i understand of pheonix, pheonix effectively dissolves the network as well with its use of web sockets
so does livewire.. i dont know.. what makes what he shows so brilliant... you still have the build step and the complexities.
@@nonefvnfvnjnjnjevjenjvonej3384 kinda my thoughts as well. Just seems like a different syntax with a different language to do the same pattern
@@nonefvnfvnjnjnjevjenjvonej3384there is no modern future without a build step, learn to live with it, even c/cpp & java have one and nobody complains. The thing is no one forces you to use build steps, it is not a law or something you can stay in your build free stack.
@@nonefvnfvnjnjnjevjenjvonej3384 i don't have great react knowledge to fully grasp what happened here but don't the other frameworks also do this in a similar way. I think laravel with livewire does this too what he showed but i might be wrong.
@@hamm8934 its not really the same
you have to make the trade off:
do you want to handle the majority of the events on the client, or the server?
There are benefits to both, & often both will work fine, but they are not the same & certain cases it just won't work.
Eg. If you are doing frame-by-frame updates on mouse movement, I don't want to handle all those events on the server.
I'm so deep in the react world and yet I haven't seen someone explain this stuff so well, amazing talk from Ryan as always
Jank mentioned
it's been 4 months i wonder if he got rid of those nvda stocks
it’s like the good parts about meteor resurfacing 10 years later!
Uh, meteor was 90% bad parts, and the 10% good parts were maybe only 5% of the good parts of react dissolving the network.
@@AndyThomasStaff 90% bad parts pssshhhhh no way. :)
Ryan made this talk just to write the remodeling bill as a business expense.
Underrated comment
I'm just amazed at how server components, client components and server actions are blowing people's minds but, for me, it's just how I learned to code. 😅
I was a mootools advocate back when he was involved in it. Respect to that shirt.
electric clojure would be something to look at also.
On tradeoffs - what immediately jumps out is this looks painful to debug and teach. Very cool demo nonetheless
Yeah good luck reimplementing a new backend framework on top of a frontend library and demoing with a local file as the db…
No offense but sadly you missed the whole point of Remix.
mootools mentioned lets gooo
Ryan is so freaking brilliant at educating (as always). I clapped in front of my laptop once the talk ended.
i love ryan
love you too
Wow, brothers and sisters, this is a fantastic talk!
brilliant talk thanks.
This talk was amazing
Htmx will become a RSC framework
yet people keep complaining about over-engineering
The moral of this is “React is good”😂
yeah this is neat functionality, but why start the talk talking about trade-offs if you aren't gonna talk about trade-offs? You can't just say "your way of doing web dev is bad" and present React as a silver bullet without mentioning the trade-offs that you promised at the start.
there are none
cooked htmx
I hope with this,
the Primegeon will finally stop making fun of react😅