text stringlengths 0 2.35k |
|---|
**Johnny Boursiquot:** Perhaps we need a blog post from you when you're done with school, or something... \[laughs\] If you don't mind me asking, what did you go back to school for? |
**Aaron Schlesinger:** Well, I went back to school for computer science. I got an undergraduate Computer Science degree in 2008. I'm not that old, but I feel older than I am, I guess... You can do the math at home, see and figure out how old I'm likely to be... And so then I've been in industry ever since, focused on i... |
I kept using the SQL and the database examples because right now I'm taking a course in databases, so that -- |
**Johnny Boursiquot:** \[laughs\] There you go. |
**Aaron Schlesinger:** ...easy extension there. But the thing that I'm planning to specialize in now is formal methods, because I love this stuff... Programming language theory, and things like that - I really do enjoy it a lot. And the formal methods specialization happens to have quite a bit of language theory stuff ... |
**Johnny Boursiquot:** Yeah, it sounds like you're in your bread and butter kind of space right now... That's nice. Nice, nice. |
**Aaron Schlesinger:** Yeah. |
**Johnny Boursiquot:** Now that you mention it, interesting enough -- I think we tend to go to school to get a specialization and to narrow down on a very particular set of skills... Even though when we go in, we might not notice what we're doing, but we're going to learn how to do X, and then we come out and we get a ... |
**Aaron Schlesinger:** Well, I'm very, very lucky and privileged to be able to do that at this point. Because I think probably all of us remember in undergrad we probably just went so we could get to whatever our next step was. Most of us it probably was a job; maybe some of us was grad school, but most of us was a job... |
**Johnny Boursiquot:** Pretty cool, pretty cool. Well, Aaron, unless you have another more unpopular opinion for me -- although I don't think anything you said here is unpopular. Maybe it's just the way you talk and put it, but I don't think any of it was unpopular... |
**Aaron Schlesinger:** Diplomacy, yeah... Well, I do have an unpopular opinion. |
**Johnny Boursiquot:** Okay... |
**Aaron Schlesinger:** This one will be unpopular. |
**Johnny Boursiquot:** Okay, wait, then I've gotta play the song if that's the case. |
**Aaron Schlesinger:** Okay, let's do it. |
**Jingle:** \[47:55\] to \[48:11\] |
**Johnny Boursiquot:** Go on, lay it on us. |
**Aaron Schlesinger:** Alright. Well, I've been doing a bunch of Rust lately, some very low-level stuff dealing with virtual machines... And I believe now that I've used Rust long enough... I believe the type system in Rust is more complete, and leads to more concise and easier to write and read programs in Go. |
**Johnny Boursiquot:** Okay then... |
**Aaron Schlesinger:** Yeah, so the Go type system has some work to do. |
**Johnny Boursiquot:** Okay, okay... |
**Aaron Schlesinger:** I don't mean to fan the flames of the Go/Rust thing, but I'm sure I just have. |
**Johnny Boursiquot:** \[laughs\] Too late, buddy... |
**Aaron Schlesinger:** I've just done that... The flame war... |
**Johnny Boursiquot:** It's been zero days now since the flame wars... \[laughter\] |
**Aaron Schlesinger:** I know. I know... I talked a lot about type system things today, and it's not that Rust lets you do all those things. It certainly doesn't. But the type system in Rust has more features than the type system in Go. It certainly allows for some programs that take forever to compile and are hard to ... |
**Johnny Boursiquot:** Okay. Well, we shall put that to the test... The audience - they will tell us whether they agree with you or disagree with you, and come find you in the night, or something... |
**Aaron Schlesinger:** Yeah, you all know my Twitter, so you can send me hatemail... I still love Go, don't get me wrong. I've been writing Go for something like ten years, or something... And there's no language I can build something more quickly in... And I'm just getting started with Rust, so this my initial opinion... |
**Johnny Boursiquot:** Hey, you can love more than one language, that's cool. As long as it's Go and Go, that's cool. \[laughter\] |
**Aaron Schlesinger:** Love anything you want, as long as it's Go. \[laughter\] I love that. |
**Johnny Boursiquot:** Awesome, awesome. So thank you so much, Aaron, for coming back on the show and talking about functional programming. 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 enable for us movi... |
**Aaron Schlesinger:** Thank you so much for having me, Johnny. |
• Discussion of functional programming with generics in Go |
• Host's experience implementing functional programming library with generics, resulting in easier implementation and more compile-time guarantees |
• Benefits of using functional programming libraries, including reduced code and increased type safety |
• Introduction to Sourcegraph for universal code search and improving coding flow |
• Aaron Schlesinger joins the show to discuss functional programming with generics in Go, specifically how it has evolved since the introduction of generics in Go 1.18 |
• Recap of functional programming basics |
• Relationship between theoretical math and practical design patterns in FP |
• History of FP in Go, including previous talks and blog posts |
• Introduction to generics as an enabler for more complex FP concepts |
• Composition and currying functions |
• Map operations on sequences (such as lists or slices) |
• Flat map operations |
• Pure functions and their applications in programming |
• Combination of lists and input/output operations |
• Filtering and zipping lists |
• Type parameterization and generics in programming languages |
• Implications of type parameterization on code generation and reflection |
• Elimination of boilerplate code with the introduction of generics |
• Elegance of leveraging type parameterization for functional programming |
• Discussion of functional programming (FP) libraries in Go and their adoption of generics |
• Benefits of using generics in FP libraries, including reduced code and increased compile-time guarantees |
• Explanation of how generic functions work in Go, including instantiation and type safety |
• Efficiency gains from using generics in writing libraries that support multiple types |
• Comparison to previous methods of supporting multiple types using the empty interface |
• Advantages of constraints on type parameters for compiler computation and improved code efficiency |
• The Go team advises caution when introducing generics to prevent overuse. |
• Functional programming in Go may benefit from a cautious approach until best practices and use cases are established. |
• The parallel version of map functions is being explored, but its effectiveness is uncertain at this time. |
• Usage in the wild and experimentation by programmers are necessary to determine the value of new features like generics and functional programming. |
• Go's imperative nature makes it challenging for some developers to adopt functional programming principles. |
• Context and higher-order functions demonstrate that functional programming concepts are already being used in production code, even if not intentionally. |
• Discussion about using PostgresQL as a time series database with advanced SQL features |
• Implications of Functional Programming (FP) on workload efficiency and best practices |
• The importance of choosing the right tool for the job, rather than overusing advanced features |
• Comparison between imperative and declarative programming paradigms |
• Benefits of declarativity in reducing lines of code, adding structure, readability, and bug fixing |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.