text stringlengths 0 2.35k |
|---|
**Johnny Boursiquot:** I think when you tweet, Twitter gives you that option to select who can reply to your tweet... If you select of the options, if you go from everyone to people you follow, or only people you mention... Let's go with the people you follow. I think that's the equivalent of saying "You know what - I ... |
**Ian Lopshire:** I agree with that. |
**sam boyer:** Yeah... I can't disagree. It's sort of literally true. I think I'm just not sure that it's worse than any of the alternative options, if you sort of play them out a bit. But that feels like a longer conversation... \[laughs\] |
**Kris Brandow:** I feel like it's a necessary thing though, because people commenting on the internet are horrible, and they are especially horrible to certain groups of people. So I think it -- I would say it depends on who's using it. If it's just someone that would be praised in bulk, if it was just open and had a ... |
**Johnny Boursiquot:** Yeah, the fact that we can all agree on the one thing - that should make for a pretty question to ask our followers. |
**Kris Brandow:** Spicy... |
**Johnny Boursiquot:** Spicy, yeah. |
**Kris Brandow:** Alright, I think that sounds like it's it, since Ian doesn't want to come up with an unpopular opinion... |
**Johnny Boursiquot:** Hey, Ian... \[laughter\] |
**Kris Brandow:** It's okay, it's okay. That just means you have to automatically have to come back next time, because -- |
**Ian Lopshire:** I could offer you my backup one, but it's got Aristotle in it, and I don't feel like anybody can understand that garbage... So let's just not. That's a terrible idea. \[laughter\] |
**Kris Brandow:** That sounds like a good place to end the episode then... Ian and Sam, thank you as always for joining us, and thank you, Johnny, for being an amazing co-host. |
**Johnny Boursiquot:** My pleasure. |
**Kris Brandow:** Thank you out there listeners for listening to another very meta and analogy-filled podcast. I hope you've enjoyed it. |
**sam boyer:** May your grass ever be greener. |
**Johnny Boursiquot:** Get some grass... \[laughter\] Get some grass... Get it? \[laughter\] |
• Go 1.19 release cycle |
• Carl Johnson on the development process of Go releases |
• Features in Go 1.19 compared to previous release (Go 1.18) |
• Golang Johnny and Mat Ryer's conversation about their vacations |
• Steve Francia leaving the Go team |
• Upcoming GopherCon EU conference |
• Grand Theft Auto character Carl Johnson's cameo |
• Go 1.19 is a refinement release with many minor bug fixes |
• Improvements to GoDoc for better documentation formatting, including links, lists, and clearer headings |
• Go 1.19 will correct GoDoc comments when running go fmt |
• The Go ecosystem benefits from having a shared tool and set of values, making it easier to implement changes like improved documentation |
• The conversation also touches on GitHub Copilot's ability to write code comments, including some humorous discussion about AI potentially becoming self-aware and turning against humans |
• A Chinese user suggested adding URL.joinpath to Go, which was implemented and merged into Go 1.19 |
• The development cycle of Go allows for bug fixes and corrections before releases |
• The memory model in computer programming languages deals with guarantees about the order of operations |
• Go's revised memory model provides clearer rules and covers more cases, but is mainly targeted at advanced programmers |
• New atomic types are being added to the Sync Atomic package, including bool, integers, and a pointer type, providing greater specificity and safety |
• Go team has added generics to standard library |
• New atomic types can be used to ensure type safety when working with pointers |
• Go garbage collector now allows for soft memory limit to be set, allowing for more control over memory usage |
• Soft memory limit will trigger garbage collection events as the program approaches the specified limit |
• Old method of controlling garbage collection was based on percentage of new memory vs old memory, but this can lead to issues with apps crashing due to excessive memory use |
• Twitch had used a hack called "memory ballast" to trick the garbage collector into triggering at different times |
• New abs() method has been added to time duration, which is different from manually calculating absolute values due to integer storage in computers |
• Handling time duration edge cases with integer representation |
• Impact of Go 1 compatibility promise on language changes |
• Generics: current usage, future development, and community involvement |
• Experimental generics packages (e.g., constraints) and their potential incorporation into the standard library |
• HTTP max bytes reader feature in Go 1.19 |
• Max bytes middleware limitations |
• String checking vs proper error types for max bytes errors |
• Designing the new `maxBytes` error type and its implementation |
• Backwards compatibility considerations in updating Go 1.x |
• Community discussion and consensus on the design of the `maxBytes` error type |
• Discussing the importance of designing systems with future flexibility in mind |
• Critique of Twitter as a "hive mind" that can be addictive and lead to echo chambers |
• Discussion of how the internet can amplify extreme opinions and behaviors |
• Warning about being vulnerable to groupthink and the importance of self-reflection |
• Johnny Boursiquot sharing his own observation about the pitfalls of using boolean values in programming |
• Mat Ryer agreeing with Carl Johnson's critique of Twitter |
• Using timestamps instead of booleans to store date information |
• Limitations of converting from timestamp to boolean |
• Advantages of using timestamps for storing date information |
• Handling empty states when working with timestamps |
• Time travel as a theme in movies and its relation to understanding time concepts |
• Criticism of the Star Trek reboot movie for inconsistent time travel rules |
• Discussion of time travel rules in science fiction movies |
• Explanation of how invisible characters should be able to see and interact with their surroundings |
• Complaints about the complexity of modern technology, particularly remotes and voice control systems |
• Joking discussion about choosing trigger words for voice control systems |
• Discussion of a past conversation |
• Johnny Boursiquot praises Mat Ryer's hosting job |
• Carl Johnson thanks Mat for having him on |
• End of the episode announcement and goodbye |
**Mat Ryer:** Hello, there. Welcome to Go Time. I'm your Mat Ryer, and today we're talking about Go 1.19, the next major release of Go. Joining me, it's co-host, it's Golang Johnny. Hello, Golang Johnny. |
**Johnny Boursiquot:** Hello, there. I'm happy to be back. |
**Mat Ryer:** Welcome back. Yeah, good to have you back. It's been a while... |
**Johnny Boursiquot:** It's been a minute, yeah. Yeah. I've just had some vacation squeezed in there, you know, and had stuff going on... |
**Mat Ryer:** Nice. |
**Johnny Boursiquot:** So yeah, it's been a minute, and I'm glad to be back. |
**Mat Ryer:** Where did you go? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.