<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>enlyth</author><text>I personally fell in love with hooks after initially disliking them, you should give it a try, maybe in a toy personal project, to see if you like it. It is great for separation of concerns.&lt;p&gt;You basically stick to writing pure functional components focused only on how to render, and try to abstract reusable logic into hooks, and expose only what you need&lt;p&gt;For example, you could make a useApi() hook and inside your component just do const { data, loading, error } = useApi(&amp;#x27;&amp;#x2F;endpoint&amp;#x27;), so you can hide everything you don&amp;#x27;t need away from the rendering logic</text><parent_chain><item><author>tekstar</author><text>I use React (well, Preact) every day.&lt;p&gt;I use it 2014-style.  Class-based components, componentWillMount, render, callbacks, and that&amp;#x27;s about it.&lt;p&gt;I love this workflow, and generally structure all my UIs this way regardless of platform - have a state struct and then fully render the UI as a function of the state.  To me, that&amp;#x27;s the big hurrah for using React.&lt;p&gt;But I have no clue why React is at version 18 and why it keeps getting new features.  I&amp;#x27;m perfectly happy making quite complicated UIs with the pattern I know well.  Should I be following along?  Does it matter?</text></item></parent_chain></comment><story><title>The Plan for React 18</title><url>https://reactjs.org/blog/2021/06/08/the-plan-for-react-18.html</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dstaley</author><text>As someone who was initially resistant to hooks, I actually find that they&amp;#x27;re a more expressive API to how I was already thinking about my applications. There&amp;#x27;s footguns for sure, just like there are with class components, but I found that rewriting my class components with hooks instead actually made the code cleaner and easier to reason about. That being said, it&amp;#x27;s possible the benefit simply came from the rewrite, but even with newer components, I feel like hooks are a better API.</text><parent_chain><item><author>tekstar</author><text>I use React (well, Preact) every day.&lt;p&gt;I use it 2014-style.  Class-based components, componentWillMount, render, callbacks, and that&amp;#x27;s about it.&lt;p&gt;I love this workflow, and generally structure all my UIs this way regardless of platform - have a state struct and then fully render the UI as a function of the state.  To me, that&amp;#x27;s the big hurrah for using React.&lt;p&gt;But I have no clue why React is at version 18 and why it keeps getting new features.  I&amp;#x27;m perfectly happy making quite complicated UIs with the pattern I know well.  Should I be following along?  Does it matter?</text></item></parent_chain></comment><story><title>The Plan for React 18</title><url>https://reactjs.org/blog/2021/06/08/the-plan-for-react-18.html</url></story>