Oh no. This: https://vuejs.org/guide/reactivity.html#Change-Detection-Cav...

    Vue.set(vm.someObject, 'b', 2)

This is exactly the kind of gotchas that drove me away from the likes of Angular, Knockout, and Polymer to the simplicity of "Just re-render everything" that is React.

Yeah, I often use React or a more react-like library because of this reason.

That said, I feel Vue does offer some things that, say, Angular/Knockout/Ractive don't to offset this, so I could see myself using it in some cases where I would otherwise go for React.

I rather like the documentation, for one, as well as the tooling that offers single-file components (js/css/markup) and plays well with the editors I use (Sublime, Atom).

I've also found that it's often easier for others to learn the angular-like markup compared to learning React.

My understanding is that one of its selling points is that it doesn't have to be a full framework. You can use it for views, create components, or use it as a full blown-framework.

Thanks for the link. Interesting. Seems it supports an angular/knockout-like template syntax by default, but allows you to drop down to the virtual dom layer or even use JSX if you want to. Also it has knockout-style computed properties which may be why it outperforms React. This may go nicely with something like RxJS, so maybe I should try it out with Horizon after all.