JSFoo: VueDay 2019

A day spent discussing Vue.js, developments in the Vue ecosystem and component architecture

Tickets

Future of Vue

Submitted by Rahul Kadyan (@znck) via Zainab Bawa (@zainabbawa) on Tuesday, 6 August 2019

Section: Full talk (40 mins) Technical level: Intermediate

View proposal in schedule

Abstract

On 1st October 2016, we released Vue 2.0. Three years have passed since. The frontend ecosystem, especially JavaScript standards and browsers, have come far. New APIs – e.g., Proxies – are available on most browsers. This has presented us an opportunity to address the caveats in Vue’s reactivity system. We are using this opportunity to address the smaller but important issues in the ecosystem. A cherry on top, significant performance enhancements for Vue 3.

Outline

In this talk, I will discuss:

  • What is in the new version i.e., Vue 3.
  • Backward compatibility.
  • Performance enhancements.
  • Reactivity caveats.
  • How to get involved with Vue 3?

Requirements

None

Speaker bio

Rahul Kadyan is Vue Core Team Member, and senior software engineer at Myntra. https://www.linkedin.com/in/rahulkadyan/

Slides

https://speakerdeck.com/znck/future-of-vue-jsfoo-vueday-2019

Comments

  • Abhishek Balaji (@booleanbalaji) Reviewer a month ago

    Hi Rahul,

    Thanks for taking the time out to do the reherasal. Here’s the feedback from the call:

    • Time taken: 30 mins with scope for 5 mins more
    • Try listing a summary of the change log showing the journey of how Vue progressed. Also explore is fits in the scheme of the talk.
    • Structure of the talk was good, along with content.
    • Add more context around the rendering logic and how that would work
    • As a Vue practitioner, could not connect to some parts, especially when showing the compiler output
    • Explain the section on monomorphic lens more
    • Around slide 48, try tweaking the explanation, since it’s not quite clear.

    Please add a link to the updated slides by Monday, so we can do a final round of review.

Login with Twitter or Google to leave a comment