News for hackers. Stuff that matters.
Re:Why we chose Vue.js by tracker1 on Friday October 21, 2016 @02:12AM (#12758482)
I just don't like the bidirectional data binding that vue seems to bring with it... I've had enough experience with this in Angular at this point to know that it's painful... then the easiest way around those issues is to use classes, and computed property getters and setters. In the end, it's just painful.

React is much clearer here, but there is more of a cognitive load in getting used to it, there's less magic at the surface. Even combining with something like Redux, or even MobX has another layer of understanding... routing and server-side rendering more still.. but they are layers you learn and add, not everything in one neat package.

I'm also not a fan of the custom DSLs that tend to come with templating engines.

Re:Why we chose Vue.js by vladimir-y on Friday October 21, 2016 @04:20AM (#12758947)
> and computed property getters and setters

It's the exact way how it's implemented in Vue, with old fashion getters/setters and some "magic" for already defined object fields, see for details https://vuejs.org/guide/reactivity.html Vue has no digest cycle (no dirty checking), so you there is no Angular's performance issues.

Re:Why we chose Vue.js by ceejayoz on Friday October 21, 2016 @10:07AM (#12760521)
> I just don't like the bidirectional data binding that vue seems to bring with it...

Vue 2 ditches it entirely, in favor of Vuex, which is inspired by Redux in part. http://vuex.vuejs.org/en/intro.html

Re:Why we chose Vue.js by dimgl on Friday October 21, 2016 @02:14PM (#12763044)
Vue 2.0 moves away from two-way binding.