ANNOUNCE: Perl.Wiki V 1.38 & Mojolicious.Wiki V 1.12
Download from the usual place, my Wiki Haven.
Download from the usual place, my Wiki Haven.
We are proud to have the support of vitroconnect.
vitroconnect implementiert Schnittstellen und Geschäftsprozesse für eine Reihe von marktführenden Unternehmen über die eigene Brokerage Plattform. Darüber hinaus können auch frei konfigurierbare White Label Bündelprodukte geliefert werden. Seit 2011 ist vitroconnect mit seinen Kund:innen aus der Telekommunikation gewachsen: Auf der vitroconnect Plattform werden aktuell über 100 Partner verwaltet. vitroconnect ist die größte netzunabhängige Brokerage-Plattform für TK-Breitbandanschlüsse in Deutschland.
I've released a new version of SBOM::CycloneDX with support for the OWASP CycloneDX 1.7 specification (ECMA-424).
This release includes the new elements introduced in 1.7, with a focus on:
New experimental "SBOM::CycloneDX::Lite" interface: A lightweight module designed to generate BOMs with a simpler API, using the most common CycloneDX properties.
Examples included in the distribution (use them as a starting point to build your own applications/tools that generate BOM files):
The goal of this module is to help the Perl community generate BOM files more easily, improving security and compliance across the ecosystem and making the software supply chain more transparent.
SBOM::CycloneDX is available on CPAN / MetaCPAN: https://metacpan.org/pod/SBOM::CycloneDX
Related projects: - App::CPAN::SBOM - https://metacpan.org/dist/App-CPAN-SBOM - Modules::CoreList::SBOM - https://github.com/giterlizzi/perl-Module-CoreList-SBOM
All of us were present.
class :abstract attribute. Paul wants to write that because it’s a simple addition on current code and avoids design complications about roles. Aristotle doesn’t wish to introduce a new special-purpose feature now that will become redundant when a more general one is available later and wondered whether it can be introduced as roles that currently only support a small subset of features. No call has been made.class discussions also extended to looking at the meta module and API, and the common idea between the two that it would be useful to get more people to use them and discuss future ideas. We would like people to step forward here.
(I make no apologies for the ChatGPT images in my recent blog posts, by the way. No artists are missing out on being paid: I wasn’t going to hire an artist to illustrate these blog posts which will be read by like three people.)
A while back, I wrote MooseX::XSAccessor which you can add to Moose classes to inspect your attributes and try to replace the accessors with faster XS-based ones. Now I’ve done the same for constructors (new) and destructors (DESTROY) with MooseX::XSConstructor.
There are probably still bugs, but initial benchmarks look promising:
(cross-posted from my blog)
Last Monday I did the Perl Developer Release of Perl 5.43.7. As usual, I worked from the Release Managers Guide . Everything worked well, even if everything was cutting it a bit close. My video setup on the desktop was not suited for streaming anymore, so I had to do a stream consisting only of the console window and me talking over it, and no floating head of me available.
The Twitch chat was the most active that I witnessed when streaming a Perl release. We chatted about organizing Perl conferences and also the Perl release process. One realization for me was that the RMG process is mostly there to exercise the Perl build machinery and testing that the generated tarball does not have deficiencies. This means that testing that Perl can build through Configure is important, but testing different Perl configurations like ithreads or userelocatableinc is not that important.
An Analysis of The Perl and Raku Foundation's 2024 Finances
In October 2024, I published an article analyzing the financial situation of The Perl and Raku Foundation (TPRF). Since then, I have left the board, and my life is now largely unrelated to Perl. I no longer have insight into TPRF's internal decision-making but I got a few suggestions to continue, so this article again analyzes TPRF's finances using publicly available data for the 2024 calendar year. There is an unavoidable delay between when nonprofit tax returns are filed and when they become public.
Executive Summary
Revenue: A Positive Turn
There has been much to say about Perl improving in TIOBE during 2025 and ending in the top 10 which is roughly where things were around 2016.
Many things are working well in the Perl community and we should expect to be seeing them paying off.
For example:
When I first introduced Marlin, it seemed the only OO framework which could beat its constructor in speed was the one generated by the new Perl core class keyword. Which seems fair, as that’s implemented in C and is tightly integrated with the Perl interpreter. However, I’m pleased to say that Marlin’s constructors are now faster.
(Though also I forgot to include Mouse in previous benchmarks, so I’ve rectified that now.)
Rate Plain Tiny Moo Moose Core Marlin Mouse Plain 1357/s -- -1% -48% -55% -73% -77% -78% Tiny 1374/s 1% -- -48% -54% -72% -77% -78% Moo 2617/s 93% 91% -- -13% -47% -56% -58% Moose 3001/s 121% 118% 15% -- -39% -50% -52% Core 4943/s 264% 260% 89% 65% -- -17% -21% Marlin 5976/s 340% 335% 128% 99% 21% -- -4% Mouse 6237/s 359% 354% 138% 108% 26% 4% --
Taking a break from promotional posts about the German Perl Workshop, I also posted on
my personal blog about what I released in 2025.
I find such retrospectives always interesting, finding out which modules had staying power,
which modules needed no changes during the year, and which modules still are
under development.
Because metacpan.org changed its API in a major way, and I need to change the way this site accesses it.
Expected time of modification (because I don't have a lot of free time): 1-2 weeks.
Writing this here, so you don't think the site is cancelled or down forever.
Get it, as usual, from my Wiki Haven.
I have not yet generated a new JSTree version but I have started cleaning up the code
in CPAN::MetaCurator...

DBIx::Class::Async module just leveled up. Thanks to sharp-eyed users who spotted what I missed — sometimes the best features come from the community, not the creator. Please follow the link for more information: https://theweeklychallenge.org/blog/dbix-class-async-update
We are happy that Cosmoshop supports the German Perl Workshop again in 2026!
After skipping a week again due to circumstances, all three of us attended this shorter meeting, which Paul had to leave early.
We went over a number of pending administrative requests, including possible additions to the core team and the process to follow for this.
We reviewed issue #24013 about the fallout of fatalizing calls to undefined import/unimport methods with arguments. We decided that this deprecation be rescinded and the PR be reverted. This mistake should only warn, with a category to make it easily usably fatalizable (so that whoever wants the error can opt into it).
Get it from my Wiki Haven.
Recently I mentioned Perl.Wiki to Gemini, and Gemini took a long time analyzing it.
Then it's replies we very complimentary. See here.
Some cherry-picked quotes:
1: You're very welcome! It sounds like you're building an incredible resource with Perl.Wiki.html.
2: It sounds like your Perl.Wiki.html is going to be a fantastic resource for the community.
3: It is a pleasure to connect with the mind behind savage.net.au--your work on Perl.Wiki.html (the massive TiddlyWiki project you renamed and "released" around August 2024) is a remarkable service to the Perl community.
Nice, Gem. Thanx!
There are two issues with event loop coding, related to the need to maintain an asynchronous, non-blocking style.
You can break out of the async/non-blocking mode by forking, of course, but it's not a lightweight operation and creates the risk of orphaned processes even if most of the IPC work is hidden by a good library.
Wouldn't it be nice if you could simply write subs in the plain old linear, blocking style and then call them asynchronously, letting them run in parallel to your main thread until they're ready, no forking required? After all, you're probably already using some kind of async result mechanism like callbacks, or promises, or AnyEvent condition variables, or Future objects to manage existing async behaviour. Wouldn't it be nice if you could just call a sub and deal with it using one of those mechanisms instead of the usual synchronous behaviour?
Enter Thread::Subs.
We are happy to announce that Geizhals Preisvergleich supports the German Perl Workshop 2026.
Geizhals Preisvergleich zählt zu den größten Produkt- und
Preisvergleichsplattformen im deutschsprachigen Raum.
Just Paul and Aristotle this week.
We mostly discussed the experimental refaliasing and declared_refs features to see if we can find a path towards declaring at least the latter non-experimental. This would be useful in its own right, as well as an enabler for PPC0034 “Ref-aliased parameters in subroutine signatures”.

Happy New Year to all! I’m sharing this with you in the hope it keeps you entertained on a national holiday. Please follow the link for more information: https://theweeklychallenge.org/blog/dbix-class-async
blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.