3 ms·
Although this may be controversial, the composition API feels very derivative of React hooks. I liked having Vue around as an alternative to React, and the decl
by doteka 6y ago
Although this may be controversial, the composition API feels very derivative of React hooks. I liked having Vue around as an alternative to React, and the declarative and predictable structure of components felt like the main selling point to me.
With this new API, my first impression is “just use React at this point”. I’m having serious trouble understanding why they’d make this change. Of course I may be biased working in React day to day, but... bleh, Vue used to be unique.
- deleted 6y ago[deleted]
- acemarke 6y agoIt _is_ derivative of React hooks... but that's not a bad thing at all. (And to be clear, I'm deeply involved in the React community myself). Tools and libraries are always influenced by what's going on in the ecosystem. New features and concepts in Tool A inspire something else in Tool B, etc. The React team came up with something reasonably novel with the hooks API (but with its own set of prior art [0]). There are several aspects to hooks that folks have expressed concerns about, but overall adoption has been positive and rapid. The Vue team looked at React hooks, saw something that seemed like it could be useful for Vue's API, but came up with their own spin on the idea that makes them better fit the Vue use cases and design philosophy. I don't see any of this as a problem - sharing ideas and improving DX is a _good_ thing. [0] https://reactjs.org/docs/hooks-faq.html#what-is-the-prior-art-for-hooks https://reactjs.org/docs/hooks-faq.html#what-is-the-prior-ar...