1) Opinion: I don't think it's true. Vue is fully featured, has all the tools and official library to create very large applications. More options are coming like a better ESLint plugin to enforce best practices. Personally, I worked on one project that counted 200+ components and counting. 2) You can use functional programming, especially in computed properties and when using Vuex. 3) Evan's Illustrator skills at work!

Facebook may have its (good) reasons for that, even more so being a big company that may want to protect itself from others (as patent fights in courts are very costly).

Evan already answered similar questions. Take a look at: https://hashnode.com/ama/with-vuejs-team-cj7itlrki03ae62wuv2r2005s#cj7iu7wur03ae6iwtrugc4l75 https://hashnode.com/ama/with-vuejs-team-cj7itlrki03ae62wuv2r2005s#cj7t9rqhv01tthowumpizjzzg

Custom tag names in the templates are treated as components. If the corresponding component is not found, Vue will warn you. It would be difficult to get around this IMHO.

Thanks for your feedback! We are currently working on a Cookbook that will feature recommended libraries and code examples for several use cases. In the mean time, you can ask on the forum.

Our plan regarding Weex and NativeScript Vue is to help writing documentations and improve the on-boarding experience. As you mentioned, there are a lot of hybrid solutions as well from the community!

I can't tell which one of Atom and VS Code I like the most.

You can start looking at the test suite and try improving it. It's a great way to learn more about the API and the internals!

Vue will not 'move' to Typescript, but the 2.5 release (in the beginning of October) will improve Typescript support a lot.

I would like to point out that we are using the 'Squash and Merge' feature on GitHub when merging PRs, so the commit count isn't very representative of the community contributions.