<story><title>Vue.js is Wikimedia Foundation&apos;s future JavaScript framework</title><url>https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/SOZREBYR36PUNFZXMIUBVAIOQI4N7PDU/</url></story><parent_chain><item><author>ggregoire</author><text>Although I understand what you saying about big shifts and kinda shared your opinion, specially about hooks, I started a new project from scratch last week and decided to give hooks a try (and, for reference, I&amp;#x27;ve been using React on a daily basis for 5 years).&lt;p&gt;Oh boy I was wrong.&lt;p&gt;Hooks are way more easier and intuitive than what I thought. It makes code so much more readable and easier to reason about. Especially when before you had to wrap your components into x number of HOCs to inject the props your component needed, risking props collision, making it really hard to debug and use with TypeScript, and eventually making it a nightmare to understand and maintain your component. I&amp;#x27;m not surprised that every React library added a hook API to its core.&lt;p&gt;At the end of the day it makes me more productive, so I guess that big shift was also a big win.</text></item><item><author>ferdowsi</author><text>Congratulations to the Vue team, this is definitely a big win for them.&lt;p&gt;Reading through the RFC is really interesting. They specifically call out the dependency on Facebook as effectively being React&amp;#x27;s Single Point of Failure, citing their negative experiences with HHVM.&lt;p&gt;And for all of the love that people give React&amp;#x27;s big shifts (like hooks), the RFC specifically counts this against them, given that best practices have shifted so drastically in the last few years.</text></item></parent_chain><comment><author>ricardobeat</author><text> I&amp;#x27;ve been through two large-scale projects now where we went 100% into hooks, and after a couple years the excitement has faded and I often wonder if it was worth it. It seems to end up making code even more complex than before, even though components look simpler on the surface. Not enough to go back to classes, but doesn&amp;#x27;t feel as good as those first steps. I absolutely hate the manual dependency tracking and having &lt;i&gt;every single thing&lt;/i&gt; be wrapped in a useX() method to avoid unnecessary updates.</text></comment>
<story><title>Vue.js is Wikimedia Foundation&apos;s future JavaScript framework</title><url>https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/SOZREBYR36PUNFZXMIUBVAIOQI4N7PDU/</url></story><parent_chain><item><author>ggregoire</author><text>Although I understand what you saying about big shifts and kinda shared your opinion, specially about hooks, I started a new project from scratch last week and decided to give hooks a try (and, for reference, I&amp;#x27;ve been using React on a daily basis for 5 years).&lt;p&gt;Oh boy I was wrong.&lt;p&gt;Hooks are way more easier and intuitive than what I thought. It makes code so much more readable and easier to reason about. Especially when before you had to wrap your components into x number of HOCs to inject the props your component needed, risking props collision, making it really hard to debug and use with TypeScript, and eventually making it a nightmare to understand and maintain your component. I&amp;#x27;m not surprised that every React library added a hook API to its core.&lt;p&gt;At the end of the day it makes me more productive, so I guess that big shift was also a big win.</text></item><item><author>ferdowsi</author><text>Congratulations to the Vue team, this is definitely a big win for them.&lt;p&gt;Reading through the RFC is really interesting. They specifically call out the dependency on Facebook as effectively being React&amp;#x27;s Single Point of Failure, citing their negative experiences with HHVM.&lt;p&gt;And for all of the love that people give React&amp;#x27;s big shifts (like hooks), the RFC specifically counts this against them, given that best practices have shifted so drastically in the last few years.</text></item></parent_chain><comment><author>nanagojo</author><text>IMO it is good that the React team was open into investigating different paradigms. It&amp;#x27;s a good thing and you rarely see this with other big projects.</text></comment>