What was your hardest part of learning React?

[@wobsoriano]

When you get introduced to Redux as a React beginner

[@hswolff]

Yeah! The hardest combo!

[@exactzero]

Yeah. Beginner tutorials should stop teaching Redux right away or at least emphasize that you don't have to master this early on.

[@podoprigoraisv]

React Docs definitely need to be better, there are a lot of nuances that have to be explained. At this moment are looking at Github is the only way to find a solution. For instance, we have ErrorBoundary but there is not explanation how to throw error inside async callback or how to fork two refs or how to make component "controllable", the different memoization approaches etc.

[@hswolff]

Yes! Agreed!

[@VinitKhandelwal]

If you find react documentation bad, try AWS documentation sometime to feel better.

[@podoprigoraisv]

@@VinitKhandelwal ))

[@JordanAF808]

You hit it right on the nose when you first learn react and you want learn the best way to do things. I'm scared of jumping into the graphql section :|

[@mudyeet_]

Oh also, webPack, I mean create-react-app saves a lot of pain in the ass but can't rely on that forever. Also, webpack is awesome, wanna learn it, but idk where from.

[@carlosjosejimenezbermudez9255]

Ditch webpack and use Vite instead, much easier to use.

[@sumanthapa6063]

class component and redux make my code look ugly

[@jornejongsma]

Right at the start of this video: press the left cursor, and do it again, and again... Faster!

[@jornejongsma]

React Router, specially when you omit ssr... I always get comments back: "Something's wrong, I can't get back to the page, the app is broken!"

[@hswolff]

Ugh yeah. Those are the worst

[@lodgin]

Have to agree with swyx, that the biggest problems I've had with React isn't even with _React_ itself but with tooling. Since I found out about React and some excellent theme packages, I've been coding my Github Pages site in React in lieu of using Jekyll, but the thing is, I'd like React to _behave_ like Jekyll's Liquid language. I don't want to package React with the site, I want React to render the site to HTML. I still haven't really found a perfect solution, but piggy backing off of Gatsby is close enough. It still creates a bunch of Javascript files though… but at least you can turn Javascript off and the website will still look and function the same. I guess if there was a real problem from the beginning, it would be state changes, and with my use case above, cross contamination code: it can be difficult to tell what code will be executed by the server and what will be executed by the client.

[@hswolff]

Yeah server side react is sooo confusing

[@swyxTV]

webpack

[@hswolff]

Yeah webpack is a beast So are your speed to comment haha. So good!!

[@Sese63728]

Context api is by far the most confusing thing in react. I always hated HOC as well (maybe not part of react though).

[@mudyeet_]

Tbh all the Providers, and ofc Redux.

[@KeepItFresh02]

Redux for me. It took me almost 2 years to learn it.

[@fakecake6776]

lol

[@aksyonov100]

I cry every day since we switched to React Redux and Redux-Saga

[@VinitKhandelwal]

The entire management of data is tedious

[@VinitKhandelwal]

If I were given an option I would use local storage directly from components

[@MrEnsiferum77]

CSS, cuz I don't get the buzz using framework, when your daily horror life is just overriding css props.

[@Ecdetails]

Context api

[@fakecake6776]

Lifecycle

[@TheInfern0s]

React

[@hswolff]

Lol

[@aRndBelgianGuy]

JS :D

[@aRndBelgianGuy]

That abomination of a language !

[@zsytssk5176]

redux