text stringlengths 0 2.35k |
|---|
[4385.30 --> 4385.60] No. |
[4388.22 --> 4391.60] Chris, do you have an unpopular opinion to finish us up with? |
[4391.60 --> 4393.66] I have many an unpopular opinion. |
[4393.66 --> 4396.92] I think I hold one of those most like coveted unpopular opinions. |
[4396.92 --> 4397.88] You absolutely do. |
[4397.88 --> 4398.58] Unpopular opinions. |
[4399.58 --> 4400.04] Okay. |
[4400.16 --> 4402.04] So this one is tech related, not Go related. |
[4402.56 --> 4410.28] But I think that we should kill off all C-like languages and C-derived languages |
[4410.28 --> 4414.28] and get rid of the von Neumann architecture and move on as an industry. |
[4414.88 --> 4416.70] Do you have a beat more as to why? |
[4417.24 --> 4417.94] Yes, actually. |
[4417.94 --> 4421.98] So when the von Neumann architecture was created, like we were still using discrete parts. |
[4422.08 --> 4426.32] But even when we made the first transition in the 70s to transistors, we had on the order |
[4426.32 --> 4429.48] of thousands of transistors operating at kilohertz. |
[4429.74 --> 4434.54] And now, as of a couple of weeks ago, you can buy a chip, buy a computer on the market that |
[4434.54 --> 4439.98] has over 100 billion transistors operating at several gigahertz each. |
[4439.98 --> 4445.44] So we've had many, many, many, many, many orders of magnitude along two different dimensions |
[4445.44 --> 4447.74] of improvement in our hardware capabilities. |
[4447.74 --> 4453.28] But we still use the same fundamental architecture that is the same fundamental bottlenecks attached |
[4453.28 --> 4459.92] to it, which ironically is turning our systems, our chips into distributed systems just to keep |
[4459.92 --> 4461.82] pace with the improvements that we've made. |
[4462.12 --> 4465.96] And I think all of this extra work and all of this strife is caused by the fact that we're |
[4465.96 --> 4470.00] still using this architecture, and the reason we still use it is because, well, it's the |
[4470.00 --> 4471.32] architecture of C at the end of the day. |
[4471.40 --> 4476.86] C very much programs in this mentality that recognizes the von Neumann architecture as being |
[4476.86 --> 4477.06] there. |
[4477.14 --> 4482.24] It's very difficult to write truly parallel or good parallel code or concurrent code in |
[4482.24 --> 4482.48] C. |
[4483.04 --> 4489.28] So jettison the von Neumann architecture and along with it, C and C-like languages, which |
[4489.28 --> 4491.22] unfortunately includes Go as of right now. |
[4491.22 --> 4495.78] Because while you can write some good concurrent code in Go, it's still pretty difficult. |
[4496.20 --> 4500.48] You know, we want languages that look more like Erlang, or at least have the same underpinnings |
[4500.48 --> 4505.16] of things like Erlang at the end of the day to really capture the capabilities of the silicon |
[4505.16 --> 4505.74] that we have. |
[4505.96 --> 4507.22] Because it is, you know, quite incredible. |
[4507.34 --> 4511.76] I mean, Apple did just come out with a chip that has 115 billion transistors on it. |
[4512.08 --> 4516.80] And it's like, yeah, we can't really utilize all of those if we're using them in our CPU |
[4516.80 --> 4517.56] based architecture. |
[4517.56 --> 4521.64] So more stuff that looks like graphics cards, too, because they're very good at capturing |
[4521.64 --> 4524.66] this idea of parallelizable and concurrent workloads. |
[4524.92 --> 4527.76] But yes, no more C, no more von Neumann. |
[4528.16 --> 4528.98] Get rid of it. |
[4529.12 --> 4530.10] Move on as an industry. |
[4530.38 --> 4530.88] Let's get better. |
[4530.98 --> 4534.74] Let's stop wasting so many CPU cycles waiting for our main memory to get back to us. |
[4535.00 --> 4539.10] Yeah, that may be an unpopular one, especially if you add in that like very blase, like, |
[4539.14 --> 4540.50] oh, you know, Go is included. |
[4541.02 --> 4544.76] I mean, it's like, it's all C, like, you know, Java, Go, Rust, C, C++. |
[4544.76 --> 4548.68] You know, all those popular imperative languages, just goodbye. |
[4549.16 --> 4549.92] Time for something new. |
[4550.16 --> 4551.98] Let's rewrite Linux and Erlang. |
[4552.30 --> 4552.84] It will be fun. |
[4553.28 --> 4556.14] So on that fine point, let's get rid of Go. |
[4556.64 --> 4558.82] Regrettably, that is the end of our episode. |
[4559.38 --> 4560.12] Thank you all. |
[4560.18 --> 4562.22] It was an absolute pleasure having you on. |
[4562.28 --> 4565.24] And I hope we'll have you all back very soon. |
[4565.36 --> 4567.46] Subject, how unpopular your opinions are. |
[4567.46 --> 4573.80] That is Go Time for this week. |
[4574.12 --> 4575.30] Thanks for hanging with us. |
[4575.74 --> 4581.34] Don't forget to follow GoTimeFM on Twitter so you can get in on our unpopular opinion polls. |
[4581.78 --> 4585.94] And if this is your first time listening, subscribe now at GoTime.fm. |
[4586.32 --> 4592.10] There you'll also find lists of recommended episodes, listener favorites, and a request form |
[4592.10 --> 4595.06] so you can let us know what you want to hear about on the pod. |
[4595.06 --> 4598.34] Special thanks to Fastly for being our CDN partner. |
[4598.54 --> 4601.00] Our episodes reach you fast because of Fastly. |
[4601.28 --> 4603.26] And to Breakmaster Cylinder for the fresh beats. |
[4603.64 --> 4605.16] Finally, thank you for listening. |
[4605.36 --> 4606.06] We appreciate you. |
[4606.54 --> 4609.50] Next week, yours truly is guest hosting. |
[4609.82 --> 4615.36] I've got Ian Lopshire and Chris Brando answering my newbie Go Curious questions. |
[4615.86 --> 4616.64] Stay tuned. |
[4616.78 --> 4619.80] We'll have that one ready for you next time on Go Time. |
[4619.80 --> 4620.10] Go Time. |
[4620.10 --> 4620.14] Go Time. |
[4620.14 --> 4622.14] Go Time. |
[4622.14 --> 4622.58] Go Time. |
[4622.58 --> 4623.14] Go Time. |
[4623.14 --> 4623.58] Go Time. |
[4625.06 --> 4626.12] Go Time. |
[4631.40 --> 4635.96] Go Time. |
[4638.10 --> 4638.68] Go Time. |
[4638.74 --> 4650.66] Go Time. |
[4650.66 --> 4650.74] Go Time. |
[4650.74 --> 4650.84] Go Time. |
[4651.38 --> 4653.40] Go Time. |
• Origins of GopherCon and its early days |
• Initial planning and goals for the first year (100-200 attendees) |
• Unexpected growth to 750 attendees in the first year |
• Early community involvement and support from sponsors |
• Evolution of the conference from a small, scrappy event to a large-scale organization |
• Changes in logistics, format, and speaker management over the years |
• The early days of GopherCon (2014) were marked by uncertainty and rapid evolution in event planning and logistics. |
• The conference's founder underestimated the costs of running events, including Wi-Fi, catering, and hotel commitments. |
• The introduction of community day (formerly known as Hack Day) was an unexpected success that required significant adjustments to planning and budgeting. |
• As GopherCon grew, it became a year-round effort requiring full-time attention from its organizers. |
• Partnering with Convention Designs helped manage logistics, negotiate contracts, and free up time for the conference's founder to focus on content and vision. |
• Selecting speakers for GopherCon is a challenging process that involves self-doubt and uncertainty for potential speakers. |
• The process of preparing for talks at conferences can be stressful |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.