VueConf US 2018


1. State of Vue

Evan You

2. How We Do Vue At GitLab

Jacob Schatz

3. Vue in Motion

Rachel Nabors

4. Testing Vue apps

Edd Yerburgh

5. Serverless Functions and Vue.js

Sarah Drasner

6. vue-rx

John Lindquist

7. Create an Engaging Native Mobile App with Vue and NativeScript

Jen Looper

8. 7 secret patterns Vue consultants don't want you to know

Chris Fritz

9. Agile Design Systems in Vue

Miriam Suzanne

10. Vue & TypeScript: Up and Running

Daniel Rosenwasser

11. A React Point of Vue

Divya Sasidharan

12. Vue & SSR: The best practices

Sebastien Chopin

13. A Short Synopsis of Vue Storybook

Peter Finn

14. Prototyping with Vue Single File Component

Pine Wu

15. 5 Libraries You Should Know About

Adam Jahr

16. Update an Existing Application to Vue

Michael Bennett

17. Vue and Vuex for Complex Application State

Patrick Seda

18. Top 5 Must-Have UI Animation Patterns

Rachel Nabors

19. The Dream: A Full Rewrite

Seth White

20. Start Your Own Vue.js Meetup

Ben Hong

21. Reusability - Is It Worth It?

Shelton Clinard

22. Reactivity - Learning by Accident

Jeff Schenck

23. Quick Publishing of Redistributable SFC on NPM

Mike Dodge

24. OverVue of Vuetify.js


25. Ionic and Vue

Mike Hartington

26. Dynamic Store Modules with Vuex

Adam Bradford

27. Build a MiniFlix Clone with Vue Contest

Dan Zeitman

28. Beyond HTML with Vue

Eduardo San Martin Morote

29. Vue with AWS Lambda

Matt Biilmann

30. 40 Hour Plan For UX Proficiency

Jacob Covey

31. Code Splitting Patterns with Vue

Sean Thomas Larkin
Notify me when new talks are available.

How We Do Vue At GitLab

How We Do Vue At GitLab

Jacob Schatz

Jacob Schatz is a staff developer at Gitlab. In his talk he describes how and why Gitlab chose Vue and what their experience with it has been.

What they needed

Jacob describes how, when moving away from writing things with Rails, Gitlab needed the following things from a front end framework:

  • Easy to contribute to (since Gitlab is open source)
  • Fast to learn
  • Concepts work on their own
  • Not a gargantuan framework

Why Vue?

He says while there are probably no “wrong answers” in choosing a framework, Vue was the best choice for them because it had the smallest learning curve and was “drop-in”, meaning it didn’t initially require npm or Webpack, but it could still scale along with them.

He found that Vue had a small learning curve and devs could be productive immediately. Also, it is both opinionated and not opinionated. Meaning it provides a whole ecosystem with options for routing and state management, which you can choose or not, and Vue will work well either way.

Gitlab’s baggage

Jacob describes how Gitlab had “baggage” from their prior tech stack, which included JQuery and CoffeeScript. One of their first steps was to remove CoffeeScript, which they compiled to ES5 then rewrote in ES6.

Instead of rewriting everything, they did progressive enhancement, delivering new code in parallel with the new features. Vue allowed them to start simply and get complex later, starting with Vue in .js files, then moving on to .vue files. Once they added Vue loader and .vue files, their performance drastically improved.


Jacob says their lives became easier as they transitioned to Vue, with less bugs due to having less code. Their code was also a lot more reusable, and their event management became easier. Previously, they were using TurboLink, which when written poorly can remove JavaScript events. Vue took care of their events for them.

As their developers starting all writing in .vue files, they needed more consistency in how they were doing things. Implementing Vuex solved a lot of their issues regarding consistency.

Because of the virtual DOM, Vue was automatically taking care of a lot of considerations that they would have had to do manually with JQuery. As a result, they were experiencing a lot faster render times.

Looking back on the journey

  • Started with jQuery, CoffeeScript and inline scripts
  • Ended with Vue, webpack, Vue Loader and Vuex

In other words, Jacob says Gitlab started with a lengthy, annoying development experience and has evolved toward a quicker, more pleasant development experience.

Gitlab even created their own docs on how they use Vue. Check them out.