Datasets:
willtheorangeguy
/
2022-Go-Time-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
2.35k
[2990.00 --> 2991.92] So you can send me hate mail.
[2991.92 --> 2993.98] I still love Go.
[2994.22 --> 2995.10] Don't get me wrong.
[2995.30 --> 2998.70] I've been writing Go for something like 10 years or something.
[2999.48 --> 3003.58] And there's no language I can build something more quickly in.
[3004.10 --> 3005.46] I'm just getting started with Rust.
[3005.56 --> 3006.92] So that's my initial opinion, though.
[3007.88 --> 3009.42] Hey, you can love more than one language.
[3009.62 --> 3009.98] That's cool.
[3010.18 --> 3010.50] Oh, yeah.
[3010.62 --> 3011.60] As long as it's Go and Go.
[3011.74 --> 3012.04] That's cool.
[3014.54 --> 3016.46] Love anything you want as long as it's Go.
[3018.30 --> 3019.28] I love that.
[3020.08 --> 3020.48] Awesome.
[3020.66 --> 3020.98] Awesome.
[3020.98 --> 3025.68] So thank you so much, Aaron, for coming back on the show and talking about functional programming.
[3026.38 --> 3037.00] Hopefully we hit a few nails on the head for folks that have been curious about functional programming and how it's done, how it's been done, and what Generics enabled for us moving forward.
[3037.56 --> 3038.80] This was a fun discussion.
[3039.04 --> 3040.36] Thanks again, Aaron, for coming on the show.
[3040.68 --> 3042.18] Thank you so much for having me, Jimmy.
[3042.18 --> 3047.80] All right.
[3047.80 --> 3049.40] That is Go time for this week.
[3049.64 --> 3050.36] Thanks for listening.
[3050.36 --> 3056.42] If you're FP curious and want some more like this, we had Eric Normand on JS Party Whileback talking about it.
[3056.58 --> 3061.84] Eric is one of the best people I've heard explain FP principles and why they are worth putting to use in your code base.
[3061.98 --> 3062.48] Take a listen.
[3062.88 --> 3065.82] Have you ever seen the original show, the Get Smart?
[3065.82 --> 3069.88] Like the intro where he has like 30 different doors he walks through.
[3070.10 --> 3070.44] Yeah.
[3070.66 --> 3073.98] And then he holds up his shoe to his ear and talks into it.
[3074.00 --> 3074.02] Yeah.
[3074.20 --> 3075.22] And he has a phone.
[3075.38 --> 3076.72] He has a cell phone in his shoe.
[3077.42 --> 3077.58] Yeah.
[3077.68 --> 3080.36] But you go through all these doors, right?
[3080.42 --> 3080.58] Right.
[3080.58 --> 3084.00] And you get deeper and deeper into the sanctum of functional programming.
[3084.00 --> 3091.86] Well, that first door is just recognizing the difference between what I call actions, calculations and data.
[3092.14 --> 3092.50] Okay.
[3093.20 --> 3096.48] Calculations are often known as pure functions.
[3096.68 --> 3104.72] They're the stuff you can do in your language that always gives you the same answer no matter how many times you run them or when you run them.
[3105.38 --> 3105.66] Okay.
[3105.70 --> 3108.08] So this is like addition, right?
[3108.12 --> 3110.10] Addition is always going to two plus two.
[3110.18 --> 3110.84] It's always four.
[3111.28 --> 3113.00] It doesn't matter how many times you run that.
[3113.00 --> 3118.04] But then there's actions that do depend on when you run them or how many times you run them.
[3118.48 --> 3131.70] So reading from a mutable variable, if you read after someone has written to it, you're going to get a different answer than reading before the other, you know, other part of the code writes to it.
[3131.94 --> 3135.60] Likewise, sending an email or writing something to disk.
[3135.60 --> 3143.02] These are all actions because, you know, sending the email zero times is different from sending it one time or 10 times.
[3143.24 --> 3157.58] And so making this distinction between actions that depend on time because they're hard to deal with and calculations is like the first gateway into functional programming.
[3157.58 --> 3159.12] Oh, and data is easy.
[3159.12 --> 3162.72] Data is just, you know, the stuff that doesn't do anything.
[3162.84 --> 3163.52] It's just inert.
[3163.80 --> 3169.34] You know, the strings and numbers and hash maps and lists and stuff like that.
[3169.34 --> 3172.30] That's episode 163 of JS Party.
[3172.30 --> 3178.60] If you want to hear more, find it at jsparty.fm slash 163 or search for it in your podcast app.
[3178.72 --> 3182.46] The title of the episode is JS is an Occasionally Functional Language.
[3182.96 --> 3185.86] Thanks once again to Fastly and Fly for partnering with us.
[3186.10 --> 3187.40] Please check out what they're up to.
[3187.56 --> 3188.74] They support everything we do.
[3189.00 --> 3191.10] And of course, thank you to our Beat Freakin' residents.
[3191.36 --> 3195.32] Breakmaster Cylinder, our beats are dope because BMC makes dope beats.
[3195.64 --> 3196.52] It's as simple as that.
[3196.52 --> 3200.22] That's all I have for you, but we'll talk to you next time on Go Time.
• Discussion of using Golang for machine learning model embedding in PHP
• Comparison of Golang to other languages due to its ease of use and minimal legacy overhead
• Introduction of Sourcegraph's Code Insights feature for tracking code base metrics
• Shoutout to listener Seb for suggesting an episode about Go and PHP
• Introduction of guests Valerie Piacchansky and Anton Titov, developers at Spiral Scout working on Roadrunner project
• Discussion of the Roadrunner project as an example of Go and PHP working well together
• PHP's long history and its significance in web development
• The speaker's early use of PHP to build a forum or CMS board due to limited options at the time
• Combination of PHP with Go (Golang) to leverage benefits from both languages
• Challenges of integrating PHP and Go, including differences in frameworks, abstractions, and ecosystem
• Personal background of the interviewee as a Golang developer with experience in .NET and C Sharp
• Inspiration from working on internal projects at SpiralScout and learning from Anton's expertise
• Overview of open source contributions and the importance of finding a need and filling it
• Discussion of PHP's limitations, including its inability to scale due to bootloading applications for each request
• Introduction of Roadrunner as a solution to these limitations by removing overhead and allowing for more efficient communication between languages
• Explanation of how Roadrunner works, using RPC calls and worker pools to handle requests
• Comparison of performance with native PHP approaches, showing significant improvements in speed
• Discussion of the target audience for Roadrunner, including both Go developers working with PHP and PHP developers working with Go
• Roadrunner aims to simplify complex tasks for developers by providing pre-built solutions for queue load balancing, HTTPS traffic, and other issues.
• It targets Go link engineers who work in pair or teams with PHP engineers, allowing easy interception and modification of requests and calls.
• Roadrunner is designed for companies that want scalable code without hiring expensive Rust engineers.
• The platform includes a plugin system called Endure, which enables developers to create custom plugins and integrate them easily.
• Velux is a tool that helps build Roadrunner with custom plugins based on GitHub.
• Separation of complex tasks into GoLang and PHP components
• Use of containerization for dependency management
• Roadrunner as a tool that manages the process, not specific to PHP
• Protocol is language agnostic
• WordRunner uses default PHP interpreter, invokes it with application, and keeps it in memory in a pre-warmed state
• Supports multiple languages, including Python and GoLang
• Compatibility with multiple interpreted languages including Python, Ruby, and PHP
• Ability to run pre-compiled code in WordRunner
• Potential for a mindset shift for developers when working with multiple processes instead of single-process applications
• Role of frameworks such as Symfony and Laravel in simplifying the development process
• Benefits of using Roadrunner for efficient execution of PHP code