Пікірлер

• 
  @randyt7009 сағат бұрын

  Lol, Ryan just effectively replaced "react"/vdom here at 16:38. It might be the mic'ing but was expecting at least a gasp from the audience. Ryan's abstractions may be much lighter/simpler than react's.

• 
  @tomhumphris97013 күн бұрын

  Great talk Josh! Thanks for this!!

• 
  @CistiC098716 күн бұрын

  Tejas is such an amazing educator, we need more of his content here on KZread!

• 
  @SnakeCaseGuy23 күн бұрын

  basically go back to react 15

• 
  @mirjalol_nightmares24 күн бұрын

  Josh is best of the best

• 
  @zidanbadr165827 күн бұрын

  keep up the great work

• 
  @choubariАй бұрын

  Thanks for having me at this amazing conference!

• 
  @BeJScommunityАй бұрын

  Thank you for your amazing talk and also for the awesome vlog you made :)

• 
  @smakoshАй бұрын

  Great talk Kawtar!

• 
  @choubariАй бұрын

  Thank you @smakosh !

• 
  @humbler144Ай бұрын

  React: I use memo Others: We have signals React: Ok let's wait till our new compiler React forget

• 
  @aquaductapeАй бұрын

  For developer experience, React Forget is a huge win, but no improvement on performance standpoint. React will still be slower then other popular frameworks, except Angular lol

• 
  @Gorgggg23 күн бұрын

  @@aquaductape angular is catching up. Already got signals now

• 
  @kevinat71Ай бұрын

  Josh is amazing!

• 
  @arya_bakhАй бұрын

  literally 1/5 of the lecture is the dude telling stories of himself

• 
  @EverydayKarma2 ай бұрын

  Gem

• 
  @viveksah20692 ай бұрын

  You need to see what those libraries are doing behind the scene. Closing the eyes in the daylight does not mean it is night for all. they are using the useEffects more than normaly a developer do

• 
  @semerset2 ай бұрын

  I don't quiet understand the difference between "bad" and "good" examples of type declaration. Where should I look? I'll appreciate any explanation here

• 
  @epicmetod2 ай бұрын

  useJquery

• 
  @FilthyAnimal8932 ай бұрын

  I feel like a big problem here is that React doesn't seem to have a clear-cut way to handle promises when rendering a component, and useEffect has become a sort of work around exploit to fulfill that very common need.

• 
  @nghiaminh77043 ай бұрын

  In 15:42, is the `setIsOpen(nextIsOpen)` safe? I always think that when you derive next state from current state, the updater function MUST be used.

• 
  @Pareshbpatel3 ай бұрын

  Excellent talk. Thank you, Nikhil. {2024-02-13}

• 
  @kingwou4 ай бұрын

  dude trying har to find solutions for an imaginary problem, useEffect is just fine, adding 10 layer above it just for the sake of not using it is NOT fine.

• 
  @GergiH4 ай бұрын

  15:40 what the actual F... I knew I'm not going to be happy with hooks when it was first introduced, gladly I could hop off the React train then. Revisiting it with this part feels like a nightmare. It's REALLY hard to follow what the hell actually (needs to) happens there even with that simplest example, can't imagine what kind of mess it would look like in a big application. I can't put it into words how much I just hate it now.

• 
  @RobertWHurst4 ай бұрын

  Talk should be "you're probably to stupid to write React effects, so use my code instead"

• 
  @kmylodarkstar22534 ай бұрын

  useEffect is the most human of all react. Don't struggle, just enjoy

• 
  @RmNrIHRoZSBDQ1AK4 ай бұрын

  Lmao all soydevs in the comments. Get good or something.

• 
  @eliancodes4 ай бұрын

  Had so much fun on this episode!

• 
  @skorotkiewicz4 ай бұрын

  useEffect runs twice only in a dev mode with strict mode, on productions runs once and this is on purpose.

• 
  @abhisycvirat4 ай бұрын

  React is creating new problems, to solve old problems. Thats how I see this.

• 
  @RaniLink5 ай бұрын

  React can suck a dick, really, re-inventing its own fucking wheel every couple of months. It's only popular because it's easy for beginners to make some bullshit "instagram clone" as their firs project. So you get a bunch of self diagnosed "full-stack developers" hype it up to be the "best thing ever".

• 
  @haletteboxell40735 ай бұрын

  ✋ *promosm*

• 
  @maxwellcoding5 ай бұрын

  I don't understand why all this noise and complaints in the comments about React. React is a library. It gives you the toolset and you are in charge of it.

• 
  @carljung47335 ай бұрын

  Yeah seriously...tons of clueless people.. UseEffect may be a foot gun.. but an idiot still has to pull the trigger. Take the time to learn to leverage the tool properly.

• 
  @maxwellcoding5 ай бұрын

  13:49 Would be great if React forced us to add the deps array by throwing an error or a warning. I just don't see any reasonable case when useEffect without the deps array could be used.

• 
  @maxwellcoding5 ай бұрын

  12:45 If data comes from an outside source, then you have to use useEffect.

• 
  @Gaijin1015 ай бұрын

  Years later and the confusion is still not solved. React in a nutshell. For others, use preact signals or vue.

• 
  @gkiokan5 ай бұрын

  Puh guys, this was never an issue with Vue. There are reasons why I don't touch React. I believe it has it's usages but it's so complex and I truly ask what the overcomplicated pattern solves as even Vue 3 is close to Reacts schematics but in a much simpler way. I didn't see any performance issue if anyone may ask.

• 
  @user-kh2wr7ju1k5 ай бұрын

  Explaining ❤❤

• 
  @vasfvitor5 ай бұрын

  haha that was so fun! I used to be Astro and Svelte guy, but now learning more about Solid and how it matches Tauri (thanks to Atila) I'm trying Solid

• 
  @BeJScommunity5 ай бұрын

  Awesome :) glad to hear that 😊 Are you building something specific with solid/tauri or just playing around with it?

• 
  @vasfvitor5 ай бұрын

  @@BeJScommunity nothing specific, I'm learning Tauri while contributing to their docs and looking to do the same with Solid :)

• 
  @BeJScommunity5 ай бұрын

  That's great :)

• 
  @Katherine_Tea5 ай бұрын

  nat alison fan club reporting in live (we love her)

• 
  @basicguy57855 ай бұрын

  With signals this presentation is already obsolete as you can stop using hooks all together.

• 
  @guseynismayylov19455 ай бұрын

  "So, use - seems cool, terrible named, but you know, that's the future." React is everything that I hate about "modern" web dev.

• 
  @nuntiusmortis89765 ай бұрын

  Great short presentation, I think it would be good to have it in article form as an easy way to quickly share the points with other engineers

• 
  @eliancodes6 ай бұрын

  It was an awesome edition and experience once again! Glad to be part of the community!

• 
  @BeJScommunity6 ай бұрын

  Thank you my friend :) It means a lot :)

• 
  @Baptistefir6 ай бұрын

  I'm a react dev and after seeing this, all i want is to change framework. What a mess they have created.

• 
  @codewithguillaume6 ай бұрын

  Thanks guys !

• 
  @BeJScommunity6 ай бұрын

  Thank you :) We're happy you liked it.

• 
  @eliancodes6 ай бұрын

  Thanks guys! Was so much fun being on the podcast!

• 
  @eXquisiteBuddy6 ай бұрын

  It feels like the solution with useEffect is basically using it with rxjs. For example the takeUntil operator is op for clean ups, I wonder why rxjs didn't pick up with react community.

• 
  @longbatphu6 ай бұрын

  Fun fact: react-query uses useEffect under the hood.

• 
  @bestexplainer48316 ай бұрын

  What is alternative?

• 
  @nested93016 ай бұрын

  react is trash this is the summary of this videeo

• 
  @eliancodes6 ай бұрын

  This was such a fun panel to do! Thanks everyone!

• 
  @himanshutripathi74416 ай бұрын

  Haww, I only useEffect and useState from last 2 years. I have never used others. One of my components has 10 useEffects. I was kinda proud of them. Even patted myself in the back and praised react for being such a nice framework.

• 
  @techponds6 ай бұрын

  Wow nice explanation