Datasets:
willtheorangeguy
/
2017-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.49k
[448.04 --> 448.38] Sometimes.
[449.24 --> 451.62] And Adam would also be a gopher con.
[452.36 --> 452.68] Yeah.
[452.82 --> 453.82] I'll be a gopher con.
[454.72 --> 456.48] I usually have random jobs there.
[456.58 --> 457.82] Sometimes I grab the trash.
[457.82 --> 460.76] I help out the staff.
[461.02 --> 462.62] Other times I have a camera in my hand.
[462.80 --> 468.12] And sometimes I'm just standing there with a weird face because I don't know what's going on.
[468.28 --> 469.36] But I try.
[470.34 --> 471.26] Anyways, Ruby.
[471.60 --> 472.22] Pretty interesting.
[472.54 --> 474.58] That's R-O-O-B-Y.
[475.58 --> 476.12] Written in Go.
[477.16 --> 477.38] All right.
[477.38 --> 478.06] What do we got next?
[478.86 --> 479.70] Next question.
[480.62 --> 482.08] Are we going linear down this list?
[482.76 --> 483.28] Why not?
[483.28 --> 487.80] Where do each of you put Golang in two years time?
[487.94 --> 488.52] Maybe five years.
[488.60 --> 490.20] So basically, pontificate.
[490.32 --> 491.24] Where's Go going?
[492.00 --> 492.64] Two to five years.
[493.18 --> 493.34] Yeah.
[493.44 --> 495.96] These future visions are always difficult.
[497.34 --> 501.08] Like right now, I mean, it really is the language of cloud.
[501.48 --> 501.64] Right.
[501.76 --> 504.74] Like most distributed system software is being written in it.
[505.32 --> 507.10] All the tooling surrounding that.
[507.72 --> 510.10] Monitoring and metric systems are all written in Go.
[510.10 --> 513.94] So, I mean, I feel like it's going to continue to grow there.
[514.78 --> 521.04] We keep seeing a little bit of hints at it on, you know, the phone and on embedded devices.
[521.38 --> 527.06] But I think that the catalyst has kind of already happened in the distributed systems world.
[528.06 --> 528.72] How about you, Brian?
[528.86 --> 529.94] You love these things.
[530.82 --> 534.94] I think they pinned your tweet on the GoTimeFM Twitter.
[537.10 --> 538.62] Brian's doing barbecue.
[538.62 --> 538.82] Thank you.
[539.36 --> 539.62] Right?
[539.90 --> 540.36] Are we losing?
[540.68 --> 541.58] He's muted or something.
[541.70 --> 544.44] That would explain why you guys didn't laugh at the thing I said earlier.
[544.56 --> 545.32] Because I was muted.
[547.72 --> 548.56] We'll laugh now.
[548.68 --> 549.38] What'd you say?
[549.64 --> 552.46] I said that you were the prince of podcasts.
[552.94 --> 553.18] What?
[553.68 --> 554.26] Oh, what?
[554.98 --> 556.28] See, I've forgotten most of it now.
[556.34 --> 562.48] The prince of podcasts, the royalty of radio, and the ocelot of open source.
[562.48 --> 563.72] Whoa, okay.
[564.22 --> 565.62] That's pretty interesting.
[566.18 --> 571.68] I thought that was pretty good because I couldn't think of anything that was royalty that started with an O and I needed to get open source in there.
[571.92 --> 572.54] So, you're an ocelot.
[572.74 --> 572.94] Sorry.
[573.30 --> 573.82] That's good.
[574.10 --> 574.92] Yeah, I like that.
[575.16 --> 576.68] Now you need a new business card.
[576.90 --> 578.82] Had I heard that, I would have laughed.
[579.32 --> 579.52] See?
[579.96 --> 580.22] Yeah.
[580.44 --> 580.84] Thank you.
[581.32 --> 581.70] You bet.
[582.22 --> 582.84] I'm here for you.
[582.84 --> 596.10] So, I think that Go in two years will continue the trajectory it's on now, but in five years, Go will be the dominant server-side language, taking over the spot of Java.
[597.48 --> 607.32] A lot of the really big server-side stuff that you see now, especially in the open source infrastructure bits, things like Kafka and Zookeeper,
[607.32 --> 619.90] they are slowly being replaced by much smaller memory footprint Go applications that are a little bit faster, a little bit easier to run, and significantly easier to deploy.
[621.06 --> 622.78] And that trend will continue.
[622.92 --> 626.52] So, I think in five years, definitely, Go will own the server-side market.
[627.22 --> 633.00] And two years, I don't think the change is going to be that drastic to see, but in five, I think Go will be on top.
[633.30 --> 634.88] What do you think is perpetuating that?
[634.88 --> 637.40] A single binary deploy.
[638.38 --> 650.90] If you've ever tried to administer a Kafka cluster or Zookeeper cluster or any of that, I mean, just the whole deploying JVM requires a master's degree in deploying JVMs.
[651.48 --> 652.22] Wow, that's a shame.
[652.84 --> 655.28] And Go is significantly easier to deploy.
[655.28 --> 665.86] And I honestly think the DevOps movement, the serverless movement, all of those things fit really nicely into a language that has a single binary deploy.
[666.40 --> 672.00] What do you say to somebody, sort of a flip side of that question, to somebody who's like Rust or Go?
[672.00 --> 675.78] I think it should be Rust and Go.
[676.42 --> 678.82] So, there are sweet spots for both languages.
[678.96 --> 682.32] There's no reason that you have to choose one over the other.
[682.74 --> 685.16] And there are places and times for each of them.
[685.74 --> 690.08] I really like Rust for extreme memory safety.
[690.08 --> 699.04] But I also think that Rust isn't the language to choose if you want to give it to a team of 100 people and have them build some awesome cloud project.
[700.10 --> 703.06] Rust is smaller, really memory-sensitive apps.
[703.06 --> 715.70] I was going to add to that, too, that I think a lot of it, too, is that these pieces of software for distributed systems are often complex and large and a lot of moving parts.
[716.36 --> 728.40] So, I think that having a language that's much easier to fit the whole language in your head at one time, I think, really helps people be able to be productive writing this type of software.
[729.16 --> 730.28] How about you, Carlicia?
[730.66 --> 732.60] What's your vision for the next two to five years?
[733.06 --> 735.78] Yeah, I agree completely with Brian.
[736.20 --> 746.40] Even with the time frame, I think in five years, Go will take over a lot of space that's taken up by Java right now.
[746.88 --> 749.30] It will become more enterprise-y.
[749.30 --> 763.76] I say this because I think it's over the past two years, independently of Go, it just has become easier to develop things in components and in a modular way.
[763.76 --> 773.06] So, it will be natural to just replace pieces of systems with Go.
[773.60 --> 778.54] I don't think Go is going to be homogeneous, the language that's going to be used.
[778.68 --> 781.02] And that will never happen no matter what the language is, right?
[781.06 --> 782.46] Because it doesn't even make sense.
[782.46 --> 791.70] But I think it will take up chunks and enough to be the dominant language because of all the attributes that Go has.
[791.70 --> 805.72] Now, in the next two years, what I see happening is with Steve Francia coming on board to be the sort of like product manager.
[805.72 --> 810.36] He has a different title, but that's one idea of what he does.