With React 16.8, React Hooks are available in a stable release
1–10 of 181 posts
Re: With React 16.8, React Hooks are available in a stable release
#2The crowd goes mild.
Re: With React 16.8, React Hooks are available in a stable release
#3I don't get it. I thought the main appeal of functions were that they were stateless so you had immutability. We already have classes if we want state, so why is this an improvement? Functions have slightly less overhead maybe? But then why didn't the React team just work on making classes have less overhead? It seems sort of "extra".
Re: With React 16.8, React Hooks are available in a stable release
#4Never a boring day being a frontend developer. Looking forward to add hooks to my React project. The next frontier would probably be functional strongly typed languages, like Reason or some variation on Elm?
Re: With React 16.8, React Hooks are available in a stable release
#5Never a boring day being a frontend developer. Looking forward to add hooks to my React project. The next frontier would probably be functional strongly typed languages, like Reason or some variation on Elm?
A variation on Elm? Why not just Elm?
Re: With React 16.8, React Hooks are available in a stable release
#6I don't get it. I thought the main appeal of functions were that they were stateless so you had immutability. We already have classes if we want state, so why is this an improvement? Functions have slightly less overhead maybe? But then why didn't the React team just work on making classes have less overhead? It seems sort of "extra".
I can't speak for everyone, but the reusability with custom hooks looks really nice and better readability than using say HOCs.
Re: With React 16.8, React Hooks are available in a stable release
#7I don't get it. I thought the main appeal of functions were that they were stateless so you had immutability. We already have classes if we want state, so why is this an improvement? Functions have slightly less overhead maybe? But then why didn't the React team just work on making classes have less overhead? It seems sort of "extra".
I'd encourage you to read through the Hooks docs [0], which explain the motivations, and Dan Abramov's posts on some of the internals [1] and what problems they're meant to solve [2].
[0] https://reactjs.org/docs/hooks-intro.html
[1] https://overreacted.io/why-do-hooks-rely-on-call-order/
[2] https://dev.to/dan_abramov/making-sense-of-react-hooks-2eib
Re: With React 16.8, React Hooks are available in a stable release
#8I don't get it. I thought the main appeal of functions were that they were stateless so you had immutability. We already have classes if we want state, so why is this an improvement? Functions have slightly less overhead maybe? But then why didn't the React team just work on making classes have less overhead? It seems sort of "extra".
I've been working with hooks for quite a while now; its main benefit is composability - before hooks up you rely on Higher order components (HOCs, HOFs but in component rendering) to provide composability of component behaviour - this is messy, very messy, and not performant.
By using hooks the logic tidies up massively (so working on it becomes a lot quicker) and several hard to diagnose performance bottlenecks disappear.
The 'not classes' stuff is a side benefit.
Re: With React 16.8, React Hooks are available in a stable release
#9The crowd goes mild.
The crowd is too fatigued to get excited anymore, there is a handful of outspoken people who will cheer any change for the sake of change or saving up a couple of key strokes at the cost of long term API size and maintenance burden. but it is getting tiresome.
Re: With React 16.8, React Hooks are available in a stable release
#10I don't get it. I thought the main appeal of functions were that they were stateless so you had immutability. We already have classes if we want state, so why is this an improvement? Functions have slightly less overhead maybe? But then why didn't the React team just work on making classes have less overhead? It seems sort of "extra".
I've been working with hooks for quite a while now; its main benefit is composability - before hooks up you rely on Higher order components (HOCs, HOFs but in component rendering) to provide composability of component behaviour - this is messy, very messy, and not performant. By using hooks the logic tidies up massively (so working on it becomes a lot quicker) and several hard to diagnose performance bottlenecks disa…
Can you please give some example of behaviour that you share across components that couldn't be factored out into a function?