8 Comments

  1. Greg Brown

    Does Vue or Preact have a stance on backwards compatibility? I’d say one of the most important and under appreciated features for WordPress’ success has been its commitment to be backwards compatible (eg compare to Drupal). I haven’t seen any mention of this around that in the JS framework discussions.

    Seems like it would be good to choose a framework with the same commitment.

    Report

    • Andrew Duthie

      From the perspective of Gutenberg, this was a major consideration in taking an initial exploration with React. While any framework will most certainly claim to have a commitment to backwards-compatibility, from an external point-of-view it’s a matter of risk and observations of history. React and Vue are both successful in offering migration paths for version upgrades (react-codemod, vue-migration-helper). React had a slight edge in targeting a small and focused API surface area, embracing the JavaScript language in its templating, and having a deterrent to drastic changes via Facebook’s own production usage (at least not without a long and well-defined deprecation path). There were compromises here in losing out on Vue’s fantastic onboarding experience, which we hoped to remedy by simplifying the block API as much as possible, minimizing the role of React to only representing a block’s edit and save representations.

      Preact is in a unique position of following React and serving as a distillation of its core concepts. The project has been mostly successful in avoiding the need for an upgrade path (never implementing PropTypes, createClass), but it’s still an open question as to how closely it stays in sync with the upstream React project, and whether the associated risks (fewer direct contributors, likelihood of sustained maintenance given the perceived fate of the similar Inferno.js project) are worth taking on.

      Report

  2. Mattias Johansson

    There are valid reasons why one might pick Vue over React, but licensing isn’t one of them. Vue has the MIT license w/o Patent grant, which is doesn’t grant any patents whatsoever. If you’re worried about the React license, you should pick something that uses Apache 2.0 license.

    Report

    • Peter Knight

      Vue has the MIT license w/o Patent grant, which is doesn’t grant any patents whatsoever.

      In other words you are saying that OSS licenses with a patent clause are better than those without, implying that we’re all better off adopting licenses with patents clauses that in the case of React was written with the explicit intent to defend the interest of a single corporation.

      99.999999% of sites using and choosing WordPress will never have to deal will issues with patent trolls. We don’t need licenses with a non-standard special clauses defending the interests of a corporation. Rejecting that doesn’t mean we are only consistent if we then pick a tool with say, apache 2.0, that would imply we feel it is necessary to have a patent clause packaged with our software. WP ships with GPL and we’ve done fine without complicating matters by introducing non-standard licenses into the mix.

      For me and I suspect plenty of others the license was a blocker not because of fear of malevolence on FB’s part (although that can’t be entirely ruled out either), but about why and who put it there and what is symbolizes: a corporate with goals contrary to those who value an open web who by necessity have worded a non-standard patents clause that uniquely defends their corporate interests. The OSS licenses compatible with WP don’t have *any* wording to protect the interests of any particular business, nor should they and nor should we want other OSS projects powered by large companies to start injecting their own non-standard legalese. Nor is there any overwhelming reason to adopt a software that includes a patent grant in the first place in the space that WP operates in. There certainly was no good reason to pick a tool that has a non-standard clause when there are many solid alternatives available.

      So, I disagree strongly with you, licensing was one hell of a good reason not to go with React.

      Report

    • chuck

      I’ll take my framework without license grants over one that will potentially revoke its license if I’m ever infringed on by them and don’t simply hide in a corner like a scared puppy. Which is essentially what React was forcing, under the guise of self-protection from trolls.

      I’m actually surprised it took WP/Automattic this long and burned so many cycles on dev, before comprehending this.

      Report

  3. Hashim Warren

    This means WordPress can easily ensure Vue’s sustainability by becoming a major sponsor

    Implied: WordPress can have influence on the direction of this project.

    That should be a factor in the decision.

    Report

  4. Bryan

    Writing this article must have been a Grammerly nightmare.

    Report

Comments are closed.

%d bloggers like this: