It's time to ditch Medium for good! 🌈⚡️

Introducing Devblog by Hashnode. Blog on your domain for FREE. Highly customizable and optimized for developers.

Learn more

Ask anything to Vue.js Team

Vue (pronounced /vjuː/, like view) is a progressive framework for building user interfaces. It is designed to be incrementally adoptable, with the ability to scale between just a library and a full-feature framework, depending on your use case.

Ask Vue.js Team about:

  • Using Vue.js
  • Contributing to code base
  • Vue.js roadblock
  • JavaScript ecosystem
  • General Programming advice

Hosted by:


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.
Ask a Question

183 discussions

Should developers to use jQuery with Vue.js? Why and why not?

My take on this is this: You shouldn’t feel that you need it, most of the time - but if you do, there’s nothing wrong with that (We’ll get to jQuery plugins further down).

Why would you not feel a need for it? jQuery’s core functionality (the parts I used and see used) has three main areas of focus:

  1. Making DOM manipulation really easy
  2. Making animations easy
  3. AJAX

Concerning DOM manipulation, Vue takes care of that in almost all cases. In the few where you actually might need to access the DOM (to focus() an input element programmatically, for example), the DOM API provided by current Browsers is more than good enough in many cases, so you can do that with a simply document.getElementById(‘#myy-id’).focus() (Actually, this is a bad example as Vue’s $ref feature would allow you to do this without any DOM query at all)

Concerning animations, it’s worth learning how to use CSS transitions and animations (with or without using Vue’s <transition> for them), you often don’t need any JS to animate your content beautifully. If you do need JS animations, there are many other solutions that are more lightweight than jQuery for that.

And concerning AJAX, we now have more modern solutions like axios, which support great features like cancellation and are very lightweight at the same time. So especially if all you need from jQuery is AJAX, you probably should look at something like axios to improve the filesize of your bundle.

But what about plugins? Well, jQuery obviously still has the biggest plugin ecosystem around, simply because it’s been around much longer and was (and is) extremely popular. So if you find that you want or have to use a jQuery plugin that you can’t find a good Vue plugin for, there’s nothing wrong with using jQuery and its plugins to achieve what you want.

That being said, many functionalities that you might want to use a jQuery plugin for are pretty trivial to implement in Vue (tabs, modals and the like for example), so it might be worth just trying out if you can recreate the functionality you want in Vue - you might be surprised how quickly you can do that in many cases.

For an exmaple of how to interate a jquery plugin with Vue, and what to look out for, tke a look at this article: https://vuejsdevelopers.com/2017/05/20/vue-js-safely-jquery-plugin/

Reply to this…

Share your programming knowledge and learn from the best developers on Hashnode

Get started

I have no question, but I use Vue on a daily basis and I just want to thank you all

Awesome!

Reply to this…

Will Vue.js utilize web component APIs in the future?

This is not something we plan to support in the core in the short term, since it will take a while for full support in all browsers / old IE’s fading out.

Once we see adoption and support mature, we will surely revisit this question, but it’s not a priority for now.

But in the meantime there’s a really good package by a guy named Karol that allows you to wrap your Vue components in a Web components wrapper, so you can use Vue components as web components today very easily.

You can find it here: https://github.com/karol-f/vue-custom-element

Reply to this…

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?

Vue 3.0 will use the Proxy API to power its reactivity system. It will improve its performance and remove all the reactivity system limitations.

For example, you will be able to do this.myArray[1] = 'new_value' and Vue will detect this change and update your components automatically. Adding entirely new properties will work too. As a result, Vue.set will be deprecated.

It will also allow performance improvements for large arrays, and lazy reactivity conversion will make using big datasets faster.

Currently, we foresee one possible breaking change: Vue will use Proxies for the values accessed on the component instance, so equality checks with the original values will fail.

Reply to this…

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.

Looking at the success of our project so far, I think it’s obvious that a lot of people value it for what is is and does, so credit isn’t much of an issue in my eyes.

Sure, you often find people on twitter who might say something that’s incorrect, wether it’s out of ignorance, misunderstanding or similar circumstances (don’t like templates? look, we have JSX, too!) - but those voices aren’t very loud in my perimeter.

What I find much harder is to disappoint the people who love Vue when they come up with an idea for it that they see as a great addition or new feature, and we have to tell them that their idea won’t make it into core (or one of our official support libraries).

As a maintainer of a popular project such as Vue, you get flooded with feature requests, both small and big, often great, sometimes silly, often useful, but also often not useful enough to a large enough percentage of the user base to justify the increase in file size and the additional code we then have to test and maintain. We do receive a lot of great suggestions and PRs, and we also accept/merge a lot of them, but many others, we don’t.

And it’s just hard to tell someone that their idea won’t make it, even though we can relate and understand that this idea is very useful to that person. We have to prioritize, and that often means to say “no” to things people want.

Luckily, in most cases people are understanding and can accept that their need isn’t enough for feature X, so bad feelings or expressions of false entitlement, anger or similar negative reactions are rare.

Reply to this…

Load more responses