You know who is dedicated to helping you understand more about Vue and if it’s right for you and your team? John Papa.  

Check out some of the top questions and answers from our recent webinar, Vue from 20,000 feet. Then, make sure to dive into some amazing real-time coding examples (and killer tips and tricks) by watching it on-demand here >>. 

You’ve got to make the decision for yourself, and there are a few things that I really look at with Vue. First, it is simple to get started, even once you get going on larger apps. It's very powerful. It's not just something you can build a very quick demo with—you can build a very powerful, successful application. But, you want to make sure that your community is going to support it.

It's very easy to get going. You can get running in minutes and learn a ton a week. When I first took a look at Vue a couple of years ago, I spent less than a day on it and I built a few apps and thought—wow, I really understand the basics now. It just felt intuitive to my programming style, and I hope you'll find that too.

First, you can only go install node from node.js org, and download the LTS version. If you're not familiar with the versioning, LTS stands for longterm support. That's really important because you want to make sure you get the most recent long-term support version. Then, you'll run and install the Vue CLI.

In Angular, you have to give it the flag of production. It's one of the differences between two of the major frameworks. I like this because I only build when I'm going to go to production or to another server. You might be wondering, "When you want to run and test your local code, don't you build?" Yes, but I do it through the NPM run serve flag and that's going to build it in memory, which is super fast and allows me to debug it locally.

Vue CLI has a UI. There's a CLI, which is all terminal-based and has a user interface. That user interface is really nice because if you're brand new to this you can actually go through this UI and get a visual way to do things (like create your apps or configure different pieces of it and add-in plugins). Maybe you want to pull in Vue X, or routing, or other features like a bootstrap library, and you can do that. You can also build and serve the code and get a lot of visual feedback.

The short answer is it’s your personal choice. Vue, React and Angular are all very powerful. They all do very similar things, just in different ways. Honestly, it's like why some people like pizza with pepperoni and some like it with anchovies and some people just like it with plain cheese. You just have to pick your style of building.

Generally, in Vue, we don't use RXJS as much as we do in Angular. RXJS is super popular, and it's something that Angular uses heavily. But in Vue, you can use it if there are libraries to hook it and if you want to—but you don't have to. There are definitely some very good form libraries with Vue as well.

Yes, the Pluralsight course that I just put out a couple of weeks ago is a good one to start with. The docs are really amazing. You can also go follow some of the core team members like Chris Fritz or Evan You or Sarah Drasner. They all have really good content on the web. There's a huge Vue community. In fact, I'd be remiss if I didn't mention there's a community called Vue Vixens. They set up free workshops around the world to teach women Vue in a day.

Yes, and I recommend Vue 2. Vue 3 is going to be rewritten from scratch in TypeScript, which will allow you to have their cleaning backwards compatibility with you. If you want these in JavaScript, they're there. They're also going to make it easier to use TypeScript in Vue 3, which is one of the cool things coming out.

Good question. I go into this more in the course, but effectively created comes first. That's when the component is created and mounted on the DOM. There are different components that you can pull in from jQuery UI, which you need to know once the elements were mounted on the DOM. Mounted is great for looking into things like that.

Hard to tell. I teach a lot of people, and it seems that in about a day the fundamentals of Vue, Angular and React can all be learned. Which one do people lock on to faster? I think it depends. Assuming you had no knowledge of any of these things other than JavaScript, Vue is the easiest to get going. However, if you have TypeScript experience or any experience with a typed language, Angular really kind of follows a lot of those policies and conventions. Angular is very easy to get going if you have Java or .NET backgrounds. So any of those can work. I've taught a couple classes where people didn't want to go down the road of the template syntax, so React really speaks to them. It really depends on what kind of person you are to figure out which one will be easiest to get going with.

Yes, absolutely. The team is not going to just basically take all the learnings they've had over many years and throw them away. Your apps will still work. The skills you're learning with Vue 2 will still be applicable to Vue 3, although there'll be additional things you can do, especially the TypeScript parts. I believe they're also looking into hooks.

Vue is a really amazing technology that is easy to pick up and incredibly powerful. However, understanding where your strengths currently are and where you’re headed can help you decide if Vue is the technology you want to use. Ultimately, taking a day or two to learn the fundamentals can give you the insights you need to see if you’re making the right choice. 

For more, watch the on-demand webinar here >>.