Agreed with this. I use both React and Vue intensively, day to day. React and Vue both have pros and cons, but I would argue it's actually easier to optimize Vue apps.

Vue's reactive nature actually is superior, because something like Redux requires destroying, regenerating, and messaging around entire objects. This can create serious problems when, for example, trying to use Chrome APIs or manage component renders.

Also, although JSX is nice for developers, it's not friendly to designers. Vue, however, supports single file components that are very designer-friendly.

FWIW, Alibaba began creating their own native framework with Vue called Weex, which is now part of the Apache project. https://weex.apache.org/

Redux is not actually necessary for React, you can manage state without it.

Can you clarify how Redux causes issues in those scenarios?

Beg to differ it can, but as it stands the statement is correct.

http://www.npmtrends.com/angular-vs-react-vs-vue-vs-@angular...

Even more so when you consider that Vue itself is a React clone underneath. Templates compile directly into createElement calls internally and if you'd strip off Vue's outward complexity, the api surface, the syntax parsers, the observable system, etc., what would remain is React.

Well they can disagree, but React is vastly larger (in both usage and community), so I would say his comment stands.

I'll take a look at Vue.JS, thanks! Is there a way to use it from Kotlin or some other "sane" language as well?

It has pretty decent TypeScript bindings iirc, but the fundamental thing it does is prevent the need to mix HTML and JS inline. If you can hold your nose at Javascript, most of the project generators for Vue.JS seem to prefer using ES6/ESnext syntax so the language is much more tolerable than, e.g. Angular and Circa-2007 JavaScript.