{"id":2862,"date":"2017-09-15T12:26:52","date_gmt":"2017-09-15T07:26:52","guid":{"rendered":"https:\/\/ahmadawais.com\/?p=2862"},"modified":"2023-08-16T05:52:22","modified_gmt":"2023-08-16T12:52:22","slug":"wordpress-react-vue-preact-development","status":"publish","type":"post","link":"https:\/\/ahmadawais.com\/wordpress-react-vue-preact-development\/","title":{"rendered":"WordPress-React Breakup: My Vue on P*react + WordPress Development!"},"content":{"rendered":"

ReactJS and WordPress are breaking up. Matt Mullenweg (co-founder of WordPress) announced<\/a> is it today.<\/p>\n

I was half asleep when I read the announcement and since then I have commented<\/a>, created a Twitter Poll<\/a>, a Facebook poll\/thread<\/a>, started a Gutenberg issue\u00a0Choosing the JavaScript Framework for Gutenberg (~WordPress)<\/a>, and now I am writing this post. It’s an exciting news.<\/p><\/blockquote>\n

Since I believe the community is moving in the right direction here \u2014 this issue<\/a> is where one could share their thoughts about different JavaScript Frameworks for Gutenberg (that goes into the WordPress Core).<\/p>\n

\ud83d\udea2\u00a0JavaScript Frameworks#<\/a><\/h2>\n

IMHO there are two prominent contenders here.<\/p>\n

    \n
  1. VueJS<\/a><\/li>\n
  2. Preact<\/a><\/li>\n
  3. Other options (Angular<\/a>,\u00a0Ember<\/a>,\u00a0Polymer<\/a>,\u00a0Aurelia<\/a>, etc.)<\/li>\n<\/ol>\n

    Just to kick-start the discussion, here’re a few thoughts from the top of my head.<\/p>\n

    \u26a1\ufe0f\u00a0VueJS<\/a>:#<\/a><\/h3>\n
      \n
    • PRO<\/strong>: Beginner friendly.<\/li>\n
    • PRO<\/strong>: Proven track-record of success with Laravel.<\/li>\n
    • PRO<\/strong>: Way more popular as compared to Preact with a great amount of community support.<\/li>\n
    • PRO<\/strong>: More contributors than Preact.<\/li>\n
    • CONS<\/strong>: Key person dependency.<\/li>\n
    • STATS<\/strong>: 133<\/a> Core Contributors on GitHub,\u00a0212494<\/a>\u00a0Stargazers, and\u00a0209<\/a> Releases.<\/li>\n
    • MONETARY BACKING: <\/strong>At the time of writing,\u00a0VueJS OpenCollective<\/a> ($9,895\/year \u2014 New campaign only four days old) and Evan You’s Patreon page<\/a>\u00a0($8,815\/month) monetary backing from the community.\u00a0S\u00f6ren in comments pointed out that OpenCollective of Vue is only four days old.<\/li>\n<\/ul>\n

      \ud83c\udfaf\u00a0I truly believe that WordPress can do a lot better with VueJS. VueJS has a huge set of followers and it’s easier for beginners to adopt. This can also turn into a big win for WordPress if done right. I have used VueJS myself, in several projects, and I love it.<\/p>\n

      Also, a framework that’s used outside of WP (such as Vue and its integration with Laravel), allows developers to use their experience in WP projects and non-WP projects.<\/p>\n

      There’s already a large cross-over of Laravel\/WP devs, so having the same js framework makes a lot of sense as those devs can contribute to help drive Laravel, Vue, and WP forward all at the same time. \u2014 Jason Bahl.<\/em><\/p>\n

      \u26a1\ufe0f\u00a0PreactJS<\/a>:#<\/a><\/h3>\n
        \n
      • PRO<\/strong>: Easier transition.<\/li>\n
      • PRO<\/strong>: Evolving community with about the same amount of monetary support as of VueJS.<\/li>\n
      • PRO<\/strong>: A subset of React based libraries would still be well supported with Preact and with compat.<\/li>\n
      • CON<\/strong>: Transition could lead to messy code and confusion (for beginners).<\/li>\n
      • CONS<\/strong>: Key person dependency.<\/li>\n
      • STATS<\/strong>: 100<\/a> Core Contributors on GitHub,\u00a038970<\/a>\u00a0Stargazers, and\u00a0114<\/a> Releases.<\/li>\n
      • MONETARY BACKING: <\/strong>At the time of writing,\u00a0Preact OpenCollective<\/a> ($16,087)\u00a0monetary backing from the community.<\/li>\n<\/ul>\n

        While PreactJS has its benefits, I am not the right person to ask for an opinion about it (since I have only slightly used Preact in two small projects). Though, it does look like that transitioning from React to Preact is very easy. That can motivate developers to chose Preact. I think this would be the wrong reason to chose it.<\/p>\n

        \ud83e\udd14\u00a0I think this would be the wrong reason to chose it. It will only confuse the developers trying to adapt to this whole\u00a0new eco-system of JavaScript frameworks, node modules, Webpack, and now aliasing Preact over React? Which could also lead to the code smells. Messier code.<\/p>\n

        Resources:#<\/a><\/h3>\n
          \n
        • My\u00a0Twitter Poll<\/a>\u00a0for 48 hours.<\/li>\n
        • Facebook Thread: Advanced WordPress Fb Group’s\u00a0Discussion<\/a>\u00a0&\u00a0Poll<\/a>.<\/li>\n
        • GitHub Issue:\u00a0Choosing the JavaScript Framework for Gutenberg (~WordPress)<\/a>.<\/li>\n<\/ul>\n<\/section>\n
          \n
          \n
          \n
          \n

          \ud83d\udd25 [imp] Since #Reactjs<\/a> is out of the picture for #WordPress<\/a> — what's your pick for the JS framework which goes into the @WordPress<\/a> core!<\/p>\n

          — Ahmad Awais (@MrAhmadAwais) September 15, 2017<\/a><\/p><\/blockquote>\n