text stringlengths 0 1.49k |
|---|
[1613.66 --> 1617.70] And a lot of people stayed for that and kind of each year it's grown bigger and bigger where |
[1617.70 --> 1621.16] now it's like a day that most people stay for the whole day. |
[1621.54 --> 1627.12] So if you have never been to the community day, you should definitely, uh, stay for that. |
[1627.16 --> 1628.92] It's probably one of my favorite days. |
[1628.92 --> 1629.80] Mm-hmm. |
[1630.18 --> 1637.12] So I saw at least two, maybe three really big projects that got a lot of lift on community |
[1637.12 --> 1637.44] day. |
[1637.60 --> 1638.82] The first one was depth. |
[1639.06 --> 1645.94] I know, um, Sam Boyer had at least three tables worth of people all contributing. |
[1646.30 --> 1650.66] And, you know, he, I think he started the day hoping that he would get, you know, two or |
[1650.66 --> 1652.62] three issues closed on GitHub. |
[1652.62 --> 1658.08] And he ended up stretching his goals beyond his wildest dreams and got a bunch of stuff |
[1658.08 --> 1660.16] done that he wasn't expecting to even finish this year. |
[1660.42 --> 1665.26] So it's really cool that so many people jumped in on the debt project and got so much work |
[1665.26 --> 1665.46] done. |
[1665.52 --> 1670.60] I know Chris Nova had a Kubicorn table and I swear to God, she looked like a cult leader |
[1670.60 --> 1673.82] over there because they were all just watching her with rapt attention. |
[1674.48 --> 1679.40] And I'm not sure what kind of things she was telling them, but I know Kubicorn had a pretty |
[1679.40 --> 1680.26] nice release too. |
[1680.50 --> 1684.18] So the cult leader is, is taking over. |
[1684.78 --> 1685.80] It was pretty cool. |
[1686.84 --> 1693.70] So how about favorite talks or at least ones that, uh, you've heard good feedback on that |
[1693.70 --> 1694.84] maybe you didn't catch yourself. |
[1695.08 --> 1700.46] I know that I often don't get to watch many of the talks, if any, until the videos are released. |
[1700.46 --> 1704.34] And depending on my work schedule is how fast I consume them. |
[1704.34 --> 1711.10] So I can start off, uh, one that, uh, seemed to get very, very good reception. |
[1711.10 --> 1716.58] And I actually have happened to watch this on, um, YouTube was just recently a guest of |
[1716.58 --> 1721.86] our show, which was, uh, Kavya Joshi, who did the, um, understanding channels. |
[1722.24 --> 1726.18] Um, if you haven't seen that talk, you weren't there for it or weren't at GopherCon. |
[1726.32 --> 1730.66] Um, it's on YouTube, all of these, all of the talks from the conference are there. |
[1730.66 --> 1733.96] Um, she walks through kind of the implementation of channels. |
[1733.96 --> 1737.64] So this isn't the, you know, how do you use them, but how do they work under the hood? |
[1738.14 --> 1745.14] And there's a bit of how the runtime works too, with regard to scheduling go routines that |
[1745.14 --> 1749.14] have, uh, blocking, uh, sends and receives on them. |
[1749.94 --> 1750.02] Yeah. |
[1750.02 --> 1755.54] It was a super geeky talk and it was low level enough that I think everybody learned something. |
[1755.54 --> 1760.40] And I, I, my favorite part of the talk was at the end when, you know, everybody mobbed |
[1760.40 --> 1761.86] her at the stage from the go team. |
[1763.08 --> 1766.52] And I turned around to Eric and I said, somebody's getting the job offer soon. |
[1769.72 --> 1771.46] So yeah, that was a really good talk. |
[1771.54 --> 1775.88] I liked, um, Edward Mueller's talk on go anti-patterns. |
[1775.94 --> 1776.90] That was a really good talk. |
[1777.00 --> 1782.04] He hit, uh, hit the nail on the head on a ton of different things that, that I've been |
[1782.04 --> 1786.16] teaching for the last couple of years and taught me several that I've been abusing for |
[1786.16 --> 1787.00] the last couple of years. |
[1787.00 --> 1788.60] So that was a really good talk. |
[1788.66 --> 1791.94] If you haven't caught that one, that room was busting out the seams. |
[1792.12 --> 1793.60] It was, it was really busy. |
[1794.08 --> 1795.52] It's one I haven't caught yet. |
[1795.58 --> 1799.24] I haven't been able to watch that video yet, but it definitely seemed like a really, really |
[1799.24 --> 1800.02] popular talk. |
[1800.76 --> 1800.96] Yeah. |
[1801.10 --> 1806.76] Everybody should watch that talk, especially beginners, especially please do. |
[1806.76 --> 1812.98] And I don't think that we could leave out, um, Russ Cox talking about the future of go, |
[1813.22 --> 1818.42] or I think people about drop dead when, uh, you mentioned that it's time to start thinking |
[1818.42 --> 1819.26] about go to. |
[1820.02 --> 1821.12] Yeah, but all right. |
[1821.12 --> 1827.64] So, you know, I love the go team and I love Russ, but man, that was the biggest cop-out |
[1827.64 --> 1828.26] talk ever. |
[1828.96 --> 1830.62] Cop-out, complete cop-out. |
[1830.74 --> 1833.16] So you put on the schedule, the future of go. |
[1833.16 --> 1835.94] And start letting rumors slide. |
[1836.04 --> 1837.50] We're going to talk about go 2.0. |
[1837.70 --> 1838.44] This is amazing. |
[1839.12 --> 1839.32] Yeah. |
[1839.34 --> 1842.20] We're going to talk about talking about talking about go 2.0. |
[1842.54 --> 1844.96] I don't, I don't, I don't know whether I agree. |
[1845.54 --> 1847.60] No, don't even try to defend him. |
[1847.82 --> 1848.52] Don't do it. |
[1848.66 --> 1848.88] Okay. |
[1849.78 --> 1850.88] Explain yourself better. |
[1851.00 --> 1851.64] I'm not kidding. |
[1851.74 --> 1854.18] I don't want to, I don't want to interpret what you're saying. |
[1854.28 --> 1855.74] Just spit it out. |
[1856.18 --> 1857.04] I'm just teasing. |
[1857.14 --> 1858.36] I'm just teasing Russ. |
[1858.70 --> 1863.08] I really have nothing bad to say about it at all, but I was just saying that we were |
[1863.08 --> 1869.08] teased by the idea that, that go 2.0 was, was coming and, and really it was just a talk |
[1869.08 --> 1873.18] about how we're going to go about talking about go 2.0. |
[1873.46 --> 1878.06] I think that the go team and everything has been, you know, very much, we're going to focus |
[1878.06 --> 1885.14] on implementation and bettering that and improving compile times and speed and all that stuff. |
[1885.22 --> 1887.06] And we're not going to work on changing the language. |
[1887.06 --> 1894.08] So I think that it still is a very exciting thing that collectively they are ready to move |
[1894.08 --> 1894.54] on that. |
[1894.62 --> 1900.06] You know, we've, we as a community have written enough go code that maybe it's time to start |
[1900.06 --> 1902.22] thinking about that and what might that look like. |
[1902.22 --> 1908.96] But I also think that, um, one of the big takeaways from that talk was soliciting for experience |
[1908.96 --> 1914.02] reports because he walks through kind of the history of how, um, they solve problems and |
[1914.02 --> 1914.72] things like that. |
[1914.72 --> 1919.42] And they want to see concrete examples of, you know, where these things are problems. |
[1919.42 --> 1921.96] Like as an example was generics, right? |
[1922.00 --> 1928.32] Like they don't, sometimes they don't have enough information to help make a meaningful decision |
[1928.32 --> 1933.22] as far as how that should impact the language without kind of seeing concrete examples of |
[1933.22 --> 1938.44] how people intend to use these things or, or, um, how it's currently failing them. |
[1938.70 --> 1943.38] So I think that that was probably the biggest takeaway is that, you know, if you want to help |
[1943.38 --> 1950.56] shape what go 2.0 ultimately becomes, um, you should make it a point to contribute that |
[1950.56 --> 1951.12] feedback. |
[1951.12 --> 1957.42] I was going to say the same thing, Erica just said, just not as articulate, but I do |
[1957.42 --> 1963.04] want to reemphasize that even though it was a talk about, let's talk about talking about |
[1963.04 --> 1968.38] go 2.0, I think it was very valuable because people communicate. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.