text stringlengths 0 2.35k |
|---|
[3817.00 --> 3818.32] What a great problem. |
[3818.68 --> 3833.76] Um, could you build something that samples running Go code and, you know, periodically at some schedule and, uh, and collects the results up, um, would be extremely useful and really fun probably as well. |
[3833.76 --> 3834.26] Yeah. |
[3834.26 --> 3835.54] It's like a lot of fun ones. |
[3835.54 --> 3841.00] Once you start to see like, for example, a large company, you know, aggregate and all the profile and data. |
[3841.00 --> 3847.82] So you can see like, Oh, the companies, you know, the, for example, you can actually improve your bill on your cloud provider. |
[3847.82 --> 3852.26] Uh, you can say that like a loss of the calls are actually like dependent on this one function. |
[3852.26 --> 3858.58] Um, and you know, if you optimize it, we can actually cut the billing, like by 10% or something, right? |
[3858.58 --> 3863.18] Like it's actually pretty useful once you start to do this systematically everywhere. |
[3863.66 --> 3864.22] Hmm. |
[3864.22 --> 3870.88] Well, I love, I love the message of when wait till you've got something running and then look at optimizing it. |
[3870.94 --> 3877.50] I think in some cases you can shortcut it, but generally speaking, yeah, that advice is sound. |
[3877.50 --> 3889.06] And the idea of being able to profile running production systems and to understand them better, I think is, is, um, a great goal to have. |
[3889.06 --> 3895.94] And what a great use of the, the tools that we, that we have as part of our ecosystem. |
[3897.10 --> 3899.42] Well, on that bombshell, I mean, I think that's it. |
[3899.50 --> 3902.82] I think we've, uh, we've reached the end of the hour. |
[3902.82 --> 3909.16] And so the end of this episode, thank you very much, Johnny and Jana. |
[3909.34 --> 3909.98] It's been awesome. |
[3910.42 --> 3911.68] How have you liked it? |
[3912.00 --> 3918.36] I can talk about this topic for hours and I think, you know, this was awesome, but we should keep, you know, talking about tools, I think. |
[3919.30 --> 3920.06] Yeah, absolutely. |
[3920.20 --> 3930.40] Well, there's a lot, there's lots more to discuss and, um, I might even see if we can bring in some people from the community that have, um, built some of the tools that we're using today. |
[3930.40 --> 3935.66] One, one other little, uh, bit of info that I think is quite interesting. |
[3936.12 --> 3944.02] The only actual contribution I personally made to the Go project was to remove something from GoLint. |
[3944.38 --> 3949.26] So one time GoLint got a bit easier, uh, to satisfy. |
[3949.58 --> 3950.32] Thanks to me. |
[3950.48 --> 3951.18] You're welcome. |
[3952.74 --> 3953.26] Yay. |
[3953.58 --> 3954.02] Yeah. |
[3954.20 --> 3955.80] I, I, I delete code. |
[3956.06 --> 3956.74] I delete code. |
[3956.82 --> 3957.98] I mean, I love it. |
[3958.34 --> 3959.42] Well, yeah, that's it. |
[3959.42 --> 3960.54] Thank you so much. |
[3960.84 --> 3963.78] Um, we'll see you next time on GoTime. |
[3971.42 --> 3974.68] Thanks for listening to this classic episode of GoTime. |
[3975.12 --> 3976.12] Subscribe now. |
[3976.20 --> 3980.16] If you're new, head to GoTime.fm for all the ways. |
[3980.56 --> 3984.80] And long time listeners, do us a solid by sharing the show with your friends. |
[3984.80 --> 3986.84] That's the best way people find us. |
[3987.06 --> 3988.62] In fact, I will cut you a deal. |
[3988.98 --> 3995.14] Email a personal recommendation to three friends and BCC go time at changelog.com. |
[3995.26 --> 3997.50] I'll send you a free pack of changelog stickers. |
[3997.84 --> 3999.00] That's a win, win, win. |
[3999.16 --> 4000.06] With win, win, win. |
[4000.30 --> 4000.92] We all win. |
[4001.00 --> 4004.50] Thanks again to our partners at Fastly for having our CDN covered. |
[4004.66 --> 4006.58] To BMC for these banging beats. |
[4006.94 --> 4007.90] And to you for listening. |
[4008.44 --> 4009.20] We appreciate you. |
[4009.20 --> 4012.48] Next week, we welcome Ronna Steinberg to the show. |
[4012.80 --> 4017.52] She joins Natalie and Ian to discuss object-oriented programming and Go. |
[4018.12 --> 4021.56] That's what you can look forward to next time on GoTime. |
[4021.56 --> 4033.84] Game on. |
• GopherCon US is moving from Florida to Chicago due to two new laws in Florida: Don't Say Gay and abortion restrictions |
• Conference organizers' decision is expensive and has significant financial implications |
• Concerns about COVID-19 spikes and travel restrictions affecting attendance at in-person conferences |
• Google's Go module proxy causing a DDoS issue for SourceHut, a Git hosting site |
• Criticisms of Google's control over the Go module proxy and its design |
• Discussion of the costs and limitations imposed by the module proxy on self-hosted projects |
• Concerns about the lack of transparency and accountability in the Go ecosystem |
• Historical context on the development of Go and its early adopters |
• Personal anecdotes from panelists about their introduction to Go and what drew them to the language. |
• The speakers discuss their love for the programming language Go and how it has become their professional language. |
• One developer mentions an experience where someone thought Go was too complex and not worth using due to its optimization capabilities, but this was not necessarily the case. |
• Simplicity is discussed as a key aspect of Go, with one speaker defining it as "anti-complexity" that pushes back on developers trying to introduce complexity into their code. |
• The speakers also discuss how Go's simplicity can be misunderstood by some developers who may think it means easy to learn and use, but it actually requires more time and effort to master. |
• The density of the language is mentioned as another aspect of its simplicity, with concise lines of code making it easier to read and understand. |
• Consistent tooling and formatting in Go are also highlighted as factors that contribute to its simplicity and ease of use. |
• One speaker mentions how consistent formatting makes it easier for tools like Copilot to work effectively with the language. |
• Discussion of Bill Kennedy's commentary on the module proxy in Go |
• Importance of recognizing both the benefits and drawbacks of big companies supporting open-source communities |
• Concerns about harming underrepresented communities through actions like centrally hosting projects |
• Trade-offs between community needs and individual developer preferences |
• The need for a more nuanced understanding of the complexities involved in balancing competing interests |
• Shout-out to Google's donations and support for the Go community, despite some concerns about resource allocation |
• Proposal for concise function definition syntax |
• Discussion of polarizing opinions on the proposal |
• Explanation of the proposal and its potential benefits |
• Criticism of implicit returns and potential impact on code clarity |
• Debate on the importance of specifying return types in compact functions |
• Reference to a GitHub issue discussing possible changes to the syntax |
• Mixed messaging around "family-friendly" language in conference announcements |
• Discussion on using clearer language instead, such as "kid-friendly" or "children welcome" |
• Concerns about unintentional signaling to marginalized communities when using ambiguous language |
• GopherCon Europe's consideration of offering discounted tickets for partners who want to attend but not participate in talks |
• Cultural differences in understanding what "family-friendly" means, particularly in the US vs. other countries |
• Discussion about the phrase "family-friendly" and its limitations in including non-traditional family structures |
• Concerns about sponsors being unwilling to support inclusive policies |
• Idea of listing benefits instead of using phrasing like "family-friendly" |
• Importance of queer inclusivity, particularly during Pride month and the concept of "queer new year" |
• Discussion of rainbow washing and its implications in promoting LGBTQ+ inclusion |
• Companies pretending to support queer rights only in June and using it as an opportunity for marketing |
• The criticism of companies changing their logos to include Pride flags without genuine support |
• Monetary donations to organizations that help queer people, such as the Trevor Project |
• Authenticity vs. performative allyship: doing something to get recognition rather than genuinely supporting the community |
• Employee-led initiatives to donate company funds to supportive organizations despite management's reluctance |
**Natalie Pistunovich:** Good evening, morning, and afternoon, everyone, from wherever you're joining us. I'm Natalie, and I'm joined today by Ian and Kris. Hello. |
**Kris Brandow:** Hello. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.