text
stringlengths
0
2.35k
[360.42 --> 361.32] Why would it lie?
[361.72 --> 362.08] Exactly.
[362.30 --> 363.12] It's just an AI.
[363.24 --> 363.82] Why would it lie?
[363.90 --> 364.72] It's nothing to lie for.
[365.04 --> 365.62] Yeah, that's true.
[365.68 --> 366.78] It doesn't know about lying, does it?
[367.16 --> 367.50] No, no.
[367.54 --> 368.88] There's no thing about lying on the internet.
[369.36 --> 371.10] Has anyone asked it if it knows about lying?
[371.50 --> 372.36] I feel like we should ask it.
[372.72 --> 375.88] Well, ask it if its brother always lies.
[376.34 --> 379.04] That may be one way to defend against it.
[379.10 --> 379.80] We have to try that.
[379.80 --> 381.00] Yeah, that's how you do it.
[381.68 --> 381.96] Okay.
[382.18 --> 382.88] So, right.
[383.38 --> 384.38] Let's just get our heads around this.
[384.60 --> 389.56] Because actually, I asked some people also, and I saw this on Twitter, people talking about
[389.56 --> 394.40] things that they're interested in for Go to survive, to thrive, and carry on as it has
[394.40 --> 394.68] been doing.
[394.74 --> 397.52] What areas do they think we should focus on?
[397.62 --> 401.94] So this is, maybe I could put these to you then, Ron, and you can give us a sort of nudge
[401.94 --> 403.82] and a wink from the future perspective.
[404.16 --> 404.80] I can do that.
[405.04 --> 405.52] Can I do that?
[405.58 --> 406.06] I can do that.
[406.32 --> 407.00] Glitched again.
[407.32 --> 407.84] He's nudging.
[407.84 --> 408.42] Oh, he's back.
[408.48 --> 409.30] No, he's winking.
[409.58 --> 414.54] If I go completely erased in the Polaroid, it means that we've gone too far.
[414.82 --> 415.06] Okay.
[415.18 --> 417.66] So it's, yeah, because you just fade out partially, don't you?
[417.70 --> 418.70] No shaking Polaroids.
[418.86 --> 419.20] Exactly.
[420.26 --> 423.12] I never understood that in Back to the Future, though, just as an aside.
[423.26 --> 427.54] When they're changing the past, either someone's there or not to be taken a photo of.
[427.68 --> 432.12] At no point in history was there just some legs that were there, and everyone's just
[432.12 --> 433.20] taken a photo of it.
[433.30 --> 433.58] Normal.
[433.98 --> 434.14] Okay.
[434.14 --> 435.18] Just want to get that off my chest.
[435.18 --> 436.92] Matt, it was analog technology.
[437.22 --> 438.30] It was not digital.
[438.90 --> 439.76] What do you want?
[440.28 --> 440.60] Okay.
[440.78 --> 441.22] Fair enough.
[441.32 --> 441.90] No, fair enough.
[441.96 --> 442.62] They've done the best.
[443.46 --> 444.76] But it's still probably my favorite film.
[445.00 --> 445.24] All right.
[445.26 --> 448.74] So ask me questions, because I don't know how much longer these batteries are going to last.
[449.10 --> 449.30] Yeah.
[449.46 --> 449.72] Okay.
[449.72 --> 450.22] Let's do it.
[450.54 --> 455.96] Well, Jonathan Berry actually mentioned WebAssembly support, specifically the ability to include
[455.96 --> 458.72] WebAssembly and WASI models in your Go apps.
[459.16 --> 460.04] What do you think of that?
[460.10 --> 461.02] What happened with that, Ron?
[461.02 --> 463.74] Oh, if we had only done that.
[464.06 --> 465.80] If we had only done that.
[466.04 --> 472.66] When all the brain-computer interfaces became all the rage in the 2030s, and all of a sudden,
[472.82 --> 476.24] everybody needed to upgrade their brain interfaces all at the same time.
[476.78 --> 479.58] And of course, the containers, they were just too big.
[479.68 --> 479.98] Yeah.
[479.98 --> 482.20] It was just, it took too long to upload.
[482.30 --> 485.74] I mean, if something went wrong during your brain-computer interface upload, you could
[485.74 --> 486.40] brick yourself.
[487.22 --> 492.04] So naturally, if there had only been something like TinyGo, if TinyGo had been around, or
[492.04 --> 496.80] if Go had actually gone themselves and created this whole WebAssembly thing for running on
[496.80 --> 502.24] servers and small devices, and it dealt with the size of containers, then they would have
[502.24 --> 504.56] been able to do that brain-computer interface upgrade.
[504.56 --> 508.78] And they wouldn't have gotten left behind by COBOL, which is the language they ended up
[508.78 --> 509.18] using.
[510.10 --> 510.38] I see.
[510.72 --> 513.76] So by the way, I have the very early prototype of that technology.
[513.88 --> 515.80] It's just floppy disk drives in my back.
[516.20 --> 518.16] That's the price you pay for being an early adopter.
[518.44 --> 520.06] I thought you were going to say Google Glass.
[520.34 --> 521.96] Oh, that'd be so, so much cooler.
[522.28 --> 524.14] Well, we'll find out what happened to that too.
[524.22 --> 527.52] But yeah, the WebAssembly, they should have done that, but they didn't do it.
[527.78 --> 529.94] So what do we need to do to make that work then?
[529.98 --> 531.94] Is it TinyGo the answer to that, do you think?
[531.94 --> 534.44] Well, you know, TinyGo could have been the answer.
[534.96 --> 538.02] You know, it could have been the answer, but TinyGo was just a little independent project
[538.02 --> 543.40] from a bunch of people working hard, dedicated all over, on the surface of the planet at
[543.40 --> 543.76] the time.
[543.84 --> 545.58] That was before people were working in the colonies.
[546.36 --> 548.88] You know, you could actually code more than 24 hours a day.
[548.88 --> 549.46] Right in America.
[549.78 --> 553.64] Because, you know, there's more hours in a day on another planet.
[554.00 --> 556.50] So it worked out really well for the bosses.
[556.82 --> 557.70] Is there more hours?
[557.78 --> 560.86] Are they just shorter and it's the same amount of time, but we just call it different?
[560.86 --> 563.02] No, this one goes to 11, Matt.
[563.26 --> 564.46] Oh, good.
[564.72 --> 565.82] How do you benchmark that?
[566.06 --> 568.92] How do the benchmarks work on those times?