Vue.js: the good, the meh, and the ugly
I really like a lot of things about Vue. I was apprehensive about using JSX when I first started using React, and I also did not like setState. I think the real issue, though, was that I wasn&#x27;t thinking functionally. I now rarely write a stateful component, and when I do, it&#x27;s usually once, for the entire application, or maybe for a few large subtrees if the app is very large. State kept alive by parameters is extremely powerful and elegant (just read about gen_server in Erlang or the State monad). I am never a fan of two way data binding as an alternative. It&#x27;s extremely hard to reason about, and it&#x27;s not nearly as composable or simple as a tree of functional transformations. So I think that, if you compare Vue to React Component classes, Vue can be quite nice, but the reality is that idiomatic React should have you writing 80%+ small, simple, composable functions with no state, and you really can&#x27;t get any syntactically barer then that. It&#x27;s also the way I teach React. When you first see a function going from state to jsx, it really just makes so much sense, and you ask yourself why you&#x27;d ever bother with anything else.