{ "version": "https://jsonfeed.org/version/1", "title": "eay.cc", "description": "Weblog von Stefan Grund", "home_page_url": "https://eay.cc", "feed_url": "https://eay.cc/2017/on-react-and-wordpress-matt-mullenweg/feed/json", "icon": "https://eay.cc/apple-touch-icon.png", "favicon": "https://eay.cc/favicon.ico", "author": { "name": "Stefan Grund", "url": "https://stefangrund.de/", "avatar": "https://stefangrund.de/avatar.jpg" }, "items": [ { "id": "33440", "_type": "link", "url": "https://eay.cc/2017/on-react-and-wordpress-matt-mullenweg/", "title": "Matt Mullenweg: On React and WordPress", "content_html": "

Link \u2192

Interesting development in the WordPress community: After creating it’s modern, React-based Calypso interface in 2015, Automattic and the WordPress team are now parting ways with React, because of a patent issue in it’s license. They are going to rewrite their upcoming Gutenberg editor with a new, yet to be chosen JavaScript framework, which then should become the new standard for WordPress.

\n

While Preact, a lightweight React alternative with the same API, would be the obvious replacement, a majority of the community prefers a switch to Vue.js. An opinion I highly support. I had the opportunity to learn and work with Vue.js in my day job and for shortfil.ms 2.0 in the last couple of months and I’m hooked. I think it’s right up WordPress‘ alley, because it’s an easy to learn, yet powerful framework and could be a perfectly fitting foundation for modern front-end development with WordPress in the years to come.

\n

TL;DR: +1 for Vue.js

\n\"\"", "date_published": "2017-09-15T20:15:50+00:00", "date_modified": "2017-09-15T22:02:02+00:00", "author": { "name": "Stefan" }, "tags": [ "frontend", "javascript", "react", "vue.js", "web-entwicklung", "wordpress" ], "_short_url": "https://eay.li/317", "external_url": "https://ma.tt/2017/09/on-react-and-wordpress/" } ] }