Popular posts

The main idea behind the next version of Vue is to refine and improve its API and internals, and it won't be a very different release (unlike 1.0 vs. 2.0).

Vue 3.0 will drop support for older browsers in order to take advantage of new web APIs like Proxy to 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. Also, your data will be tracked lazily so Vue will be faster with large datasets.

The upgrade to v3.0 should be quite easy since most of the API won't change. The only thing to consider is it will only support "evergreen" browsers (including MS Edge) which means it will not work on Internet Explorer. But don't worry in case you target older browsers, both Vue 2.0 and Vue 3.0 will evolve with the same features and be maintained in parallel until those browsers aren't used anymore.

Vue 3 is not going to be one of those "big change releases" - the main difference will be that Vue 3 only targets modern "evergreen" browsers (i.e. IE11 & below are out).

Resetting the browser support baseline gives the opportunity to:

• Rewrite the reactivity system using ES2015 Proxies. This will get rid of almost all of the existing gotchas/compromises in the current reactivity system, and has potential to improve performance as well.

• We can drop all the code dealing with compatibility issues and esoteric bugs in older browsers. This should shed some good amount of weight from the lib size.

This is really the main point - we strive to keep the public API close to 100% compatible, and v2/v3 will be maintained in parallel with feature parity until the older browsers completely phase out.

I still use version 2 and works great, for example on Tempmailo.