What Makes Vue Great?
Developing for Vue couldn't be more simpler, you use standard HTML5, incorporating handlebars or HTML attributes to retrieve your dynamic data. You can include filters, pipes, all sorts of data mutaters. You can control at what part of the component lifecycle code is executed in fine detail. I mean there's not much I can;t say about this framework. The beauty is, if you learn Vue, you don't have to learn too much more to learn React and Angular 2.x. It's an easy transition to one of those other frameworks. Never seen a Vue site before? Check out DLive which is also associated with Steemit on the blockchain. This site is built using Vue and it works and functions great.
Why Not Angular 2+?
Angular 2 was just being released so I decided to start learning that. My thinking was, get a jump on this new framework and I can be one of the first experts using it. What I really liked about it, is the framework included everything you needed start to finish, no extra module were required to build an app. It includes a router, and HTTP processor and everything, the down side to this, is if you're not using those built in module, the code is still there making your app bulky. After building a few apps for fun over the course of about a month, there were so many revisions to the core that the first app's coding was vastly different to the second app's coding, and both apps were pretty much doing the same thing. The first stable release of Angular 2 was September 14, 2016. Shortly following that, Angular 4 was released March 23, 2017. Just 6 short months after Angular 2's initial release, and guess what... Major coding overhaul. November 5, 2017, Angular 5 was released... only 8 months later. May 4, 2018 Angular 6 was released. So for me this kind of instability is unacceptable in a framework. I don't want to develop an app and its core has drastically changed every few months. I understand incremental updates such as Angular 2.1.2 but going from Angular 2 to angular 6 in a matter of about 18 months is a little too much for my taste. I'm not going to spend my time learning something just for everything to change after im finally comfortable with it.
What About React?
React seemed to be the framework where all of the jobs were looking at. React is great, unlike Angular 2+ which had everything included, React is modular which means include only the modules you need and keep your app lean. This is great, for someone who's been in the framework for a while and knows all the different modules that can be integrated. But, to that point, if you want to integrate React into an already existing page, you can and it's fairly easy, you can't do that with Angular 2+. So I started spending more time learning React my problem was, at the time, there was not enough documentation to say, "If you want to accomplish this, use this module, here's how it integrate with React". I was getting , "you should use this module, no use this module" and I would look at those modules, add them in read the integration documentation and get it working... yay. Here's the issue with this approach. I'm very forgetful, and it always reminds me of that scene in the "40 Year Old Virgin" where Steve Carell's character is in this sex information class for these teenagers and is asking questions to the group leader and he asks, "Is it true if you don't use it, you lose it?", well in the coding world this is very much the case. So for everything you want to do outside of core React stuff, you have to learn the different module and how it integrates with React.