Wait, Vue doesn't prescribe the notion of a component tree with top level / parent components being containers for stateless feature agnostic granular components? In that context, the concept of a container component isn't too hard to digest, and you can see how all the modern component oriented frameworks work similarly.
So how does Vue differ in this respect? From my limited playing around with Vue, I'm pretty sure it prescribes to container components as aforementioned.
If you ask a general question, there is no context. So the answer is simple - use Vue, not React.
Its way easier to on board and get you up and running, and mature enough that you can develop complex apps if you need that.
Other people usually tell 'it depends', but that is just excuse for not being able to draw a line.
Things change quickly though.
1. The happiness and productivity level I have when perusing one over the other.
2. The actual application being shipped and the level of happiness and satisfaction that I get from the customers.
3. The number of features I can quickly ship on top of the application.
4. The ease of maintainability / support for the application. Easier to maintain = more stars in my world.
The feature set that both frameworks offer are pretty much on par, although I would say (IMHO) that Vue is far easier to understand and seems to be less complex, over all the other frameworks I have used (React, Angular, Ember, Knockout).
Edit: found one. This looks awesome https://www.gitprime.com
Hopefully as the Vue community grows that will drive more resources to the development of cool projects like Weex either directly by having members of the community getting involved on the development of those projects, or indirectly by motivating companies to develop tools to cater a sizable market.
From a comment on Reddit:
> 1.6 million weekly downloads for React vs. 200k weekly downloads for Vue. I don't think the GitHub stars measure much. People are downloading react at approximately 8 times the rate of vue.
(I would still bet that React is used much more yet, just noting that the NPM comparison doesn't tell the whole story - nor does the stars comparison)
I'd be curious of what other metrics Github stars correlates with (# of applications in production, $ in revenue/investment, etc.), but I suppose if Vue ends up replacing React in clear popularity that some will point to this as a significant moment in that history.
There are lots of micro libraries because there's zero barrier to putting something on github and NPM, and there's a huge population of people wanting to practice and demonstrate their programming skill.
Many of those are irrelevant. Guess what? Me throwing a "cool-cucumber.js" library doesn't obligate anyone to learn or keep up with it.
It's like a random author publishing a random book. Who cares? you don't have to read it.
The rest is much more stable. There's a bit of fluff on the surface but underneath is not changing that much.
My father is afraid of git. My sister in law is afraid of open source software. And, that fear is reflected in their career choices and the quality of their code.
Vue is still one of the few frameworks that stays lean.
Easier learning curve by new developers trying to pick a front end framework.
If the parent means by byte count, React + ReactDOM is about 32.5KB, Vue is 30.3KB. Not a dramatic difference in byte bloat, either.
The empire strikes back
 - https://news.ycombinator.com/item?id=17316267
I was laying in bed at 2:30am after watching a TV show and then playing checkers with my wife, and was about to go to sleep but decided to check Twitter one last time (yeah I'm pretty addicted!)
I usually search for "reactjs i" ("i" to filter out blog spam) and this time I saw a few people commenting on this "star race". I knew both React and Vue are close to 100k, and I found it amusing that just as I opened the website tracker, it was leading by 2 (!) stars.
I knew this would be exciting to a lot of people (folks don't hesitate to tell me they prefer Vue to React every day, as I often seek out negative opinions to learn more). So I shared it with some of my personal thoughts on Vue (see follow-up tweets).
Not sure if you implied I had some sort of hidden agenda but you can just chat to me. :-)