Datasets:
text stringlengths 0 1.49k |
|---|
• 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. |
**Erik St. Martin:** Welcome back everybody for another episode of GoTime. Today's episode is number 49, and today's sponsor is Toptal. |
Today on the show we have myself, Erik St. Martin, we also have Carlisia Pinto - say hi, Carlisia... |
**Carlisia Thompson:** Hello, everybody. |
**Erik St. Martin:** And Brian Ketelsen couldn't be here, but we are fortunate to have Johnny Boursiquot join us today. |
**Johnny Boursiquot:** Good to be back! |
**Erik St. Martin:** And our special guest for today, for all the [VS Code](https://code.visualstudio.com/) lovers out there, is actually the author/maintainer of VS Code. [Ramya](https://twitter.com/ramyanexus), welcome to the show. |
**Ramya Rao:** Hey, everyone. Good to be here! |
**Erik St. Martin:** So do you wanna maybe give everybody a little bit of a background of who you are and what you're working on? You actually work for Microsoft as well... |
**Ramya Rao:** Yes. Like you already said, my name is Ramya... I joined Microsoft straight out of college about nine years ago in India. Four years later I moved to the U.S. here in Seattle. Ever since I've been in this group called Developer Division - we call it DevDiv. It's all about developers, developer tools, all... |
You finally get to be in a place where the product you make is useable by you. You are your own customer, and that's a different high altogether. |
I've been in a couple of teams of in DevDiv. The first one was about developer content services; you know how you have MSDN, you have TechNet... Microsoft is a big company, so almost every team had their own thing going when it comes to trying to do content. We tried to consolidate everything, bring everyone up to spee... |
So I did that for a while, then I joined VSTS (Visual Studio Team Services). That's like a collection of services needed for your application lifecycle management (ALM). So you have source control, you have \[unintelligible 00:02:52.22\] issue tracking, you have build for your continuous integration, you have release f... |
If you think of the old-school Team Foundation Server (TFS), which used to be an on-prem product, VSTS is like a online offering of the same, but so much more. So I did that, and then I heard VS Code was spawning a team here in Redmond. Until then, VS Code was a team of about ten people in Zurich, headed by Erich Gamma... |
**Erik St. Martin:** Were you using Go prior to starting on this plugin, or was this kind of like your intro to Go? |
**Ramya Rao:** I hadn't even heard of Go, to be honest, before that. What happened was I joined the team, and right about two months before I joined the team, the person who wrote the Go extension had left the company... That's Luke Hoban, for everyone... A big shoutout for starting this whole amazing tool. |
\[04:07\] So they decided, "Hey, let's give that thing to the new girl." \[laughter\] So there I was, new to VS Code, new to the VS Code extension story, new to Go, and I was the only maintainer/contributor for a while there. So yeah, that's how I came into Go. |
**Erik St. Martin:** So do you like and love Go now? Do you use it for other things, now that you kind of were forced by way of building this extension? |
**Ramya Rao:** I don't use it much in the day-to-day job because we don't get to use it in the product; VS Code doesn't use Go. But once in a while I try to write small programs and learn more about it. |
**Erik St. Martin:** That's really cool. So VS Code - I think that's built on [Electron](https://en.wikipedia.org/wiki/Electron_(software_framework) ), isn't it? |
**Ramya Rao:** VS Code is built on Electron, yes. The way it started was initially about five years ago Erich and a few others were thinking about "Hey, let's look into having a developer experience, a coding experience in the browser, if we can do it, using web technologies", and that's how the [Monaco Editor](https:/... |
It was used in, say, the Azure portal for your \[unintelligible 00:05:20.20\] Azure websites online; Electron was used in IE11 in the debugging support - what you see there is Monaco. Then VSTS itself uses it, so you can edit code online - that's Monaco. And then I think right about that time Electron was gaining tract... |
That solves our cross-platform problem, and lets you write this amazing product using just web technologies. I love that one thing about Electron - you no longer have to write desktop applications, which is cross-platform; you no longer need to know the native technologies anymore. You know web tech, and that's all you... |
**Carlisia Thompson:** We heard that some other code editors have an issue of performance and that it is due to - what's the name again? Electron. But VS Code does not seem to have the same performance issues. Did you tweak something to make it the Electron performance issues go away, or what we heard is not accurate a... |
**Erik St. Martin:** Well, I think the differentiator is the editor that's written on top of Electron - I believe they're two separate editors, both written on Electron. |
**Ramya Rao:** I think you're referring to [Atom](https://atom.io/)... |
**Carlisia Thompson:** We didn't say that, you did. \[laughter\] |
End of preview. Expand in Data Studio
2017 Go Time Transcripts
Complete transcripts from the 2017 episodes of the Go Time podcast.
Generated from this GitHub repository.
- Downloads last month
- 137