Learning Decision-Making from the Vue.js GitHub
Vue.js has continued to evolve for over a decade. Behind that evolution lie countless discussions in Issues, Pull Requests, and RFCs.
In this session, we'll use AI to comprehensively organize roughly a decade's worth of Issues, PRs, and RFCs accumulated in vuejs/vue, vuejs/core, and vuejs/rfcs, in order to understand what challenges Vue.js has faced and what decisions it has made along the way.
In this session, I'll be reading through the public records left on GitHub not as a committer, but simply as a Vue user. By tracing discussions that you can't see from release notes or official documentation alone, I aim to understand "why" features like the Composition API and <script setup> ended up taking the shape they did.
What I want to introduce in this session isn't the history of Vue.js itself. It's a new way of learning — learning about OSS design and decision-making by reading through the discussions left on GitHub.
Now that AI lets us work with massive volumes of development history, I believe OSS can be leveraged not just as something to "use," but as something to "learn from."
I hope that those who want to understand Vue.js more deeply, and those who want to learn about design and decision-making from OSS, will walk away with a new perspective.
Yuto NAGAI
Learning Decision-Making from the Vue.js GitHub
Vue.js has continued to evolve for over a decade. Behind that evolution lie countless discussions in Issues, Pull Requests, and RFCs.
In this session, we'll use AI to comprehensively organize roughly a decade's worth of Issues, PRs, and RFCs accumulated in vuejs/vue, vuejs/core, and vuejs/rfcs, in order to understand what challenges Vue.js has faced and what decisions it has made along the way.
In this session, I'll be reading through the public records left on GitHub not as a committer, but simply as a Vue user. By tracing discussions that you can't see from release notes or official documentation alone, I aim to understand "why" features like the Composition API and <script setup> ended up taking the shape they did.
What I want to introduce in this session isn't the history of Vue.js itself. It's a new way of learning — learning about OSS design and decision-making by reading through the discussions left on GitHub.
Now that AI lets us work with massive volumes of development history, I believe OSS can be leveraged not just as something to "use," but as something to "learn from."
I hope that those who want to understand Vue.js more deeply, and those who want to learn about design and decision-making from OSS, will walk away with a new perspective.