shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

285
active users

#perl

3 posts3 participants0 posts today

I was looking for an alternative to classic shell scripts, so I timed a Hello World program in different languages for fun. I thought you might want to know:

1 ms - #Bash
1 ms - #Perl
12 ms - #Python
33 ms - #Go (shebang calling `go run`)
38 ms - #C (shebang compiling to temporary file)
61 ms - #Rust (shebang compiling to temporary file)

Needless to say that this is a highly unfair and silly comparison. It's still interesting, though.

#Perl DBD::mysql and the corresponding #RHEL package have always been #MariaDB compatible, i.e., you could install MariaDB and DBD::mysql RPMs together.
But the new DBD::mysql package in #CentOS stream can no longer be installed with MariaDB.
I filed a bug (issues.redhat.com/browse/RHEL-) and #RedHat said it's not supposed to work. Except it always has.
What do you think?
(Note if it doesn't work then all Perl scripts on the host that use DBD::mysql must be modified to use DBD::MariaDB instead.)
#mysql

issues.redhat.comLoading...

Me in 2005: Man, I wonder if Perl 6 will ever get here. Thankfully Perl 5 is still great!
Me in 2025: Man, I wonder if Perl 7 will ever get here. Thankfully Perl 5 is still great!

Don't get mad at me, #Perl peeps. I love you. At least you value backwards compatibility! *COUGH* *COUGH*

Disclaimer: I haven't seriously written any Perl code in a long time, but the language still has a special place in my heart.

Nah Bitch, now you're on *My Family's Turf*.

I asked Google for an #ASCII ART generator (because this isn't my machine, I have two bookmarked) so and "AI" was all up in my space "Let Meeee do your ASCII Art!!!

Fucker, I'mma go find some site that looks like it's from 1998, probably using #Apache and #CGI to rattle less than a hundred lines of stale, crufty, #PERL code, if ... *IF* someone didn't #monster_bash it out.

Logging into my #NextCloud to get my fucking #bookmarks because fuck this.

I can't remember if I asked this already, but I'm not seeing any search results...

Any #Perl #PerlDev folks able to shed some light on my issue installing Alt::Devel::CallParser::ButWorking ? I get an error but it's unclear how to remediate.

I'm trying to install it in an #AlpineLinux 3.19 Docker image -- it installs fine on Alpine 3.14. In 3.19, I get:

error building lib/Devel/CallParser.o from 'lib/Devel/CallParser.c' at /usr/share/perl5/core_perl/ExtUtils/CBuilder/Base.pm line 185.

Woo! After 8 months of not getting even a single reply on an enormous amount of applications, my old contractor friend who hired me years ago to do #Perl + #Mojolicious things, just asked me if I would to help him again. Paying rent and buying food without stress will be a good thing.

Personal contacts and word of mouth FTW. But tossing resumes into the black hole sucks ass.

Continued thread

Different languages are good at different things.

People have mocked #Perl for being a "write only" language, but I feel like the Perl community should take pride and own that slur - you don't need to constantly read and re-read and re-re-read (and edit) the Perl code, because it just keeps working.

Not so with #Python. Python will deprecate your shit and you will NEED to re-read that code so you can make pointless edits to keep it working.

Breaking data.table in #rstats.
This was noticed by our brilliant data analyst Hamza Mir, when analyzing a 10 #gigarow #EMR dataset. #fread will assign a name to each row, i.e. the row number. If the number of lines exceeds 2^31, then a long vector of names has to be generated and R does not support those apparently (yet).
Reproducible example (#Perl code to generate a very large dataset on left, and #rstats output with failure).
ALT-text for code.
See also stackoverflow.com/questions/76

The Perl 5 Porters have released #Perl versions 5.40.2 and 5.38.4 to address CVE-2024-56406. It is believed that this #security #vulnerability can enable Denial of Service or Arbitrary Code Execution attacks on platforms that lack sufficient defenses.

You can soon download both from your favorite #CPAN mirror or find them at:

https://metacpan.org/release/SHAY/perl-5.40.2/

https://metacpan.org/release/SHAY/perl-5.38.4/

Changes are listed in their respective “perldelta” documents:

https://metacpan.org/release/SHAY/perl-5.40.2/view/pod/perldelta.pod

https://metacpan.org/release/SHAY/perl-5.38.4/view/pod/perldelta.pod
MetaCPANperl-5.40.2The Perl 5 language interpreter
Why We Rewrote All Our Rust Code in Perl and Raku at SBI — And Why It Worked

In a bold move that raised more than a few eyebrows, Dr. K, our visionary CEO at SBI, led the initiative to rewrite all of our Rust codebase in Perl 🐪 and Raku 🦋. Yes, you read that right — Rust 🦀 out, Perl and Raku in.

What seemed unconventional at first turned out to be one of the most strategically sound decisions we’ve made:

Unparalleled Expressiveness ✨: Raku’s powerful syntax and Perl’s mature libraries gave our teams the agility to iterate faster and express complex logic with clarity.

Developer Productivity ⚡: Our engineers experienced a significant boost in productivity. Fewer lines of code, less boilerplate, and highly flexible scripting accelerated both prototyping and deployment.

Legacy Interoperability 🏛️: Perl's vast ecosystem allowed seamless integration with legacy systems, saving us months of re-engineering work.

Community & Support 🤝: While not as trendy, the Perl and Raku communities provided deep, battle-tested solutions to problems we faced.

This wasn’t just about tech—it was about culture. Dr. K reminded us that innovation doesn’t always mean following the newest trend; sometimes it means re-examining the tools we overlook and discovering new potential in them.

The results? ✅ More stable code, ✅ happier devs, and ✅ improved time to market.

Curious about how we made the transition? Let’s connect — I’d love to share what we learned.

#TechLeadership #SoftwareEngineering #Perl #Raku #Innovation #Rust #SBI #EngineeringCulture