text stringlengths 0 1.49k |
|---|
**Travis Jeffery:** Oh, Java... |
**Brian Ketelsen:** So we started this discussion, and lots of people are jumping in on it, but we'll have to see where it goes. There's lots of people that are inside Google that are interested in this too, so I'm hoping we'll get some traction and have some convergence on a minimal interface that will make most peopl... |
**Erik St. Martin:** I think it's another one of those dependency-type things too, where there's a disadvantage when some things are steered from kind of like a benevolent dictator. There's a lot of good that comes from it, but the bad part is the tunnel vision. The logging - who knows what they use internally for logg... |
At Google's scale, logs probably don't mean much; it's probably all metrics at that point, and anomaly detection and things like that. Logs are probably things that are turned on during debug phases, and that's about it... Because I don't think I would wanna know how much log data Google sites generate. Enough to knock... |
**Brian Ketelsen:** Yeah. The nice thing about this conversation is that the folks at Google are even discussing potential compiler changes that would make certain operations in the logging world less costly in terms of allocations and such. |
**Erik St. Martin:** Nice. |
**Brian Ketelsen:** ...so there's definitely some good engagement on this to make logging fast and pain-free. I'm excited to see it go somewhere. |
**Erik St. Martin:** I don't think people realize how engaged the Go team is with the community too on a lot of things; they help big users of Go and stuff like that in making changes that help their software run better. |
**Travis Jeffery:** One of the coolest things was whenever they had a discussion about Go dependencies and they brought in guys that were working on Go Vendor and godeps and everything and brought them in as people to talk with - that was really cool to see. |
**Erik St. Martin:** Yeah, definitely. So I think we are 15-ish minutes over time, somewhere in that neighborhood, so we should probably close out the show, before we drive Adam crazy, sitting there waiting for us. |
**Brian Ketelsen:** We covered all the corners of the internet today though, it was kind of awesome. |
**Erik St. Martin:** If we all close Slack and don't look to see if he messages and we just keep going, how long do you think he hangs up on us? \[laughter\] |
**Brian Ketelsen:** It's because we can't see him saying, "Cut! Cut! Cut! We're long, we're over!" "Oh, sorry, I couldn't see it. It's radio." \[laughter\] |
**Erik St. Martin:** Alright, so with that, I wanna thank everybody for being on the show, especially to you, Travis, and Carlisia, who's not here with us - she already said her goodbyes. |
Thanks to all the listeners who are listening live and everybody who's going to be listening to this how when the recording is released. Huge shoutout to our sponsors, StackImpact and Backtrace. |
If you are not following us already, we are GoTime.fm, you can sign up; eventually, we'll get around to putting out our weekly email. We are @GoTimeFM on Twitter, and if you wanna be on the show, have suggestions for topics or guests for the show, github.com/GoTimeFM/ping. With that, goodbye everybody! We'll see you ne... |
**Brian Ketelsen:** Bye! Thanks, Travis. |
**Travis Jeffery:** Thanks for having me. |
• Go's growth and specialization within Google |
• Internal vs external community work on Go |
• Brad Fitzpatrick's role as public face of open source Go |
• Process for contributing to Go project |
• Upcoming changes to contribute process (pull requests, etc.) |
• Codenames for Go releases ( proposal from Brian Ketelsen) |
• Discussion about adding GoTime to the website |
• CL (change list) 41146 and its approval process |
• Proposing changes to the standard library, including requirements for proposals and submitting code without a strong use case |
• Adding code to GitHub instead of the standard library for flexibility |
• Domain name registration and management, including tips for purchasing domains |
• Discussion about the Go 1.9 release and plans to get the community more involved in bug triage and code review |
• Gardening tasks and triaging bugs |
• Organizing a shared presentation for meetups on contributing to projects |
• Exploring the concept of "Bugmash" or collaborative bug-fixing events |
• Improving the contributing process and documentation for Go project contributors |
• Using tooling to accept GitHub pull requests and convert them into Gerrit changes |
• Discussion about the _Help Wanted_ tag in GitHub for Go and its limitations |
• Challenges of labeling issues as "beginner-friendly" due to varying difficulty levels |
• Alternative approaches to labeling, such as bite-sized tasks or time-chunks |
• Brad Fitzpatrick's hobby project involving home automation and motion detection using Go |
• Use of OpenCV and FFMPEG in the project |
• Generating GIFs from video footage and sending them via Telegram |
• Ideas for improving the project, including object recognition with Google Vision API |
• Sony MiniDiscs with unknown music content |
• Difficulty accessing old floppy disks and digital storage devices |
• Nostalgia for early computing experiences, including dial-up internet and cassette tapes |
• Discussion of the TV show "Halt and Catch Fire" and its portrayal of the 1970s and 1980s computer industry |
• Mention of the HBO series "Silicon Valley" |
• Introduction to Camlistore (Perkeep) as a personal storage system and its development in Go programming language |
• Brad Fitzpatrick discusses his past involvement with Camlistore and his current role in reviewing contributions from another developer |
• The development of Camlistore's LetsEncrypt integration is explained, including its impact on ease of use and security |
• Brad mentions the potential for subdomain rate limiting issues with LetsEncrypt and plans to address this issue |
• Go team burnout and frustration with repetitive tasks are discussed, as well as motivations for a potential Go 2.0 release |
• The idea of goroutines being Go's unique feature is expressed, and concerns about other languages copying them are mentioned |
• Brad mentions Crystal language, a Ruby-like language that has adopted goroutines and channels, but notes it still needs work on its standard library |
• Discussion about language features and how they compare to Go |
• Goroutines and channels as a key aspect of Go's design |
• Other languages experimenting with lightweight tasks or goroutines, but struggling to implement them effectively |
• Crystal language's attempt to incorporate Go-like features, but ultimately falling short |
• The importance of code readability in Go and its impact on productivity |
• Why people might be hesitant to try Go due to its perceived complexity |
• Projects attempting to create runtime environments for other languages (e.g. Python in Go) |
• Prospects for adding Generics to the Go language |
• Ian Lance Taylor's efforts to design a proposal for Generics, and potential plans for a Go 2 release |
• periph.io as an alternative to Gobot for GPIO and I2C/SPI |
• Dave Brophy's code generation tool at github.com/dave/jennifer |
• React bindings for GopherJS at github.com/myitcv/react with Preact support |
• Discussion on removing items from the Go standard library, including HTTP |
• Potential changes to the Go language around the 10-year mark |
• The Go team's decision to include HTTP in the standard library and its implications |
• Debate over what should be included in the standard library and how it affects usability and adoption |
• Discussion of promoting external libraries versus maintaining internal ones |
• Concerns about maintenance, fragmentation, and the need for better package discovery tools |
• Ideas for analyzing and optimizing the Go ecosystem, such as using GitHub data and machine learning |
• Proposal to make bigints automatic and efficient |
• Removing `new` keyword from Go language |
• Simplifying declaration of slices and arrays |
• Getting rid of naked return statements |
• Changing string and byte slice handling in Go to reduce confusion and overhead |
• Introducing a "view of memory" type to accept both strings and byte slices, with read-only access. |
• Free Software Friday segment on the podcast |
• Shoutouts to open-source projects: Changelog website and GoTime website's search feature, Buffalo for web development in Go, GopherCon and GopherAcademy websites |
• Discussion of production use cases for Buffalo in Go |
• Mention of previous production environments used on the show (Caddy, Hugo) |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.