Skip to content

Vue vs. React

Curtis Belt edited this page Sep 17, 2020 · 2 revisions

Update: This may swing wildly in React's favor depending on:

  1. If interoperability between the React frontend and Gutenberg components in the backend is practical to achieve. Currently this doesn't seem to be the case (needs further look).
  2. If many problems facing Gutenberg + GraphQL are fixed

See:


Points from the article

  • "React and Vue.js share many features and philosophies," the proposal explains. "Both enable developers to build UIs in a declarative, reactive, and component-based way; both core libraries are fairly light-weight and performant; both possess large and active communities."
  • We believe that the Foundation would be well-served by adopting either tool. However, we believe that Vue.js has a few key advantages that are relevant for the Foundation's use-cases."
  • Vue.js, the proposal says, has better support for front end build tools like Webpack and Babel, appears to allow code with fewer dependencies, and is evolving in a stable manner.
  • Also, the proposal suggests, React's parentage is a problem. Specifically, React was developed by Facebook, and between 2014 and 2017 the interface library was subject to a BSD + Patents license that other organizations viewed as a potential risk.
  • Facebook in 2017 shifted React to the MIT license, but the company's business model and behavior remain a matter of concern for some developers. [Would need to research what behavior specifically was the concern in this context]
  • The proposal notes, "Vue.js development is not led by a single corporation whose goals may diverge from those of the WMF."
  • The WMF was also unimpressed that another open-source Facebook project, the HipHop Virtual Machine (HHVM), used to convert PHP to machine code for better performance, stopped fully supporting PHP last year, forcing WMF to migrate away from it.
Clone this wiki locally