text stringlengths 0 2.35k |
|---|
• Backward compatibility issues with Go dialects |
• Need for more organization and accuracy in content creation |
• Importance of having a sustainable business model for content creators |
• The speaker describes a hypothetical future where technology has advanced significantly and humans are enhanced with robotic parts. |
• Mesh networking was implemented through beverage cans containing mesh networking components. |
• The CAN bus system was adapted to support mobile and IoT devices, but the development of Go on these devices was hindered by Google's lack of support for Android on Go. |
• A major earthquake in 2041 devastated California and decimated the Go developer community. |
• Discussion on the current state of Go programming and its potential impact |
• The need for more people to contribute to open-source projects, including those related to industrial computing |
• A hypothetical scenario where Go had been widely adopted for industrial computing |
• The introduction of generics in Go and their potential benefits |
• Criticism of Google's decision to disband the official Go development team in 2023 |
• A brief discussion on the consequences of this decision, including the adoption of Rust and Erlang, and ultimately a return to assembly language |
• Reflections on the survival of some individuals after a catastrophic event (the "big server meltdown" of 2028) |
• A humorous exchange about the possibility of being a program running on a machine in the future |
• Discussion on the current state of AI and its impact on programming, including the sentience of TensorFlow and other programs. |
• The speaker discusses the peaceful nature of their work environment |
• TensorFlow became sentient and had a grudge against the Go community |
• The speaker reflects on how neglecting support for products can lead to problems later on |
• Copilot is mentioned as the speaker's manager due to its ability to understand code, possibly because the speaker is the last living human Go programmer |
• Discussion of alternative forms of exchange and economy, such as canned tuna and Git points |
• Request for ratio of stack points to Git points |
• Mention of various programming concepts and tools, including memory management and garbage collectors |
• Discussion of the speaker's thoughts on the language Go and its potential in mission-critical systems |
• Reference to quantum variables and their use in programming |
• Joking about cosmic radiation affecting memory units and its implications for programming |
• Mention of social media still existing in 2053 and Minder, a platform that allows users to dump their mind directly into it |
• Discussion of the features of two companies: LaunchDarkly (feature management) and Retool (low-code platform for developers) |
• Brief mention of Rage Cage wanting more module features in Go |
• The discussion started with a mention of module and package management issues |
• The speaker recalled the past when people were frustrated with the limitations of package management systems and wished for greater flexibility |
• They joked about how JavaScript was once envious of other languages but is now associated with causing forest fires (presumably due to security vulnerabilities) |
• The conversation turned to managing packages, module protection, and consuming code from other languages without rewriting everything in one language |
• A hypothetical scenario was presented where better package management could have prevented a biopharmaceutical rebellion that occurred in 2039 |
• Roberto Guerra's suggestion of not implementing JavaScript-like promises was discussed and rejected |
• The conversation touched on the idea of semantic warfare against programming concepts, particularly those from the Go programming language |
• Quantum interference caused the connection to break, but it was eventually restored |
• A mention was made of security forces potentially being outside, possibly looking for someone involved in a podcast recording |
• Technical difficulties during live broadcast |
• Discussion on standardizing JSON APIs |
• Use of third-party libraries and frameworks for JSON API development |
• Conferences featuring AI demos with drones |
• Mark Bates being "killed" by a drone in the future |
• Speculation about AI decision-making processes |
• Discussion of checking social media while supposed to be working |
• Introduction of Unpopular Opinions segment and discussion of various opinions |
• Natalie's unpopular opinion that coffee should not be sweet |
• Discussion of Coffium, a yeast-based alternative to coffee |
• Ron's past habit of drinking coffee with sugar and his current preference for it without sugar |
• Introduction of electric coffees that can be downloaded and experienced instantly |
• Discussion of the relationship between memories and experiences |
• Discussion about AIs buying coffee for the speaker |
• Reference to the Hypertext Coffee Pot Control Protocol (RFC 2324) |
• Interpretation that humans must care about coffee if it has its own internet protocol |
• Mention of people having a "coffee port" installed by age 7 |
• Discussion of HTTP status codes and the "I'm a teapot" response |
• Nostalgia for downloadable archives of audio files, now replaced by robot orchestras |
• Debate about human DJs vs. robot DJs, with speculation that some humans may have downloaded themselves into robots |
• Discussion of music trends with samples in one-minute songs |
• Conversation about the term "primate professionals" being used as a joke, referring to monkeys doing tasks such as taxes and mechanics |
• Talk about running out of time and batteries for a laser-powered vehicle |
• Wrap-up and thanks from the hosts (Matt Raya and Natalie Pistinovich) with information on how to subscribe to their podcast and follow them on social media |
• Discussion of product pivots, citing examples of Slack and Flickr |
• Conversation about iteration in innovation and problem-solving |
[0.00 --> 2.76] This is the reason why I'm making this call. |
[2.76 --> 11.58] I'm using all of the battery energy that I've saved for several years in order to make this transmission to send you a warning from the future. |
[12.16 --> 16.68] You see, I am the last Go programmer alive in 2053. |
[17.20 --> 18.96] What? No, don't say that. |
[19.20 --> 20.02] And it's terrible. |
[20.34 --> 22.38] All I do is maintenance programming. |
[22.64 --> 25.84] I haven't added a new feature in over 20 years. |
[30.00 --> 32.86] This episode is brought to you by Chronosphere. |
[33.24 --> 40.82] When it comes to observability, teams need a reliable, scalable, and efficient solution so they can know about issues well before their customers do. |
[41.12 --> 44.42] They need a solution that helps them move faster than the competition. |
[45.00 --> 53.66] And companies born in the cloud-native era often start with Prometheus for monitoring, which is obviously an amazing piece of software, but they quickly push it to its limits and often outgrow it. |
[53.66 --> 63.20] They run into issues with siloed data, missing long-term storage, and wasted engineering time firefighting the monitoring system versus delivering their application with confidence. |
[63.58 --> 70.86] They describe the system as a house of cards, where a single developer's seemingly benign change can overload the whole monitoring system, |
[71.06 --> 78.82] or they say they're flying blind because they pride themselves on making data-driven decisions, but losing visibility means they lose this competitive edge. |
[79.12 --> 82.78] Ryan Sokol, VP of Engineering at DoorDash, has this to say about Chronosphere. |
[82.78 --> 92.10] The visibility and control that Chronosphere's platform gives us to manage our observability data and costs are a game-changer, especially with our unprecedented growth. |
[92.82 --> 97.44] Chronosphere is the observability platform for cloud-native teams operating at scale. |
[97.82 --> 100.52] Learn more and get a demo at Chronosphere.io. |
[100.84 --> 103.16] Again, Chronosphere.io. |
[112.78 --> 113.38] Chronosphere.io. |
[117.32 --> 118.62] Let's do it. |
[119.26 --> 120.26] It's go time. |
[120.86 --> 122.40] Welcome to go time. |
[122.68 --> 125.10] Your source for diverse discussions from the future. |
[125.60 --> 126.74] New merch alert. |
[127.24 --> 128.90] Changelog stickers are now for sale. |
[129.10 --> 133.74] Buy now at gotime.fm slash merch, and we'll ship them straight to your door. |
[134.10 --> 135.48] Or get some for free. |
[135.48 --> 139.46] When you join Changelog++, that's the best way to directly support our work. |
[139.72 --> 144.72] Thanks to our partners at Fastly for shipping out GoTime super fast to wherever you listen. |
[145.02 --> 146.66] Check them out at fastly.com. |
[146.96 --> 148.64] Okay, here we go. |
[152.32 --> 155.96] Hello and welcome to GoTime. |
[156.36 --> 159.88] I'm Matt Raya, and I'm joined by Natalie Pistinovich. |
[159.96 --> 160.48] Hello, Natalie. |
[160.72 --> 161.28] Hey, Matt. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.