text stringlengths 0 2.35k |
|---|
**Mat Ryer:** We don't need one. We could just go on a website now and \[unintelligible 00:49:14.17\] and it'll make the folder, with loads of files inside, and the index page goes alongside the folder. |
**Ron Evans:** No, I can't receive files from the past. I haven't already downloaded it in the past. |
**Mat Ryer:** We could leave files from you here, could we? |
**Ron Evans:** Wait, does that make sense? \[laughter\] |
**Mat Ryer:** Well, the whole episode, or just that bit? |
**Natalie Pistunovich:** Did you just do NFTs? |
**Ron Evans:** No, it ended up you had to pay people for them. They ended up going negative -- like negative interest rates, they went to negative values. All of a sudden people are like, "You want to own the NFT? I need some money." And it was like -- ugh, what a mess. |
**Mat Ryer:** Yeah, no one saw that coming. NFTs end up being a debt. That would be interesting. |
**Ron Evans:** But the one thing that was cool is musicians started actually selling downloadable archives of audio, and people would download them and listen to them. It was kind of amazing. |
**Mat Ryer:** Hm. It sounds weird... |
**Ron Evans:** But then, all of a sudden, all of the robot orchestras took over. |
**Mat Ryer:** They're gonna be good. |
**Ron Evans:** Look, a human DJ had a physical limit of let's just say 48 hours straight... Whereas a robot DJ - they could play a 120-hour set, no problem. I mean, what human could keep up with that, I ask you? |
**Natalie Pistunovich:** Some of the Berlin DJs? |
**Mat Ryer:** \[laughs\] I thought that's all DJs did anyway. |
**Ron Evans:** I think that some of those humans downloaded themselves into those first robotic DJs, just so they would have the stamina to reach that level of dance floor completion. |
**Mat Ryer:** I've often wondered that about human DJs anyway... Like, you're making the robots do it now. They're just playing stuff on their laptop. I don't know what they're doing... I never understood it, but -- you know, I don't wanna have a go at DJs. I'm sure it is very skilled. Please don't write in. |
**Ron Evans:** Oh, no, no, that was the only music left. If you don't play at least five different songs at the same time in the future, people can't even hear the music. It's just too boring. |
**Mat Ryer:** \[laughs\] Yeah. It's the attention span, isn't it? |
**Ron Evans:** We don't have a lot of time. In a one-minute song you've gotta pack in at least 8 or 9 different samples. That's the trend in the future of music. |
**Natalie Pistunovich:** It sounds efficient. It sounds not bad. |
**Ron Evans:** Yeah. If you don't like the song - don't worry, a new one will be on in one minute. |
**Mat Ryer:** Yeah. Are monkeys still around, Ron? |
**Ron Evans:** So I find that comment offensive... |
**Mat Ryer:** Oh. |
**Ron Evans:** They are known as primate professionals. |
**Mat Ryer:** \[laughs\] |
**Ron Evans:** You know, they do my taxes... A primate professional is one of my mechanics that maintains my prosthetic limbs... So I really resent that comment. I think you should take that back. They're primates. |
**Mat Ryer:** Fair enough. Yes, primate professionals. Fair play. Well, okay, I'll tell you what - I mean, obviously, Ron, we wanna pick your brains about the future all night, but unfortunately, we've run out of time. |
**Ron Evans:** Well, that's good, because I'm actually -- my lasers are almost out of batteries. I'm gonna have to start pedaling. I'm gonna have to be pedaling for at least six or seven months to recharge now, so... I wish all of you gophers in the past a tremendous lifetime. I hope that you're able to listen to some ... |
**Mat Ryer:** Thank you, @deadprogram, Ron Evans. As always, absolute pleasure. I've been Mat Ryer, and of course, my co-host, Natalie Pistunovich... See you next time! |
• Ron Evans is calling from 2053 using a partial data quantum transmission system |
• He's the last living Go programmer and has been maintaining existing code for over 20 years |
• The future has been devastated by disasters, with climate refuges like La Pipa being rare exceptions |
• Ron has used all his battery energy to send a warning about the state of the world in 2053 |
• Chronosphere is mentioned as an observability platform for cloud-native teams operating at scale |
• Maintenance programming and lack of new features |
• Importance of writing tests for Ron's sake |
• Fiddling with the timeline and its potential consequences |
• Using Twitter to communicate without direct answers |
• Lambda AI's sentience and potential lies |
• Defending against possible threats by asking questions |
• Areas to focus on for Go to survive and thrive |
• WebAssembly support in Go apps |
• Brain-computer interfaces and the need for smaller container sizes |
• TinyGo as a solution to make WebAssembly work in Go |
• The importance of having dedicated teams working on projects full-time |
• Project structure and templates for new Go projects |
• The history of Go being compared to Java |
• The importance of frameworks in Java programming |
• Enterprise applications and lack of patterns/templates |
• Java's rise to prominence due to deals with big companies |
• The Tabbers vs Spacers war of 2035 and its impact on mechanical keyboards |
• Daniel Pakak's suggestion for more Java frameworks written in Go |
• The need for immutability and enums in programming languages |
• The silicon virus of 2027 caused by lack of standards (imperial units, made-up units) |
• Tooling and third-party libraries for image processing and other tasks in Go |
• The evolution of the standard library from being code to a belief system |
• Conflict between standard library purists and those who accepted ideas from other places |
• Heretics who were thrown out of the community went on to create new languages like Lisp |
• Silicon virus incident, with Natalie joking about it being related to bad silicon |
• Discussion of maintaining Go code for Tesla and the constraints that come with being the last Go programmer |
• Bug fixes and lack of feature development in the standard library |
• The need for money to maintain a youthful appearance through blood transfusions |
• Advertisement for FireHydrant, a reliability platform for developers |
• Brief discussion about tabs versus spaces in text editing |
• Error handling in Go |
• Philosophy of "do or do not" instead of "try" |
• Infiltration of "try" concept into Go community |
• Variable lifetimes and ownership |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.