Datasets:
text stringlengths 0 1.17k |
|---|
• Curtis Poe is the guest, discussing the programming language Pearl |
• Curtis' username "Ovid" is based on the Roman poet |
• Pearl was used for web development, especially for freeform text, but lost market share to competitors |
• Curtis emphasizes that Pearl is a "fabulous language" despite its complex syntax |
• He discusses his experience transitioning from mainframe development to Pearl in 1999 |
• Curtis wrote a book on Pearl and runs a consulting company that specializes in the language |
• The speaker has been programming in Perl for 15 years and finds it to be a versatile language that can handle text extraction and manipulation |
• Larry Wall, the creator of Perl, released it in 1987 as a tool to handle problems with other languages like AWK and sed |
• The speaker specializes in large-scale websites and finds that Perl is well-suited for this due to its ease of use and ability to glue together multiple tools |
• The speaker compares Perl to Cobol, noting that Cobol's lack of power forces users to build small, decoupled tools that can be piped together |
• The speaker mentions that Booking.com is a well-known site that uses Perl as its back-end language |
• The speaker contrasts Perl's ease of use with the complexity of other languages like Java, and notes that it is a good choice for both small and large-scale projects. |
• Java vs. Perl conversion at a company |
• Perl used in various large-scale systems, including the BBC's metadata repository and crowdsourcing platforms |
• Discussion on Perl's reputation and community, including its perceived lack of marketing and visibility in the open source community |
• Explanation of the Perl 6 project and its intended role as a sister language to Perl 5, not a replacement |
• Criticism of the community's hostility towards marketing and its impact on the language's visibility |
• Discussion on the ongoing development of Perl 5, including new features and releases, and the availability of powerful libraries and tools. |
• The power and capabilities of the Perl programming language |
• Difficulty in marketing and communicating the strengths of Perl to those outside the community |
• Sponsorship by RackSpace and its offers for developers |
• Perl's strengths and weaknesses compared to other languages, such as PHP |
• Syntactical similarities and differences between Perl 5 and Perl 6 |
• The role and benefits of Perl's "roles" feature, a concept introduced by Perl's "invariant sigils" |
• Traits researchers discovered that classes have two roles: agent of responsibility and agent of code reuse |
• The problem with inheritance is that it combines these two roles, making it difficult to reuse code without inheriting unwanted behavior |
• Roles separate class responsibility from code reuse, eliminating the need for multiple inheritance and mixins |
• Roles are available in Perl 6 and other languages, providing mathematical guarantees such as commutativity and associativity |
• The Perl 6 community has adopted roles widely, simplifying code and making it easier to understand |
• The development of Perl 6 has diverged from Perl 5, with Larry Wall shifting his focus to Perl 6 and Rakudo being used to distinguish it from Perl 5 |
• Pearl 6 is a separate community from Pearl 5, with a new set of developers from various backgrounds, including academia and real-world experience. |
• Pearl 6 is not yet in production, but some users are experimenting with it for smaller tools and scripts. |
• The transition to Pearl 6 is still in progress, with more work needed to port it to more VM and JVM. |
• Roles vs. Inheritance: the speaker discusses the differences and limitations of roles and inheritance, and their own work on "role basic". |
• Moose is mentioned as a fully-fledged object-oriented system, providing a more rigid and secure approach to type constraints and attribute validation. |
• Dynamic languages can benefit from Moose's features, such as lazy evaluation and meta-programming. |
• The speaker discusses a project called Test Class Moose, an x-unit framework for large-scale enterprise databases, which includes a metadata system for inspecting methods and attributes. |
• The speaker talks about the benefits of meta-programming, including the power it provides for simplifying code, making it easier to write and faster to execute. |
• The speaker discusses the testing story in the Perl community, including the use of TDD (Test-Driven Development) and the importance of testing code. |
• The speaker explains the CPAN (Comprehensive Perl Archive Network) and its automated testing feature, which allows developers to test their code on various operating systems and versions of Perl. |
• The speaker highlights the benefits of CPAN's automated testing, including the ability to identify which operating systems and versions of Perl a module fails on, and the ease of getting feedback from other developers. |
• The speaker also talks about the importance of testing in the Perl community, and how it's considered essential to have tests for popular modules before uploading them to CPAN. |
• The speaker discusses their positive experience with CPAN, a package manager for Perl, which has made it easier to install and manage packages. |
• The speaker compares CPAN to CPAN-MINUS, a lighter alternative that simplifies package installation and management. |
• The speaker notes that the Perl community has adopted GitHub for sharing and collaborating on code, with many developers contributing patches and documentation. |
• The speaker discusses the integration of GitHub with CPAN, allowing developers to easily link to source repositories and bug trackers. |
• The speaker mentions the rise of metafiles in Perl distributions, which provide links to external resources such as GitHub repositories and bug trackers. |
• The speaker briefly pauses the show to give a shout-out to a sponsor, StatusPage.io. |
• The speaker discusses the use of CPAN as a registry for professional modules, with Metacpan.org serving as an alternative search engine. |
• Transitioning open source work to GitHub |
• State of the Perl community on GitHub and open source |
• Use of cpan vs GitHub for collaboration and code management |
• Popular web development frameworks and tools in Perl (catalyst, dancer, mojolicious) |
• ORM layers (dbx class, rose db) and templating engines |
• Diversity of tools and complexity of choosing one for a project |
• Legacy systems and rebuilding/ modernizing them |
• Legacy data and making Pearl systems easier to use |
• Project "Veer" and building a text-based MMORPG in Pearl |
• Test class Moose repository for building large-scale test suites in Pearl |
• Programming heroes: professors who taught Cobalt with real-world experience |
• Support for the professional community and ecosystem of Pearl |
• Communication and marketing divide between Pearl 5 and 6 |
• Felt like saying goodbye to someone |
• On mute, making the speaker unaware |
[0.00 --> 14.24] welcome back everyone this is the change log and i'm your host adam stekowiak this is |
[14.24 --> 21.74] episode 133 today jared and i talked to curtis poe about all things pearl a great conversation |
[21.74 --> 27.26] you're gonna love it this show is sponsored by code ship rack space and status page.io |
[27.26 --> 32.58] we'll tell you a bit more about rack space and status page.io later in the show but our friends |
[32.58 --> 38.46] at code ship are all about continuous integration and delivery as a service you can release more |
[38.46 --> 44.34] frequently get faster feedback and build the product your users need a simple push to a repo |
[44.34 --> 49.84] runs your automated tests and configure deployments from the simple deployments are roku to complex |
[49.84 --> 55.34] deployment pipelines for large infrastructures they can all be set up with ease they even integrate |
[55.34 --> 60.54] with github or bitbucket you can get started today with their free plan setup takes just three minutes |
[60.54 --> 67.06] make sure you use the code the changelog podcast to get a 20 discount for three months on any plane you |
[67.06 --> 73.68] choose head to code ship.io slash the changelog and tell them the changelog sent you and now on to the |
[73.68 --> 87.38] show everybody we're back and today we're joined by curtis ovid uh ovid poe actually he's got a cool |
[87.38 --> 92.00] middle name there's not a real middle name maybe at some point curtis you can mention how you got that |
[92.00 --> 98.58] name it's your internet handle right yes it is i'm here jared's here we're all here with curtis and |
[98.58 --> 105.34] we're going to talk about pearl so we're excited what's uh what's ovid ovid um a long time ago when |
[105.34 --> 111.06] i switched from mainframe development and getting into pearl uh i decided to sign up for the website |
[111.06 --> 117.30] called pearl monks and i happen to tremendously enjoy poetry and when i had to pick a username |
[117.30 --> 122.90] my two top favorite poets were uh an 18th 19th century scottish poet named john davidson |
[122.90 --> 129.82] or the roman poet ovid and john davidson sounded like a very stupid username so i picked the username |
[129.82 --> 136.86] ovid and it just stuck with me for the years i like ovid i wish i had that name and i could be i |
[136.86 --> 141.28] could be a ba with with ovid oh his poetry is phenomenal highly recommended particularly |
[141.28 --> 148.16] translations by peter green so uh that's that's obviously language dependent there but um let's |
[148.16 --> 155.90] give a shout out to to uh robert norris uh he's rob n r-o-b-n on github he actually suggested this |
[155.90 --> 160.22] show via our ping repo so if you don't know it and you're a listener out there we have a weekly email |
[160.22 --> 166.80] we ship we have a featured section in there for pings we get on the ping repo drop an issue in there |
[166.80 --> 172.58] just like robert norris did or rob n on github did uh to suggest us to talk to curtis and talk about |
[172.58 --> 178.14] pearl and kind of bring we've never actually had a pearl specific show on this uh on the podcast |
[178.14 --> 183.90] so we're excited about that but uh every week we feature how many repos we feature jared on in |
[183.90 --> 191.30] weekly uh three three okay so we feature three repos in our weekly email via ping so if you've got |
[191.30 --> 195.76] some awesome repos out there you need some extra traction on drop them in there they might show up |
[195.76 --> 199.82] on the podcast they might show up in the email they might show up on the blog you just never know |
[199.82 --> 204.90] we might even tweet it out so uh with that said let's let's drop into to this conversation with |
[204.90 --> 211.06] curtis curtis you know jared jared and i you know jared back in college you did some pearl work |
[211.06 --> 217.32] i own a few pearls um we probably have a pretty diverse listenership to this uh to this podcast |
[217.32 --> 222.36] that is going to be really adept to programming but maybe not that big of a fan to pearl so what |
[222.36 --> 229.38] do you say to those people who are not huge fans of pearl um i actually don't say anything to them i'm i |
End of preview. Expand in Data Studio
2014 Changelog Interviews Transcripts
Complete transcripts from the 2014 episodes of the Changelog Interviews podcast.
Generated from this GitHub repository.
- Downloads last month
- 50