| • Ramya Rao's background and work at Microsoft, including her role in VS Code
|
| • How Ramya came to be involved with Go, specifically building the Go extension for VS Code
|
| • The architecture of VS Code, built on Electron and using Monaco Editor
|
| • Performance issues with other code editors built on Electron, such as Atom
|
| • Ramya's opinions on the performance of VS Code compared to other editors
|
| • Discussion of various editors (VS Code, Vim, Gogland) and their features
|
| • Users share their experiences with different editors and plugins (Vim plugin for VS Code)
|
| • Performance issues with some editors and the importance of a good extensibility model
|
| • Separate processes for extensions in VS Code to prevent performance impact on main editor experience
|
| • Troubleshooting issues with Vim plugin, including problems with switching between modes
|
| • General discussion of keyboard shortcuts and keymaps for different editors
|
| • Discussion of using VS Code extensions for other editors (e.g. Sublime, Atom)
|
| • Introduction to CodeLens capability in VS Code
|
| • Explanation of new features and contributions to Go extension (e.g. stubs, extract method)
|
| • Discussion of open issues and seeking help from contributors
|
| • Overview of writing code for VS Code extensions (using TypeScript or JavaScript) and Language Service protocol
|
| • Conversation about prioritizing features and user feedback
|
| • Ramya Rao's process for deciding which feature requests to implement in the Go extension
|
| • The importance of community feedback and upvotes in determining priority
|
| • Implementing features in response to changes in the core VS Code product
|
| • Managing technical debt by staying up-to-date with new features and APIs
|
| • Using snippets in the Go extension, including typing prefixes or using the command palette
|
| • Customizing snippet settings and mapping keyboard shortcuts
|
| • Ramya Rao's experience with her first open source project, including the challenges of triaging and keeping up with language changes
|
| • The importance of pacing oneself and releasing updates at a sustainable cadence
|
| • The difference between developing for an employer versus an open source project, where thousands of people have different priorities and expectations
|
| • Appreciation from strangers and users, which can be fulfilling in open source projects
|
| • New projects and tools mentioned, including Gonvim (a GUI frontend for nvim written in Go) and Draft (for determining application type and automatically generating Docker files and Kubernetes specs)
|
| • The VS Code Docker extension and its features
|
| • Open source philosophy of pulling request instead of creating an issue
|
| • The speakers discuss their struggles to keep up with the vast amount of conference videos available.
|
| • GopherCon is mentioned as an upcoming event in June, with the CFP for lightning talks currently open.
|
| • Ramya Rao announces her attendance at GopherCon and expresses interest in having a booth or meeting space.
|
| • Erik St. Martin teases some upcoming surprises for GopherCon, hinting at exciting developments behind the scenes.
|
| • High-Performance Go talk from FOSDEM is mentioned as an interesting video to watch.
|
| • The speakers discuss their favorite ways to consume conference content, including Just For Func videos and other online series.
|
| • DevOps Day is mentioned briefly.
|
| • Kelsey Hightower's talk at DevOps Days Austin and its emphasis on vulnerability and openness in sharing personal struggles
|
| • The importance of humanizing people in tech, particularly those who are often marginalized or underestimated
|
| • Ramya Rao's introduction to open source through VS Code and Go
|
| • Edward Muller's mention of Vim and VS Code being top two editors used by Go writers
|
| • Shoutouts to Kelsey Hightower for his talk and Jaana B. Dogan (JBD) for her work on performance improvements in Go and contributions to the Devex group
|
| • Discussion of #FreeSoftwareFriday, where the hosts recognize people or projects that make their lives easier in the open source world
|
| • Ramya Rao discusses her use of the `q` library for debugging in Go code.
|
| • Ramya gives shoutouts to contributors and developers who have helped with the Go extension.
|
| • Erik St. Martin gives a shoutout to Microsoft's contributions to the Go plugin and VS Code.
|
| • Johnny Boursiquot agrees with Erik and thanks Ramya for her work on the plugin.
|
| • The panel discusses and thanks various contributors, including those from Microsoft, before wrapping up the show. |
