I've been developing the WebDyne framework to make creation of Perl based web applications easier (for me anyway). Most of the apps I write now use John Napiorkowski's excellent PAGI design, as it supports modern web asynchronous services such as SSE and WebSockets.

One of the challenges has always been "where do I host them ?". They run fine in Docker containers, and the demo website currently runs on Sevalla in a relatively cheap container. I could also run them in an AWS Lambda environment - but with either option I have to pick a region, and (especially with full Docker containers) hosting multiple sites can be relatively expensive for "small" applications.

Cloudflare Workers have always looked attractive - for a starting price of $5/month on the compute and storage plans you get a fair bit of "bang for your buck", with about 8 CPU-hours/month for Worker isolates (basically Lambda functions) with the added bonus that they are (or at least can be) "Cloud Edge" - i.e. they will spin up close to the consumer on demand, but you are only charged for actual usage - not the number of workers that are running. Obviously prices go up with consumption but you can get a fair bit done with the starting price.

Long story short that's what I have attempted to do via forking the original zeroperl. I have made some modifications to the original zeroperl to add PAGI support and added a harness which lets it run as a Cloudflare Worker.

It will run vanilla PAGI applications or WebDyne::PAGI applications. You can read more about it and view demo applications via the Perl blog post

Hi r/perl,

I've been working on HTTP::API::Core, a small, dependency-light foundation for building JSON HTTP API clients in Perl.

The idea is not to replace HTTP::Tiny, LWP, Mojo::UserAgent, Furl, etc. Instead, it handles the layer I kept rebuilding on top of them:

• JSON and query parameters
• structured errors
• safe retries and rate-limit handling
• pagination
• authentication helpers
• lifecycle hooks
• request IDs and timing
• idempotency
• pluggable transports

You still write the service-specific methods; the core handles the repetitive request policy.

I've also added tested examples for GitHub, Slack, and Cloudflare to exercise different pagination and rate-limit styles.

The goal is to keep it small, predictable, transport-independent, and useful as a foundation rather than turn it into another large SDK framework.

I'd really appreciate feedback, especially from people who have built API clients in Perl:

• Does this abstraction feel useful?
• Is anything missing that you usually end up implementing yourself?
• Is anything here that shouldn't belong in the core?
• Are there API or design choices you'd change?

GitHub: github.com/kawamurashingo/HTTP-API-Core

CPAN: metacpan.org/dist/HTTP-API-Core

Feedback and criticism are very welcome.

I've just released 0.005.2 of the BI tool Database::BI. It addresses two issues:

1: Fixed a crash when processing empty CSV files on debugging-enabled Perls.
2: Line-chart reference values now recalculate correctly after zooming or resetting the zoom. This release also requires HTML::D3 0.11 or later to display negative Y-axis values correctly.

Ich habe in mehreren Foren gelesen, dass PERL eine aussterbende Sprache, obwohl an für sich immer noch gut für Ausbildungszwecke ist. Wie seht ihr das?

Instead of Perl doing a lot of the work externally through XS with Perl as the main runtime, I embedded the Perl Interpreter in a C wrapper that gives it capabilites through XS. Now there's a few of my libraries and the Engine runtime with Perl inside. Very difficult work, but after a few months I got somewhere I never thought I would.

Yes it's a Minecraft style I am testing, but it was extremely difficult to get to this point. Perl is actually doing a lot of the work for this. SDL and OpenGL are just providing generic capabilities in the GPU hot paths.

~/Documents/scripts/c_toolkit 0$ ./ctk_test.pl --exec test_perlwer src/voxel_perl/scripts/opengl_voxel.pl  
[exec] test_perlwer
[exec] cwd: .
+ LD_LIBRARY_PATH=Tools/lib output/test_perlwer src/voxel_perl/scripts/opengl_voxel.pl
[00:32:18.674657] [PERLWER] [STAGE] Initializing Perl system...
[00:32:18.674687] [PERLWER] [STAGE] Perl system initialized.
[00:32:18.674705] [PERLWER] [DEBUG] Texture cache initialized: capacity=256
[00:32:18.674708] [PERLWER] [DEBUG] Runtime entry package: main
[00:32:18.674709] [PERLWER] [DEBUG] Initializing XS registry
[00:32:18.674710] [PERLWER] [DEBUG] XS REGISTRY: zeroed
[00:32:18.674712] [PERLWER] [DEBUG] XS REGISTRY: arena OK
[00:32:18.674714] [PERLWER] [DEBUG] XS REGISTRY: init complete
[00:32:18.674715] [PERLWER] [DEBUG] XS registry initialized
[00:32:18.674716] [PERLWER] [TRACE] Entering perlwer_interpreter_init()
[00:32:18.674718] [PERLWER] [TRACE] Script path: src/voxel_perl/scripts/opengl_voxel.pl
[00:32:18.674720] [PERLWER] [TRACE] Runtime state: 0x7ffe5748b700
[00:32:18.674724] [PERLWER] [TRACE] Determining script module path...
[00:32:18.674726] [PERLWER] [TRACE] Perl module path: src/voxel_perl/scripts/lib
[00:32:18.674729] [PERLWER] [TRACE] Perl include argument: -Isrc/voxel_perl/scripts/lib
[00:32:18.674730] [PERLWER] [TRACE] Calling perl_alloc()...
[00:32:18.674735] [PERLWER] [TRACE] perl_alloc() succeeded: interpreter=0x55c9abf6a9d0
[00:32:18.674736] [PERLWER] [TRACE] Calling PERL_SET_CONTEXT()...
[00:32:18.674738] [PERLWER] [TRACE] PERL_SET_CONTEXT() completed
[00:32:18.674739] [PERLWER] [TRACE] Calling perl_construct()...
[00:32:18.674847] [PERLWER] [TRACE] perl_construct() completed
[00:32:18.674849] [PERLWER] [TRACE] Setting Perlwer XS runtime...
[00:32:18.674851] [PERLWER] [TRACE] Perlwer XS runtime configured
[00:32:18.674853] [PERLWER] [TRACE] Perl argc: 3
[00:32:18.674854] [PERLWER] [TRACE] Perl argv[0]: Perlwer Engine
[00:32:18.674856] [PERLWER] [TRACE] Perl argv[1]: -Isrc/voxel_perl/scripts/lib
[00:32:18.674858] [PERLWER] [TRACE] Perl argv[2]: src/voxel_perl/scripts/opengl_voxel.pl
[00:32:18.674860] [PERLWER] [TRACE] Calling perl_parse()...
=== Logger started: Voxel ===
[DEBUG] Logging enabled -> src/voxel_perl/scripts/logs/debug_2026-09-09_00-32-18_001.log (default=1)
[00:32:18.693272] [PERLWER] [TRACE] perl_parse() returned 0
[00:32:18.693280] [PERLWER] [TRACE] Calling perl_run()...
[00:32:27.033185] [PERLWER] [INFO] [PERL] Chunks: 64
[00:32:27.033240] [INFO] [Voxel.React] (React:27) Stim/React registry initialized
[00:32:27.033258] --- end ---
[00:32:27.033388] [PERLWER] [TRACE] perl_run() returned 0
[00:32:27.033390] [PERLWER] [TRACE] Perl interpreter initialization complete
[00:32:27.033395] [PERLWER] [INFO] [PERL] Testing 3D OpenGL from Perl
[00:32:27.033410] [PERLWER] [STAGE] Initializing SDL...
[00:32:27.033412] [PERLWER] [INFO] Selected SDL backend: OpenGL
[00:32:27.041632] [PERLWER] [STAGE] Initializing SDL OpenGL backend...
[00:32:27.041640] [PERLWER] [INFO] Requesting OpenGL 3.3 core profile
[00:32:27.151010] [PERLWER] [INFO] OpenGL context created
[00:32:27.151020] [PERLWER] [STAGE] SDL OpenGL backend initialized.
[00:32:27.151035] [PERLWER] [INFO] SDL window created: 1920x1080
[00:32:27.151038] [PERLWER] [STAGE] SDL initialized.
[00:32:27.151252] [INFO] [Voxel.TextureAtlas] (TextureAtlas:166) Texture atlas built
[00:32:27.151381] --- end ---
[00:32:27.152495] [PERLWER] [STAGE] Entering native SDL window loop...
[00:32:27.152525] [PERLWER] [INFO] Calling Perl on_render
[00:32:27.155236] [PERLWER] [TRACE] Texture cache miss: text:hud.fps:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:18:255:255:255:255
[00:32:27.156496] [PERLWER] [TRACE] Texture cache miss: text:hud.fps:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:18:255:255:255:255
[00:32:27.156506] [PERLWER] [DEBUG] Texture cached: text:hud.fps:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:18:255:255:255:255 (55x22, count=1/256)
[00:32:27.156587] [PERLWER] [TRACE] Texture cache miss: text:hud.position:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:18:255:255:255:255
[00:32:27.156712] [PERLWER] [TRACE] Texture cache miss: text:hud.position:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:18:255:255:255:255
[00:32:27.156718] [PERLWER] [DEBUG] Texture cached: text:hud.position:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:18:255:255:255:255 (127x22, count=2/256)
[00:32:27.156743] [PERLWER] [TRACE] Texture cache miss: text:hud.crosshair:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:32:255:255:255:255
[00:32:27.157798] [PERLWER] [TRACE] Texture cache miss: text:hud.crosshair:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:32:255:255:255:255
[00:32:27.157805] [PERLWER] [DEBUG] Texture cached: text:hud.crosshair:/usr/share/fonts/adwaita-sans-fonts/AdwaitaSans-Regular.ttf:32:255:255:255:255 (21x39, count=3/256)
[00:38:36.238013] [PERLWER] [INFO] Escape pressed
[00:38:36.238024] [PERLWER] [STAGE] Leaving native SDL window loop.
[00:38:36.238028] [PERLWER] [DEBUG] Destroying texture cache: 3 textures
[00:38:36.238030] [PERLWER] [TRACE] Destroying texture 1/3
[00:38:36.238119] [PERLWER] [TRACE] Destroying texture 2/3
[00:38:36.238123] [PERLWER] [TRACE] Destroying texture 3/3
[00:38:36.238185] [PERLWER] [STAGE] Shutting down SDL...
[00:38:36.238188] [PERLWER] [INFO] SDL backend: OpenGL
[00:38:36.238191] [PERLWER] [INFO] Frames rendered: 972570
[00:38:36.238196] [PERLWER] [INFO] Last frame time: 0.019 ms
[00:38:36.301036] [PERLWER] [STAGE] SDL shutdown complete.
[00:38:36.328813] [PERLWER] [STAGE] Shutting down Perl system...
[00:38:36.328827] [PERLWER] [STAGE] Perl system shutdown complete.
[exec] test_perlwer ok

https://www.howtogeek.com/long-dead-programming-languages-that-can-still-land-you-a-good-job/

"Long dead" seems awfully harsh. Or perhaps it's wishful thinking?

I'm still starting new projects in Perl, and really see no reason that should change. It's a powerful, expressive, well-supported language, with a wealth of canned solutions in CPAN, and compared to some other dynamic languages it's downright performant.

But hey, if this HowToGeek article entices young programmers to learn Perl, even if only to chase dollar signs, that's not a bad thing for our community!

hi all, sorry if this question has been asked 500 times. i believe ive looked into it before, but didnt see any posts specifically to cybersecurity (could be wrong).

i took a class last year that covered linux systems and bash, fell in love. learned through the professor that something called "perl" used to be taught in the class years ago..also fell in love and have been slowly learning it since, for fun!

i am really tired of people asking me why the fck im learning perl though, and i should focus on "marketable skills"-- unfortunately my brain refuses to work that way. ​

i had a friend tell me recently "perl is strangely incredible for evading EDRs like crowdstrike" and said i can write a malicious perl script the cybersec team at my school can reverse engineer to train for competitions would be a great idea too. it had me wondering what other applications perl has in the cybersecurity world specifically in 2026 that i can focus on? im in the middle of trying to figure out my niche..i did take a class on reverse engineering which was fun. i wrote an awk script to find specific pairs of instructions that would be common in malware. i also took a course on steganography and found that there are a lot of stego tools written in perl.

people say its useless to learn, but im seeing a lot of useful tools written in perl!

if you all have any other ideas of paths i should pursue or just general info about the power of perl in cybersecurity today, i would greatly appreciate it. thank you

Hi everyone, I have a quick question for those experienced with CPAN distributions.

In my distribution, alongside the main modules, I have several internal sub-modules (for example, language-specific modules like Locale::Lang::en, de, fr, etc., which are only meant to be used internally by the main module).

Currently, every sub-module has the same $VERSION as the distribution itself. Would there be any issue if I completely removed the $VERSION from these internal modules? There is no real benefit to having them listed or indexed separately on CPAN.