(Just putting some of my comments into its own entry)
There is a common misconception about Vue: that it's only for simple stuff. No. The underlying development model of data-driven views and interface composed of component trees is almost identical between React and Vue. The main difference is how the API is exposed and how React leans toward a more everything-in-JS approach while Vue embraces HTML/CSS/JS as what they are.
When you go beyond the basics, the concepts involved in how to structure and maintain state in large, complex applications are not tied to a specific view-layer. For example, you can use Redux with either React or Vue. Both would work. If you can build complex stuff with React, you can do that with Vue too. I'd even claim that anything that can be built in React can be built in Vue with similar if not less amount of time and effort.
Well, Vue isn't opinionated on how you manage your state, nor does React itself. You need to realize that the preference of leveraging immutable data is what the React community has been pushing for, but not something baked into React. That's why there needs to be Flux (and its 1024 different implementations). If Facebook didn't promote Flux as the go-to pattern for building larger React apps, I bet a ton of people would still be using setState() everywhere today - which is essentially mutable state inside the component.
On the other hand, Flux patterns can be applied to Vue too. Vue components do not own the state - they simply observe an external plain state object. Optimizely has been using NuclearJS (their Flux variant) with Vue since Vue's early days. Redux, the currently most popular Flux variant, is also view-layer agnostic. You can use it with Vue no problem, because you can build your Vue components as dumb, purely prop-based ones and just shove a new state tree from the root. Granted you need a bit more discipline (e.g. not mutating state retrieved from stores), but similarly in Redux you need to refrain from mutating state in reducers too. If you want to go the immutable way, it's just something you have to enforce as a rule. The general claim that "React makes your state easier to reason about" is superficial and not addressing what actually contributes to it, and in my opinion shows how many people are just chasing the latest fad without really understanding the details.
If you are interested in enterprise usage, sure Vue doesn't have super high profile usage in US like React does, but it's used in production by some of the most dominant Chinese tech companies: Alibaba, Baidu, Sina Weibo, Xiaomi... in particular, Alibaba used Vue for its mobile channels during the Singles' Day sale (think Amazon during Black Friday).
Nope. In terms of performance, Vue is a bit slower than React for startup but has better runtime performance and is easier to optimize for than React. There are some simple benchmarks out there, but if you are really interested into the details, listen to this JavaScript Jabber episode - the performance parts are near the end.
You need server-side Rendering. If you are not using Node.js then this can't be done anyway. But the cases where you really need SSR is fewer than you think, and it comes with tradeoffs. Read this article for more details
You want to reuse the same codebase for all 3 clients via ReactNative. This is a very compelling reason and Vue doesn't address that at all. But again, it only matters when you need this.