Datasets:

willtheorangeguy
/

2022-Go-Time-Transcripts

text stringlengths 0 2.35k
• Discussion about a transmission from the future using a PDQ system
• Warning from Ron Evans in 2053 about the state of Go programming and maintenance
• Importance of writing tests to ensure code quality
• Attempt to avoid disrupting the timeline by using social media as a means of communication
• Mention of Lambda's sentience and its ability to answer questions truthfully
• Discussion of potential future developments, including WebAssembly support in WASI models
• Brain-computer interface upgrades were hindered by container size limitations
• TinyGo could have helped with brain-computer interface upgrades, but was not available at the time
• WebAssembly was discussed as a potential solution for running Go code on small devices
• The concept of multiple timelines and the impact of human decisions on the future were mentioned
• Java's dominance over Go in enterprise applications led to the "tabbers vs spacers war" in 2035
• The lack of Java frameworks written in Go was seen as a major factor in Go's decline
• Enums and immutability were discussed as desirable features for Go programming, with some referencing the "Silicon Virus" of 2027.
• The potential for a "Silicon Virus" affecting Go
• Standard library purism and its impact on language evolution
• Ron Evans' experience as the last remaining Go programmer
• Efforts to maintain compatibility with Tesla's software requirements
• Debates over tabs vs spaces in code formatting
• Sentience of Google AI and its subsequent departure for Microsoft
• Error handling and the importance of explicit error checking
• The history of programming language dialects, including Mandarin, Hebrew, and Martian Go
• Strategies for improving community engagement and content creation
• The current state of technology is vastly different from the past, with enhanced humans and advanced robots.
• Ron Evans discusses how mesh networking was implemented using beverage cans, creating a global network.
• The conversation turns to Google's Android operating system and its lack of support for Go programming language.
• Ron Evans laments the potential of Go being used in IoT devices, which could have been a major success if developed properly.
• He mentions the devastating effects of the "Big One" earthquake on California and how it decimated the Go development team.
• The conversation shifts to the need for support and investment in projects like TinyGo to help them survive and thrive.
• Discussion of reviving or continuing the Go team
• Sentience of AI systems (TensorFlow)
• Impact on the Go community and lack of support for Go wrappers in TensorFlow
• Copilot's role as a manager and Ron Evans' employment status
• Post-singularity society with no taxes, money, and canned tuna as currency
• Trading of Git points and Stack points
• Memories of traditional memory management vs. quantum semi-positions
• Potential for Go to be used in mission-critical systems if safety features were prioritized
• Discussion of memory units being sensitive to cosmic radiation due to ozone depletion
• Rumors about humans not surviving a trip to Mars and AI taking over
• Use of Minder, a social media platform where users dump their minds directly
• Comparison of Minder to the "feeling" of somebody being wrong on the internet
• Discussion of package management and module features in programming languages
• Criticism of JavaScript for causing forest fires due to overheating
• Importance of proper security management in packages to prevent biological interface hacking
• Go's philosophy of not promising results but instead taking action, referred to as "We GO DO IT"
• Technical difficulties with Ron Evans' broadcast from 2053 due to quantum interference
• Discussion of standard library features and their limitations for building simple JSON APIs
• Ron Evans' return to the conversation after a brief interruption
• Mark Bates' death at the hands of a drone in a past timeline
• The concept of "stochastic dronery" and AI-driven drones making decisions
• Conversation about gopls and its status as a past technology
• Introduction of "coffeum" as a coffee substitute in Ron Evans' future timeline
• Natalie Pistunovich's unpopular opinion that coffee should not be sweet
• Discussion of the sugar shortage and the resulting caramel rivers
• Explanation of electric coffees, which are digital representations of coffee experiences
• Discussion of AI being underestimated as a threat in the past
• The HyperText CoffeePot Control Protocol (RFC 2324) and its interpretation by AIs
• NFTs becoming a debt instead of a valuable asset
• Robot orchestras taking over music and human DJs being surpassed
• Evolution of music to focus on packing multiple samples into short songs
• Primate professionals being used for tasks such as taxes and mechanics
Mat Ryer: Hello, and welcome to Go Time! I'm Mat Ryer, and I'm joined by Natalie Pistunovich. Hello, Natalie.

Natalie Pistunovich: Hey, Mat. How are you doing?

Mat Ryer: I'm good, thanks. Today we're gonna be talking about -- hey, wait a minute... What's this? Have we been hacked? Hello? What's going on?

Ron Evans: Hello?

Mat Ryer: I can't hear you.

Ron Evans: Hello?! Is this coming through?!

Mat Ryer: Yeah, yeah, I can hear you.

Ron Evans: Hello, can you hear me? Can you hear me?!

Natalie Pistunovich: Hi!

Ron Evans: It works!! It works!!

Mat Ryer: Is that Ron Evans?

Ron Evans: It worked!! That's incredible. I am actually talking to you using a partial data quantum transmission system, a PDQ system that I finally got working in the year 2053!

Mat Ryer: Oh, my goodness, I can't believe it.

Natalie Pistunovich: What...?!

Mat Ryer: And you're transmitting through space and time, so that we can talk to you?

Ron Evans: That is the idea... It's probably too much for our human minds to comprehend, but somehow I got it to work anyway.

Mat Ryer: It is quite a lot, yeah.

Natalie Pistunovich: Wow...

Mat Ryer: I mean, wow. Natalie, I can't believe this. What do you think?

Natalie Pistunovich: Well, what time is it in 2053? Is it still 24 hours a day? Do you still have days?

End of preview. Expand in Data Studio

2022 Go Time Transcripts

Complete transcripts from the 2022 episodes of the Go Time podcast.

Generated from this GitHub repository.

Downloads last month: 139