<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>wokwokwok</author><text>You realize you&amp;#x27;ve just done exactly what the parent complained about right?&lt;p&gt;- said it was bad&lt;p&gt;- not provided any concrete details&lt;p&gt;&amp;gt; they&amp;#x27;ve become unmaintainable when reaching a certain size&lt;p&gt;How?&lt;p&gt;Did you start getting lot of hard to replicate bugs?&lt;p&gt;Did you find authoring new components was made difficult by your heavy use of custom hooks that were actually not as generic as you thought when you wrote them?&lt;p&gt;Did you find 3rd-party hooks had bugs?&lt;p&gt;Did you find that useRef doesn&amp;#x27;t work like you think it does, and you can&amp;#x27;t mix and match useRef and useEffect? (ouch)&lt;p&gt;What kind components are you writing that you find hooks are such a bad fit for?&lt;p&gt;Be specific.&lt;p&gt;(I&amp;#x27;m not saying hooks are perfect; I&amp;#x27;ve had all of the issues I listed happen to me, but it&amp;#x27;s still quicker to implement new features on a medium sized web app using hooks than with components in my experience; I work on 3 apps, and only one of them still uses components, and it&amp;#x27;s the most annoying to make changes too, simply because for &lt;i&gt;simple business components &amp;amp; forms&lt;/i&gt;, hooks seem to reduce the amount of boiler plate, and flat out, reduce the lines of code; less code -&amp;gt; faster changes. It&amp;#x27;s not always that simple (see bugs comment above), but mostly... it is, in my experience: ...HOWEVER, what you&amp;#x27;ve done is just wave your hands vaguely and fail to actually say anything except you don&amp;#x27;t like hooks)</text><parent_chain><item><author>Exinferis</author><text>Although the article is too generic, or not detailed enough regarding examples of what he states, I have to agree with what he is trying to say. 
React hooks are a mess, or at least code based around it tends to be. We have had our share of hooks based applications and they&amp;#x27;ve become unmaintainable when reaching a certain size and I am glad that we are back to class based components wherever we can. In may opinion this comes down to the fact - as he states - that the mental model (what will happen, when I do this) is not simple to grasp, thus not predictable for many people.</text></item><item><author>ritchiea</author><text>This is the kind of post that suffers from lack of specific examples. I would love to see an interesting discussion of how hooks are not in line with most developers mental model of React and what problems it&amp;#x27;s causing (if that is indeed true, or at least true in the eyes of the author). But this post is far too generic to illuminate what the real problems are or convince me that there are any.</text></item></parent_chain></comment><story><title>React is becoming a black box</title><url>https://jaredpalmer.com/blog/react-is-becoming-a-black-box</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>alfonsodev</author><text>&amp;gt; React hooks are a mess, or at least code based around it tends to be.&lt;p&gt;I&amp;#x27;ve read a lot warnings about the pitfalls, and about hooks not doing what you think they are doing, but honestly, I haven&amp;#x27;t experience any of that, maybe because my use cases are so close to the documented ones, that I don&amp;#x27;t need to stretch the concept, and it just works as intended for me.&lt;p&gt;Could it be, that as with many other programming patterns, some developers are using it as a silver bullet, and trying to solve everything with hooks?&lt;p&gt;Otherwise I&amp;#x27;m failing to understand, it would be useful to see examples as the mentioned above.</text><parent_chain><item><author>Exinferis</author><text>Although the article is too generic, or not detailed enough regarding examples of what he states, I have to agree with what he is trying to say. 
React hooks are a mess, or at least code based around it tends to be. We have had our share of hooks based applications and they&amp;#x27;ve become unmaintainable when reaching a certain size and I am glad that we are back to class based components wherever we can. In may opinion this comes down to the fact - as he states - that the mental model (what will happen, when I do this) is not simple to grasp, thus not predictable for many people.</text></item><item><author>ritchiea</author><text>This is the kind of post that suffers from lack of specific examples. I would love to see an interesting discussion of how hooks are not in line with most developers mental model of React and what problems it&amp;#x27;s causing (if that is indeed true, or at least true in the eyes of the author). But this post is far too generic to illuminate what the real problems are or convince me that there are any.</text></item></parent_chain></comment><story><title>React is becoming a black box</title><url>https://jaredpalmer.com/blog/react-is-becoming-a-black-box</url></story>