Ask us about:
- Using Vue.js
- Contributing to code base
- Vue.js roadblock
- General Programming advice
Message from the host 💬
Thank you for joining our AMA. The questions were brilliant; we all had much fun answering them. Here is a summary of the AMA:
- Vue 2.5 is coming
- vue-cli 3.0 has started and we want the community to participate
- We plan public roadmap to make it easier to get on board and contribute.
- Egoist and Linusborg might or might not be machines/AI
- React patent issues don't affect Vue; we are unlikely to see any issues surrounding this. Vue will remain on MIT license.
- Company backing is not an issue for us. We believe Vue has already surpassed the critical mass and "survival" is really no longer an issue.
- Weex, NativeScript + Vue, and other tooling will be supported by the team for the long term. We are helping to mature the documentation and bridge the gap to help adoption.
- React Fiber is interesting. Vue can leverage some learnings, and we will watch the space. Although we don't see a strong need to implement something similar.
- Vue 3.0 is in the planning phase, targeting evergreen browsers. This will help us enhance the reactivity system and reduce library size. 2.x and 3.x will be maintained in parallel.
- Web components will not (yet) be part of core, but we will continue to watch this space
- We wish Wordpress all the best with their upcoming challenges and will support them as much as we can. It's still too early to say what will happen here, but we are very excited as a team on the prospects it brings.
Are there any plans for an official package, similar to React Native, for Vue?
Do you feel that if Vue has a Native package (Vue Native 😎), it's adoption would see a rapid growth and hopefully be adopted & supported by major players?
Thank you for your amazing work. Kudos 🙌
Vue.js is awesome; there's no question about it. Considering the recent license changes to ReactJS, many developers and startup are curious these days.
How can we be sure that this won't happen with Vue.js?
Browsing Github issues we can find some hints that Vue 3 may show up in the upcoming future. What are the key features or changes that you consider and how do you imagine potential transition from Vue 2?
A lot of people is worried about a big company not backing Vue, is that a real problem for the future adoption of the technology?
I love Vue for its great simplicity to use, the high quality documentation, and the entire ecosystem* around it. What are the next major efforts for the team and how or where can I best follow those efforts?
(aka if I see something I can help with, I'd love to, otherwise just follow)
*vue-cli, easily used and extended templates, VS Code's vetur, Chrome DevTools extension
I have no question, but I use Vue on a daily basis and I just want to thank you all
Should developers to use jQuery with Vue.js? Why and why not?
Will Vue.js utilize web component APIs in the future?
Can you explain the upcoming reactivity system rewrite? What will be the gain from the user perspective and what potential side effects we should be aware of?
What is the biggest challenge in trying to support something that is used by other people? Do any of you ever get frustrated by others' misconceptions about Vue or that it doesn't often get the credit it deserves?
Thank you and keep up the hard work.
Thank you guys for your work on Vue, your many side projects, and help in the community. With FB's move to React Fiber, have you given any thought towards implementing something similar? Are the concerns FB's attempting to address even applicable?
Evan You: Why did you start Vue.js project? What was your initial thought? What problem were you trying to solve?
With Weex or NativeScrict, we can make Vue a native solution.
But, will Vue.js team make a single native package ? (named "Vueative" ?)
Vue.js is definitely mature. I see new upcoming challenges as heading toward definitive growth and more "React-ish" kind of moves tempting you.
What do you think it would take to stay true to your initial mission and values despite external forces pulling you in different directions?
Because I know you want to keep your independent style and approach. And that's awesome.
Hi Vue.js team ! I falled in love with vue-class-component and vue-property-decorator, and all my Vue projects are now using them. Now that class and property decorators are stage 2 at tc39, I was wondering if you plan to make an official template which use decorators (either ES6+Babel or Typescript).
Which, according to you, is the best resource (other than your own docs) to get started with Vue?
What did you plan about mobile app ? I follow weex but documentation is a little obscure and i don't see lots of project using it in production (some chinese company but it's all). Did you think weex and his documentation are production ready ?
Else we have other alternatives with nativescript and vue (but still in progress), OnsenUI for not native apps ...
What is the best way for mobile apps with vuejs ?
Do you like the idea of build-only frameworks like Svelte? Would Vue.js ever go in this direction?
Hi there! Thank you for hosting this AMA!
Currently, each Vue component requires at most one root element. Are there any plans to allow multiple root elements in components?
With Vue releases named after anime titles, how many of you actually watches anime?
Is there anyone else apart from Evan You maintaining the core of Vue.js?
Will it be a major shift in JS world when WordPress decides to choose Vue now that it has ditched React cause of all the license issues?
Beside Nuxt, what do you recommend for a static site generation?
Thoughts on Mesut Ozil? #COYG
What did you guys learn from your work on Vue and from contact with its userbase, be it on chats, meetups or consulting work? Was there anything you were expecting that didn't happen during last year of Vue growth or something that did happen, but wasn't expected?
Using the opportunity, can you guys officially and honestly confirm or deny that Egoist is an artificial intelligence written by Evan to solve all Vue-related problems, one package a day? I know many people who are raising such suspicions, because of how active he is in the ecosystem and how high quality his packages are.
What are your thoughts in mutable vs inmutable approaches to handle application state in fe frameworks ?
I try to follow Vue community close but so far I have yet to find a popular Vue package written by a woman. It's of course highly possible they are parts of larger teams or stay behind package names, but except for Sarah Drasner who makes high quality tutorials, courses and talks about Vue (and codes brilliant animations), we don't see women active in Vue community. What can we as fellow developers do to make the community more open for them?
Can I know what are your thoughts on Facebook's patents on VDOM (the most lucrative thing about Vue) and whether it'll affect the open-source community if Facebook decide to do something about it?
Not sure if these questions are best for here or another forum.
Question 1: Vue developer tools works amazing when working on small scale applications with simple mution paths, but anytime we try to use it in our complex mutation webapp it crashes instantly with the increase in mutations. Is there a plan to improve the performance of the dev tools?
Question 2: Vuex Plugin examples for sockets isnt extremely clear, especially if you are subscribing to multiple sockets and I have not been able to find an example of anyone else using plugins extensively. How would one best integrate with Sockets for vuex?
Next year's VueConf will take place in London. Were there other alternatives, signaled by potential organizers? Are you aware of plans for other big Vue-related gigs, similar to VueConf or the New York meetings?
My company has a big code-base (mainly a component library) written in Angular which we'd love to port to Vue but it's too much work to do it in one go.
Are there any plans for an official way to use Vue in existing AngularJS apps to slowly transition? There are a few tutorials and 'hacky' suggestions on the web but I think lots of people would make the jump if it was easier.
Any plans to improve TypeScript support and make it work out of the box with vue-cli
I bet you've heard of MoonJS. What do you think about it? Are there ideas VueJS could benefit from like it did for Angular and React?
What is a great starting point to study the Vue.js code? I would really like to study the library code but I often find myself in a situation where I don't know where to look first, what files should I look for to begin with. Do you have any tips for this?
Just wanna say, you all are awesome! The team answers the question so quick and in detail in the vue.js forum. Especially Thorsten, because he answered most of my questions :) Thanks!
I'm just a-week-old-Vue-developer ;) I mainly code using ember.js! I feel vuejs as a combination of various frameworks (react - say, flux architecture, angular - say, HTML attribute kind of things and ember - say, computed properties ). Is that true that Vue was born by integrating all the pros of various frameworks?
Hi ! Will VUEJS move to typescript (like NG2 does) ?
After the official release of vue-test-utils, will there be a separate official testing guide similar to SSR one? I know the new package comes with its own documentation, but is there any plan for a broader guide for testing?
I have really loved learning Vue this year, I am new to it. I come from a backend development background so don't have a lot of the front-end expertise as a lot of other folk. A challenge I have found is making decisions in design and frameworks that have big impact on your project. Once you are committed there is a lot of effort to change For example I am using Vue with Nuxt and Vuetify. I want to see how SSR behaves and I want a GUI framework that is responsive and supports this design choice. But that is just one of many options.
What is the most common / recommended setup for Vue projects?
One of my concerns is for these other frameworks as well. I don't think Vue is going anywhere but who says Vuetify is going to be around in a year or maybe something new would be the next big thing.
Any suggestions on what we can do to best decide on what core components / frameworks to use?
thanks for all the great work you guys do by the way.
Hey, Why Vue doesn't use custom tags (like some other frameworks) and and prefers changing it into div or any other valid tag ? (actually I'm fan of this method) And my other q : Since I'm Ember dev too, Is there any plan to create anything like EmberData in Vue too? cause that's awesome and really helps in big projects.
As someone that is becoming very familiar with VueJS as a developer, I would like to also start contributing.
What parts of the Vue framework would you recommend would be the easiest to learn from?
Vue is awesome, and our project is considering using it. However, the recently Facebook React Patent issue has raised our attention, does Vue use any patent that holds by Facebook? Here is an extend read about the BSD+Patent license, where the author stats using Vue and Preact may be riskier than using React: https://email@example.com/react-facebook-and-the-revokable-patent-license-why-its-a-paper-25c40c50b562
1) "Don't use Vue for large-scale projects and also if you have a large team Angular is better.", do you agree with this?
2) How about functional programming in Vue?
3) What a beautiful logo Vue has :)
I print data and the result is [ob: Observer]，There's data in there, but you can't get it out
I like chocolate, so I'm really curious to know, do you have any plans for Vue-flavoured chocolate?
What's your opinion on corporations enforcing less open licenses on their Open Source projects? e.g. Facebook's BSD license
Is this justified?
Which method do you prefer for write and manage CSS? Vue's own Scoped styles (which is similar to CSS Modules), or any other CSS-in-js tool?
Whats your plan with competing with other frameworks?
Vue.js has removed some of the core functionalities like Filters in Vue2.0.
Would not be it really handy and helpful for developers to have them?
What's the trade-off for Vue.js between features in framework vs size of the framework(which makes it pretty fast)?
We have production apps using angular 1 as well as ng2 with typescript. Is it relatively straightforward to build new features with vue and have them work in our apps. Are there known/significant integration and build hurdles for hybrid vue usage in angular apps?
Looking at the answer '...the hardest part is telling people that it (feature) won't make it into core', what types of feature requests are common that would not make it into core?
Is Vue.js a good project for open source newbs to contribute to? I am becoming more and more familiar with it, and would love to contribute. Any pointers?
Are there plans to improve the user experience of vue-cli. It doesn't have the same "ease-of-use" as the rest of things associated with officially supported Vue repos. Will additional focus be given to improving it from a user flow perspective.
I'm checking again on using Vue in production for a client. The upstream Vue version deliberately fails mounting on the body element (el === document.body || el === document.documentElement && fail or something like that).
Yes, Vue 2.0 does replace the element it is mounted on, but there is nothing DOM uncompliant in replacing the body, even while this will often fail due to browsers trying to close runaway tags, or 3rd party code doing the same.
I insist on re-enabling mounting on the body element as a very useful thing. When trying to do SEO friendly SSR on our previous projects with vue 1.x, we were very pleased how well it worked with routing. On client-side, routed body element worked like magic to automate things like event listener attachment, setting ARIA attributes according to page content, lang or text direction properties, or changing contextmenu attribute when it was still a thing.
I tried to remove the check and use vue 2 on our past projects, and so far, nothing breaks. The few 3rd party scripts that rewrite the body as a string have to be removed and rewritten for use with an SPA anyways.
How can we educate software developers to be more inclusive and participate in open source?
Over the last 6 months or so, I've been creating proof-of-concepts for migrating some of my company's large projects to Vue. In doing that, I've come up with some assets/enhancements that are useful for large projects I'd love to feed back upstream (in particular, enhancements to the webpack vue-cli template for building with more configurability, and also a Cordova/Vue template). Assuming you might be interested, what would be the best way to get that in front of you guys and start the conversation?
What does your workspace look like? Also, what editors and applications do you prefer?
Seemingly odd question, but...what exactly was the train of events that led to the creation of Vue?
Hi all, fantastic work you have done with Vue.js so far. I would like to know when the vue-test-utils package will be released. As it would be a definitive must-have for a wider adoption in the company I work for (Orange not to name it). We have a test driven development philosophy for many services and it would help us a lot ! Keep Vue.js as cool as it already is !
A follow up on my previous question that Phan answered,
Phan, do you think I am not aware of the issue with too much code always competing for the document.body? Dan Abramov gives amateurish reasoning on the issue in the article you linked. Do not read his stuff.
A lot of shoddy written third party code competes for document.body or the body sting content, and you always have to rewrite code that runs into conflict while doing so invariably of how you use Vue on the page.
In our case we need to do that. We have complete control over 3rd party code, and we rewrite stuff that misbehaves.
How to get in touch with you guys outside of AMA?