News for hackers. Stuff that matters.
Re:Why we chose Vue.js over React by tyingq on Sunday December 11, 2016 @10:48AM (#13151515)
I was initially confused about why a Drupal shop would need either Vue.js or React, since Drupal sites are most typically blog like things.

Appears it's for their backend though, and this is actually pretty nice: http://pixeljets.com/sites/default/files/why-we-chose-vuejs-...

Re:Why we chose Vue.js over React by fabian2k on Sunday December 11, 2016 @11:10AM (#13151629)
Drupal is a bit overkill for a blog-like site, my impression is that it is usually used for more complex sites than e.g. Wordpress.

With the latest version Drupal 8 there also was a push to make headless Drupal easier, which is pretty much just the Drupal data exposed as an API so that you can create SPAs for it.

Re:Why we chose Vue.js over React by tyingq on Sunday December 11, 2016 @11:14AM (#13151653)
More complex, sure. But it's still very centered around taxonomy with dates/sections, end user editing of nodes with WYSIWYG, page centric tags, etc. Very blog like.

Seems like a big hammer for use as a datastore for an SPA.

Re:Why we chose Vue.js over React by snurycombinator on Sunday December 11, 2016 @12:37PM (#13152074)
That was true back in Drupal 6 in 2008.

Drupal 7 and 8 use entities, which are arbitrary combinations of fields that can be composed through the UI and accessed through APIs via JS or other methods.

One thing we use it for is its user management which is good enough out of the box.

Re:Why we chose Vue.js over React by dnm on Sunday December 11, 2016 @11:18AM (#13151679)
Blog like things? http://www.nba.com/
Re:Why we chose Vue.js over React by tyingq on Sunday December 11, 2016 @11:22AM (#13151711)
Yes. And you could produce that with wordpress as well using custom post types, with probably a similar amount of headache. They are both CMS systems that primarily handle taxonomy, nodes, tags, WYSIWYG editing, etc.