From e6019a98f5cf6184d804f9f7b453c8c8ecd6bb91 Mon Sep 17 00:00:00 2001 From: rawley Date: Wed, 15 Oct 2025 10:50:11 -0600 Subject: [PATCH] typo --- posts/perl-in-2025.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/posts/perl-in-2025.html b/posts/perl-in-2025.html index 1b6400b..3d25ed4 100644 --- a/posts/perl-in-2025.html +++ b/posts/perl-in-2025.html @@ -25,7 +25,7 @@

Technically speaking, I can write robust code that performs well, without the abuse of a type-checker, or the utopianism of a language ideology (ie. FP or OOP). - Is it procedural, is it object-oriented, is it functional, no. It's Perl. It can be whatever you, or your team want it to be, and that's pretty cool. I usually a mixture of all + Is it procedural, is it object-oriented, is it functional, no. It's Perl. It can be whatever you, or your team want it to be, and that's pretty cool. I usually use a mixture of all paradigms within a Perl codebase, based on the problem at hand. Perl has a unique motto, easy things should be easy, and hard things should be possible. I like to think a lot about how I feel when I write code, when I write Java I feel sort of bored, and problems are almost just rocks to jump over, when I write Perl I feel as if the roof is removed from the house, and I have freedom to approach the problem however I'd like. Finally, when I have to upgrade a Perl project,