undefined | Better HN

0 pointsbrucou3y ago0 comments

I beg to differ here. Or let's say that the React "functional programming" model has very little to do with the actual functional programming done by actual functional programmers. What is true is that React components are functions. But functional programming and programming with functions are two different things.

Second, side effects are just about in every React component where you use a hook.

Third, (hypothesis) `useEffect` is probably a misnomer that stick there because it would be a breaking change to rename it to something more proper.

Words and bickering aside, you can write great applications with React, that's fact. It is also a fact that a lot of folks are using it wrong, which shows either a problem with React learnability itself, or with its documentation, or well, with the programmers themselves.

0 comments

1 comments · 1 top-level

schwartzworld3y ago

> side effects are just about in every React component where you use a hook.

I would expect most of your side effects to happen as a result of user interaction, i.e. in an event handler. Data fetching would probably be at the top of the tree. What side effects are you including in every component?

> a problem with React learnability itself, or with its documentation, or well, with the programmers themselves

All three!

- Most programmers dont learn FP before adopting React, which means they aren't going have a more difficult time working with React's functionalish model.

- Lots of blog posts, tutorials and even docs of popular libraries feature poorly written React code. It's just reality. Lots of people use this library, and there's no barrier to entry to write a tutorial post. IMO, the new React docs are a step in the right direction and should be a primary learning material for most.

j / k navigate · click thread line to collapse