ivan/site
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

u

Browse Source
This commit is contained in:
rawley
2025-10-15 10:51:27 -06:00
parent e6019a98f5
commit becd0095d8
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
posts/perl-in-2025.html
View File

@@ -26,7 +26,7 @@
<p> <p>
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). 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 use 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 <i>should</i> be easy, and hard things <i>should</i> be possible. paradigms within a Perl codebase, based on the problem at hand. Perl has a unique motto, easy things should <i>feel</i> be easy, and hard things should <i>feel</i> 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 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, 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,
no matter its age I can rest assured that it will work, and continue to work. Some people call this stagnation, I like to think of it as standardization, there will be no Perl version no matter its age I can rest assured that it will work, and continue to work. Some people call this stagnation, I like to think of it as standardization, there will be no Perl version