Datasets:
willtheorangeguy
/
2016-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.82k
**Erik St. Martin:** Yeah, I'm terrible about that. And I think that's it. Twitter: @GoTimeFm on Twitter, as well. With that said, goodbye everybody.
**Brian Ketelsen:** Thanks for being on, Scott.
**Scott Mansfield:** Sure thing.
**Carlisia Thompson:** This was fun, thanks Scott.
• Discussion of a survey on Go usage and dependency management
• Ed Muller's role in creating the survey and his observations on the responses so far (2,400+)
• Comparison and ranking of various Go dependency managers (Godep, Govendor, GB, Glide)
• Historical context for Godep's dominance in dependency management
• The challenges of solving the problem of vendor directories and metadata standards
• The Go Team's approach to dependency management and their desire for community input and solutions
• The Go community is frustrated with the lack of a standardized solution for dependency management and repeatable builds.
• Some newer programming languages (e.g. Nim, Rust, Crystal) have built-in solutions to these problems that are considered more effective than what Go has to offer.
• The Go Team's stance on this issue is that it's not their responsibility to solve it, but rather the community's.
• Ed Muller suggests that instead of creating new tools for dependency management, people should read existing codebases, submit PRs, and fix problems.
• Some of the issues that still need to be figured out include actual upgrade and version management of dependencies, specifying constraints on versions for libraries, and implementing semantic versioning.
• Semantic versioning issues in Go libraries and lack of adoption
• Difficulty in tracking changes to dependencies due to missing or inconsistent version tags
• Social contract of semantic versioning vs. technical implementation
• Importance of tools for checking API compatibility and detecting breaking changes
• Comparison with other languages that have addressed dependency management from the start
• Go's support on Heroku, including formal support for Go applications and documentation in dev center
• Growth of Go adoption on Heroku, particularly among API service developers
• Heroku customers are increasingly using Go in conjunction with other languages
• Large portions of the Heroku platform have been rewritten in Go, including Git server, log router, private spaces, API work, and system metrics
• Ed Muller estimates that 60-40% of the rewritten code is new development vs. rewriting existing code
• Doozer, a distributed coordination system written in Go, was used by Adobe and Bit.ly among others but is no longer widely used
• The Paxos implementation in Doozer was done by Blake Mizerany and Keith Rarick
• Discussion about a legacy Go project from 2011-2012 and its idiomatic code
• Heroku CLI tool is now 98% Node, with some remaining Go and Ruby code being phased out
• Damian's contributions to the Go community, including answering questions on Reddit and GoTime FM
• SourceGraph Editor plugin for Vim/Sublime/Atom, which provides real-time code analysis and examples
• Discussion about SourceGraph company and its open-source projects
• Cross-platform GUI type approaches in Go
• Gob project for writing a full web browser in Go
• CEF (Chrome Embedded Framework) as an alternative
• Shiny library used by Gob for UI components
• Gogs self-hosted Git service and its documentation
• Heroku's open source Go projects
• go get button Chrome extension for easy package management
• Pachyderm project for data science with Go
• Discussion about a tool that allows data pipelines to be piped through containers
• Mention of Visual Studio Code as an editor for Go development with praise for its features and tight integration with Delve debugger
• Shoutout to Luke Hoban and the Microsoft team for creating the Visual Studio Code plugin
• Comparison between Vim Go and Visual Studio Code, noting that VS Code is "significantly prettier"
• Mention of Go Doc Tool (also known as Pythia) which jumps to code source definition
• Discussion about Apache Kafka as a distributed message queue and publish-subscribe system
• Heroku's support for the Go world and their contributions to open-source projects
• Upcoming events, including the Women Who Go first birthday party in San Francisco and the next episode of GoTime FM with Jessie Frazelle and Beyang Liu
• Discussion of the podcast format and interaction with listeners
• Expression of gratitude to guest speaker Ed Muller for appearing on the show
• Wrap-up and goodbyes from all participants
**Erik St. Martin:** Alright everybody... \[laughter\] I'm still laughing. \[laughs\] I actually had to pull away from the mic on that one. Alright, welcome back, it's episode ten. As always on the call myself, Erik St. Martin, we have Brian Ketelsen...
**Brian Ketelsen:** Hello!
**Erik St. Martin:** ... and Carlisia Campos.
**Carlisia Thompson:** Glad to be here.
**Erik St. Martin:** ... and today with us we have a special guest, Ed Muller from Heroku, who will be talking about all things Go at Heroku and some dependency management and any other random topics we decide to come up with. How are you doing, Ed?
**Ed Muller:** Howdy!
**Erik St. Martin:** Thanks for coming on, it's kind of exciting.
**Ed Muller:** Thanks for having me.
**Erik St. Martin:** What I want to talk about first is you recently sent out a survey - which I hope everybody's taken - getting information about people's Go usage. Do you wanna talk to us a little bit about that and the purpose you're looking for from that? And hopefully we can get more people to take it.
**Ed Muller:** Yeah, so I started asking people in various Slack channels, "Hey, what can you tell me about Go users in different ways?" and Damian Grisky, the gentleman who does all the Go implementations of all the various different types of algorithms, he had linked me to the State of Rust Survey and said "Something...
**Erik St. Martin:** How were the responses from that, Ben? Have you been getting a lot of feedback from that?
**Ed Muller:** So far there's almost 2,400 responses, but I know there's more than 2,400 Gophers in the world.
**Erik St. Martin:** I'm willing to bet that there probably are.
**Carlisia Thompson:** 2,401, I took it today. \[laughter\]
**Erik St. Martin:** I have to admit, I didn't complete it all the way through. I was really trying to analyze the page where it started asking what would I change, what would I want, and I feel like I've been around too long, I'm too used to it, so I was trying to sit back and think about that constructively, and I ne...
**Ed Muller:** Go back to it, do it again...
**Brian Ketelsen:** I took it and I answered all the questions honestly, and then at the end it said, "And do you want to leave your name?" and I was like, "Oh man, I answered all these questions honestly." Alright, so I figure at GopherCon I'm gonna get a beatdown from somebody.
**Erik St. Martin:** So you put my name instead of yours is what you're saying?
**Brian Ketelsen:** No, I put my real name in, but I did mention that dependency management was a pain point that we need to resolve as a community immediately.
**Ed Muller:** Yeah, we do. So I maintain the Go Buildpack at Heroku and I have the wonderful honor of having to implement all sorts of different detections based on whether people are using things like GB or Glide or Govendor or Godeps, and that also excludes things like GVT and all sorts of other stuff... Where the o...
**Brian Ketelsen:** That's gotta be a lot of fun.
**Carlisia Thompson:** \[03:57\] So what are the dependency packages that you support at Heroku?
**Ed Muller:** The managers that we support are Godep; I'm also the current maintainer of that. Govendor, GB, and - it's not released yet, but if you use the master branch of the Buildpack, Glide support. And I think I've come up with a way to manage our last version, but I need to spend some time and write a bunch of ...