<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>BilalBudhani</author><text>Hooks seem to be a drastic change in how we&amp;#x27;re going to write React components in the future. I&amp;#x27;m quite satisfied with the current way of writing components which is to me is very explicit (with no magic). With Hooks React is taking a different direction from their original motto of explicit design patterns. From the looks of it, Hooks seems like a counter-intuitive design pattern but traditionally that&amp;#x27;s how most of the JS concepts were before they went mainstream.&lt;p&gt;I&amp;#x27;m going to wait and see for some production success stories become giving it serious thought.</text><parent_chain></parent_chain></comment><story><title>With React 16.8, React Hooks are available in a stable release</title><url>https://reactjs.org/blog/2019/02/06/react-v16.8.0.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>devit</author><text>Are hooks being accepted as a good design by the community?&lt;p&gt;It seems to me that the lack of a parameter explicitly indicating the component and the reliance on hook ordering to match them across calls of the component function make them a bad design, but I might very well wrong and would be happy to be convinced otherwise.</text><parent_chain></parent_chain></comment><story><title>With React 16.8, React Hooks are available in a stable release</title><url>https://reactjs.org/blog/2019/02/06/react-v16.8.0.html</url></story>