text
stringlengths
0
1.49k
[1968.52 --> 1969.56] I mean, it's just normal.
[1969.72 --> 1976.54] We're not very effective and sometimes we're in a hurry, but that talk was basically, I mean,
[1976.54 --> 1981.18] there were the other things too, but the basic, the main takeaway for me was like Eric said,
[1982.04 --> 1983.82] go 2.0 is going to happen.
[1984.78 --> 1991.96] And if you have a problem that you want to, is not being solved now that you do want to
[1991.96 --> 1999.76] be solved, submit what your problem is, because we need to understand what kind of problem it
[1999.76 --> 2000.08] is.
[2000.24 --> 2001.96] Don't submit a feature request.
[2002.06 --> 2003.94] Don't jump ahead and say, oh, I have a problem.
[2003.94 --> 2008.26] And I think it's going, it will be solved if you go ahead this.
[2008.56 --> 2012.46] So therefore I am requesting that you add this to go.
[2013.36 --> 2019.66] They were, he was very specifically saying, submit your problem, submit a use case for
[2019.66 --> 2020.18] your problem.
[2020.66 --> 2026.82] And I was reading Reddit and there were so many people saying, oh, after that talk, I
[2026.82 --> 2031.00] don't know if they watched it or not, or read about it or not, because there was also a blog
[2031.00 --> 2032.04] post that goes with it.
[2032.04 --> 2035.50] But people were saying, yeah, I love if you go ahead this.
[2035.92 --> 2040.86] And some people are pointing out, dude, you need to submit your problem.
[2041.70 --> 2042.74] Not a feature request.
[2042.88 --> 2044.86] It's not about submitting feature requests.
[2045.90 --> 2049.34] If they had named the talk, if I'm sorry, I didn't mean to cut you off.
[2049.42 --> 2049.86] Please finish.
[2050.70 --> 2052.16] No, I was just going to repeat myself.
[2052.26 --> 2053.20] Thank you for cutting me off.
[2053.20 --> 2060.78] If he had named the talk, how to communicate or build consensus on the forward movement
[2060.78 --> 2063.60] of a project, then I would give it 12 out of 10.
[2064.68 --> 2066.04] But he named it the future of go.
[2066.46 --> 2070.54] So I say it's, it's a five out of 10 because we didn't talk about ghost future.
[2070.58 --> 2075.30] We talked about communicating and building scientific evidence about why we need to change things
[2075.30 --> 2075.58] and go.
[2075.58 --> 2079.00] We talked about how we will influence the future of go.
[2079.52 --> 2079.90] Exactly.
[2080.08 --> 2081.10] Which will be a future of go.
[2081.36 --> 2086.94] Which again is an incredibly valuable talk, but we totally got click baited on the title.
[2087.64 --> 2091.00] 10 people got together in a room and built go to go 2.0.
[2091.36 --> 2092.98] Click here to see what happens next.
[2092.98 --> 2100.54] So, um, uh, one cool fact that I'm, I'm going to totally ignore Brian right now.
[2101.90 --> 2102.84] This is new.
[2103.28 --> 2108.82] One, one cool fact that came out of that though was, um, I forget where the stat came from,
[2108.82 --> 2114.22] but I know that they had estimated somewhere between 500,000 and a million go programmers
[2114.22 --> 2118.22] in the world, which seems astronomical at this point.
[2119.28 --> 2122.96] I can't remember where the stats came from either, but you're ignoring me.
[2122.98 --> 2124.00] So I won't answer any.
[2126.34 --> 2131.14] So other talks, um, Oh, you know, who nailed one?
[2131.44 --> 2132.14] Liz rice.
[2132.76 --> 2133.00] Yeah.
[2133.00 --> 2135.22] The go programmers guide to this calls.
[2135.46 --> 2136.66] That was so cool.
[2137.94 --> 2138.68] Great talk.
[2139.38 --> 2145.94] She basically, uh, started the talk out, um, talking about how in, um, prior talks, she
[2145.94 --> 2152.86] mentioned system calls and she wanted to kind of make sure she knew what she was
[2152.86 --> 2156.02] referring to when, uh, talking about them.
[2156.02 --> 2160.04] So we're to talk, uh, explaining how system calls work to people.
[2160.04 --> 2161.38] And that's actually really great.
[2161.38 --> 2166.30] If you're not familiar with how system calls work and, uh, a little bit of it, like Linux
[2166.30 --> 2170.80] assembly to kind of really helps solidify that too.
[2170.80 --> 2177.20] And, and what it talks about, you know, as far as, you know, resetting registers and things
[2177.20 --> 2177.76] like that.
[2178.42 --> 2178.86] Yeah.
[2178.94 --> 2181.56] Brian downs and slack said he could listen to Liz talk about anything.
[2181.56 --> 2182.60] And I totally agree.
[2182.60 --> 2187.88] This is maybe the third time I've seen her talk and she just has such a fantastic delivery
[2187.88 --> 2192.58] and she's so eloquent and she knows the material so well.
[2192.58 --> 2197.58] I mean, you know, between her and Jess Frizzell, I have a hundred percent imposter syndrome when
[2197.58 --> 2200.44] it comes to deep kernel level knowledge of anything.
[2200.70 --> 2202.08] Just no, go ask them.
[2202.14 --> 2202.68] Cause I don't know.
[2203.44 --> 2205.96] I want to say, I was going to say the same thing.
[2206.04 --> 2210.56] I was going to say, I haven't seen her talk, but I don't even care what it was about.
[2210.64 --> 2211.84] Cause I've seen her talks before.
[2211.84 --> 2215.28] Or like the talk that she gave it, go, go language K last year.
[2215.28 --> 2216.82] It's like, she's so great.
[2217.22 --> 2218.88] I would watch anything she talks about.
[2220.00 --> 2220.64] Yeah.
[2220.74 --> 2225.80] And, um, if you didn't see it, the talk that Carlyce is referring to, um, from Golang UK
[2225.80 --> 2230.62] was, um, she implemented containers in go.
[2231.94 --> 2233.28] She did it live.
[2233.76 --> 2234.02] Yeah.
[2234.20 --> 2235.76] And this is very badass.
[2236.14 --> 2237.10] It's super cool.
[2237.14 --> 2241.68] And I love that it makes the containers, uh, seem less magic.
[2242.34 --> 2246.04] Cause I think a lot of people see them as, you know, just kind of this, it's kind of
[2246.04 --> 2246.98] like a virtual machine.
[2247.10 --> 2251.80] You don't implement your own virtual machine, you know, virtualization software, but it kind
[2251.80 --> 2256.34] of really breaks it down and you can kind of see the primitives of how C groups and namespaces
[2256.34 --> 2262.80] play into it and how that they're, you know, uh, it's really just a highly configured process.
[2264.00 --> 2270.50] So also on the deep technical end was Keith Randall, uh, came back and talked about SSA.
[2270.50 --> 2272.22] Uh, the SSA talk.
[2272.32 --> 2272.94] That was a good one.
[2273.46 --> 2273.62] Yeah.
[2273.62 --> 2277.72] Which also, uh, if, if you, uh, love assembly.
[2278.38 --> 2278.82] Yeah.
[2279.04 --> 2282.58] Which to be honest, I still don't understand, but it was a great talk.
[2283.34 --> 2285.72] I was going to say exactly the same thing.
[2285.72 --> 2288.34] Hand wavy magic, something, something compiler.
[2288.56 --> 2288.70] Look.
[2289.26 --> 2289.66] Yeah.
[2290.04 --> 2293.64] It's one of those things like you don't understand, but it makes sense.
[2293.74 --> 2294.58] It's amazing.
[2294.90 --> 2295.90] It's a great talk.