text stringlengths 0 1.49k |
|---|
**Erik St. Martin:** I'm getting there, I'm getting there. |
**Brian Ketelsen:** Okay. |
**Erik St. Martin:** Alright, thank you everybody for coming on the show. Definitely thank you Carolyne for coming on and joining us, and anybody who's hiring - you can't go wrong hiring Carolyn. |
**Brian Ketelsen:** Yeah, seriously... Get on it! |
**Carolyn Van Slyck:** Yeah, hit me up on Slack. |
**Erik St. Martin:** We'll put your contact info in the show notes. |
**Brian Ketelsen:** Show her cell phone number... \[laughter\] |
**Erik St. Martin:** Address, social security number - all the good stuff. So if you enjoyed the show, definitely share the show with colleagues, friends, anybody who would find it interesting. You can find us at GoTime.fm. We are on [Twitter](https://twitter.com/GoTimeFM). If you wanna be on the show, have suggestions... |
**Brian Ketelsen:** Goodbye! Thanks, Carolyn. |
**Carlisia Thompson:** Yes, thank you. |
**Carolyn Van Slyck:** Bye! It was great talking to you. |
• Sam Boyer's background as a Go programmer and his experience with package management |
• The problem of package management in Go and the complexity of the issue |
• The creation of GPS (Go Packaging Solver) library by Sam Boyer to address the issue |
• The development of the dep tool using GPS and its integration into the Go toolchain |
• The goal of obviating the need for multiple tools and providing a single solution for package management in Go |
• The representation from various tools on the committee developing the dep tool, aiming to solve all use cases |
• The motivation behind creating a library like GPS instead of another standard canonical tool |
• Approaching dependency management with multiple tools |
• Current limitations and future plans for dep |
• GPS (Go Package Specification) design choices and features |
• Converting existing tools to use GPS metadata |
• Trade-offs of incorporating on-the-fly conversion support in dep |
• Importance of using semver and tagging releases |
• Encouraging community adoption of standard practices through tooling and education |
• Discussion of the `release` command in GPS and its potential future functionality |
• Mention of UpSpin as a distributed storage system for tracking releases |
• Comparison to other package managers (npm, Crates, etc.) and their central registries |
• Trade-offs between decentralized systems like IPFS and the need for seeders |
• Introduction of dep tool as a reference implementation for GPS |
• Explanation of dep's unique feature: static analysis and constraint-solving for dependencies |
• Discussion of the importance of distributing dependency versioning decisions across the ecosystem |
• Discussion on the importance of community momentum and consensus for adopting a versioning standard in Go |
• Need for a tool that works well with semver to encourage adoption of tagging releases |
• Hypothetical use of a platform at GopherCon to promote change |
• Vendor directory structure and its potential replacement by an alternative implementation |
• Concerns about code generation and volatility of vendor directories |
• Roadmap for stabilizing the dep tool and merging it into the Go toolchain, with a goal of inclusion in Go 1.10 |
• Upcoming release of GoDep |
• Roadmap and project management |
• Getting involved with GoDep and contributing to its development |
• Plans for stabilizing manifest and mod files |
• Future vision for the dep tool and its integration with Go toolchain |
• Community adoption and agreement on dependency management tools |
• Go 1.8 release and its impact on performance |
• SSA (Static Single Assignment) optimizations in Go 1.8 |
• Bug fixes in Go 1.8, including ordering issues with dependencies |
• Upcoming Go 1.9 features, including interface optimization changes |
• New tools for HTTP manipulation and testing |
• Sourcegraph's code intelligence implementation and its benefits |
• Distributed storage and networking tools, including Rook and Meshbird |
• Discussion of Hamachi VPN |
• Fuzzing as a test and benchmark tool |
• Integration of fuzzing into the Go testing framework |
• American Fuzzy Lop (AFL) fuzzer |
• Static analysis tools in Go |
• Dependency management in Go |
• #FreeSoftwareFriday segment |
• Discussion about Node installation on Erik's machine |
• Introduction to gcli, a CLI generator tool written in Go |
• Overview of code generators and their benefits |
• Shoutouts to authors and contributors who write documentation for open source projects |
• Discussion about Helm, a project that creates guided installations for well-known applications on Kubernetes clusters |
• Mention of KubeApps, a platform for searching and installing Helm charts |
• Episode sponsors: Toptal and Compose |
• Importance of sharing the show with others |
• Links to social media platforms (Twitter, GitHub) |
• Invitation to participate in future episodes or suggest guests/questions |
**Erik St. Martin:** Welcome back everybody to another episode of GoTime. Today's episode is number 36, and today's show is sponsored by Toptal and Compose. |
On the show today we have myself, Erik St. Martin, Brian Ketelsen is also here... |
**Brian Ketelsen:** Hello! |
**Erik St. Martin:** And Carlisia Pinto... |
**Carlisia Thompson:** Hi, everybody. |
**Erik St. Martin:** And our special guest today, bringing some well-needed love and knowledge to the dependency world in Go is Sam Boyer. How are you, Sam? |
**Sam Boyer:** Hello, hello! I'm great, how are you? |
**Erik St. Martin:** Good, good. Do you wanna give everybody a little bit of a background of who you are, what you are working on? We'll kind of kick things off there. |
**Sam Boyer:** Sure. I'm a Go programmer, believe it or not... |
**Brian Ketelsen:** What?! |
**Sam Boyer:** It's crazy, I know. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.