Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[1257.30 --> 1259.66] changed because some whitespace thing.
[1259.82 --> 1265.12] And that got so annoying that it's very high motivator, I think, to get people formatting.
[1265.12 --> 1266.10] But I don't know.
[1266.10 --> 1268.44] I assume everyone does format their code.
[1268.88 --> 1270.92] Do you do it in the way Daniel described then?
[1271.10 --> 1274.96] Or do you do it like me, where you just, every time you save a file, it does just that file?
[1275.62 --> 1278.60] I don't think I've ever run either of the tools.
[1279.24 --> 1282.42] Or I certainly haven't run either of the tools by hand in years.
[1282.80 --> 1286.36] My editors are just set up to format files as I save them.
[1286.82 --> 1287.12] Oh, yeah.
[1287.16 --> 1287.28] Yeah.
[1287.28 --> 1291.40] I thought you were saying that you just write it in perfect, go-thumped way first time.
[1291.40 --> 1293.56] Oh, no, no, I don't.
[1293.62 --> 1294.02] Nailed it.
[1294.08 --> 1298.06] I write it in the wrong way and just let the format or take care of it.
[1298.22 --> 1300.74] Like any good codeveloper.
[1301.00 --> 1301.52] Yeah, exactly.
[1301.66 --> 1306.30] To be honest, I'll deliberately make mistakes so that when I hit save, I get the visual clue
[1306.30 --> 1307.34] that it has formatted.
[1307.74 --> 1311.16] Because if I write it and I get it right and then I hit save and nothing happens, I'm like,
[1311.50 --> 1312.58] computer's not working.
[1312.58 --> 1318.40] So I genuinely sometimes like to see the little shift into place of things as a clue that it's
[1318.40 --> 1318.76] working.
[1319.10 --> 1319.22] Yeah.
[1319.28 --> 1323.04] I mean, that's like a nice way to know that like, oh, the syntax is correct.
[1323.32 --> 1324.24] Yeah, that's true.
[1324.46 --> 1325.30] You know, it can parse.
[1325.60 --> 1328.22] Yeah, because if it errors, it doesn't complete it.
[1328.34 --> 1330.56] So it actually is a feedback loop thing.
[1330.88 --> 1331.22] There you go.
[1331.44 --> 1332.46] Tip there for everyone.
[1332.72 --> 1334.40] I've actually done that with tests.
[1334.56 --> 1339.24] Like if you write a ton of software and some tests and you run the tests and everything's
[1339.24 --> 1341.56] green, I often go like, I don't believe that.
[1341.56 --> 1345.44] Let me bring one of the tests to see if I'm doing something really dumb right now.
[1345.58 --> 1347.02] Yeah, absolutely.
[1347.58 --> 1350.78] In TDD, they do talk about that red-green testing for that reason.
[1350.88 --> 1352.44] Like you have to see the test fail.
[1352.80 --> 1355.36] So you know it's saying something useful.
[1355.84 --> 1357.94] And then when you fix it, that's true.
[1358.04 --> 1362.02] If I write some code and it just, even if I'm just running it and I'm going to run it
[1362.02 --> 1366.90] myself and look at the results in the terminal, like without even any tests, if that works
[1366.90 --> 1370.20] first time, I'm highly suspicious, really suspicious.
[1370.20 --> 1374.00] So yeah, in a way, I'm not happy when it does.
[1374.92 --> 1375.24] Okay.
[1375.38 --> 1379.50] We've also got the Pacer redesign in the garbage collector.
[1379.86 --> 1380.26] Right.
[1380.46 --> 1381.16] That's interesting.
[1381.28 --> 1382.16] What's going on there then?
[1382.38 --> 1386.36] I brought this up because I think it's a very interesting topic, but I think we should also
[1386.36 --> 1389.58] warn that none of us here are experts in this area.
[1389.58 --> 1393.60] So we can talk about it at a high level, but I'm going to stop there.
[1393.70 --> 1397.94] If anybody wants to read more about it, we can mention the issue number and then they
[1397.94 --> 1400.46] can go and read the whole doc.
[1400.78 --> 1402.12] And I think that's very reasonable.
[1402.70 --> 1402.82] Yeah.
[1403.12 --> 1403.58] Fair enough.
[1403.68 --> 1404.26] Good disclaimer.
[1405.22 --> 1411.06] To give a bit of an intro, the way I understood it, because again, I just read this, the GC Pacer,
[1411.06 --> 1415.20] it's the part of the garbage collector that decides when a new collection should happen.
[1415.68 --> 1419.68] So it's sort of the thing that times when the GC should be doing its work, because if
[1419.68 --> 1423.62] it happens too often, then you're just burning too much CPU, you're wasting time.
[1423.76 --> 1428.36] But if you run it too little, you might be holding onto too much memory, or you might be
[1428.36 --> 1432.60] delaying some things happening in the runtime that you don't want to delay by very long.
[1432.60 --> 1436.84] It seems like the GC Pacer was designed a while ago.
[1437.34 --> 1439.44] For the purpose that it was designed, it was good.
[1439.68 --> 1443.78] But over time, it's accumulated a bunch of debt and a bunch of quirks.
[1444.06 --> 1448.44] And they've sort of sat down and said, okay, let's redesign it in a way that it does a lot
[1448.44 --> 1452.96] better in these edge cases that we found in production workloads that the old one doesn't
[1452.96 --> 1453.64] do very well in.
[1454.14 --> 1456.12] And I think that's where I'm going to leave it.
[1456.92 --> 1456.96] Hmm.
[1457.60 --> 1458.62] That's very exciting.
[1458.62 --> 1463.32] I'm really interested whenever there are these kind of really low level, because it's funny,
[1463.46 --> 1468.72] like when you dig into these little subsystems, they're just like other types of programs.
[1468.72 --> 1472.60] Like they are just doing the same things that we're doing in our programs.
[1472.82 --> 1478.74] But they're just so kind of, it's such an interesting domain, I think, that it always makes it more
[1478.74 --> 1479.08] interesting.
[1479.18 --> 1483.78] And the fact that, I love the fact that as programmers, we get this for free.
[1483.96 --> 1487.72] Like people are doing this work for us to make these improvements.
[1487.72 --> 1490.98] Like I didn't even know about a pacer, to be honest.
[1491.16 --> 1493.74] So it's very nice to know that that's happening.
[1494.16 --> 1495.50] What do you think about that, Michael?
[1496.02 --> 1497.00] Do you know anything about this?
[1497.46 --> 1504.38] Not, I mean, I am not closely acquainted with it, but I think any runtime improvements are
[1504.38 --> 1505.66] well appreciated.
[1506.50 --> 1507.76] Good work, team.
[1508.22 --> 1508.44] Yep.
[1508.64 --> 1512.44] And it's Michael, there's another Michael who I think was the author of the redesign.
[1512.68 --> 1513.14] Is that right?
[1513.76 --> 1514.16] Yeah.
[1514.16 --> 1517.08] Do you know all the other Michaels on the Go team?
[1517.32 --> 1520.06] Or have you got together yet with all the rest of the Michael?
[1520.42 --> 1521.14] Is there another?
[1521.94 --> 1522.72] There's a Michael.
[1523.28 --> 1524.80] I may just be a contributor, actually.
[1525.12 --> 1525.82] There's two.
[1526.70 --> 1527.80] Are there more than two?
[1528.58 --> 1530.52] Or are there three, I guess, including myself?
[1530.90 --> 1531.18] Okay.