a mostly about the Internet blog by

Fastmail Donates USD 10,000 to The Perl and Raku Foundation

Furnished content.

2025 was a tough year for The Perl and Raku Foundation (TPRF). Funds were sorely needed. The community grants program had been paused due to budget constraints and we were in danger of needing to pause the Perl 5 core maintenance grants. Fastmail stepped up with a USD 10,000 donation and helped TPRF to continue to support Perl 5 core maintenance. Ricardo Signes explains why Fastmail helped keep this very important work on track.

Perl has served us quite well since Fastmail’s inception. We’ve built up a large code base that has continued to work, grow, and improve over twenty years. We’ve stuck with Perl because Perl stuck with us: it kept working and growing and improving, and very rarely did those improvements require us to stop the world and adapt to onerous changes. We know that kind of stability is, in part, a function of the developers of Perl, whose time is spent figuring out how to make Perl better without also making it worse. The money we give toward those efforts is well-spent, because it keeps the improvements coming and the language reliable. Ricardo Signes, Director & Chief Developer Experience Officer, Fastmail

One of the reasons that you don’t hear about Perl in the headlines is its reliability. Upgrading your Perl from one version to the next? That can be a very boring deployment. You code worked before and it continues to “just work” after the upgrade. You don’t need to rant about short deprecation cycles, performance degradation or dependencies which no longer install. The Perl 5 core maintainers take great care to ensure that you don’t have to care very much about upgrading your Perl. Backwards compatibility is top of mind. If your deployment is boring, it’s because a lot of care and attention has been given to this matter by the people who love Perl and love to work on it.As we moved to secure TPRF’s 2025 budget, we reached out to organizations which rely on Perl. A number of these companies immediately offered to help. Fastmail has already been a supporter of TPRF for quite some time. In addition to this much needed donation, Fastmail has been providing rock solid free email hosting to the foundation for many years.While Fastmail’s donation has been allocated towards Perl 5 Core maintenance, TPRF is now in the position to re-open the community grants program, funding it with USD 10,000 for 2026. There is also an opportunity to increase the community grants funding if sponsor participation increases. As we begin our 2026 fundraising, we are looking to cast a wider net and bring more sponsor organizations on board to help support healthy Perl and Raku ecosystems.Maybe your organization will be the one to help us double our community grants budget in 2026. To become a sponsor, contact:olaf@perlfoundation.org

Read more here

posted at: 12:00am on 05-Feb-2026
path: /Programming/Perl | permalink | edit (requires password)

0 comments, click here to add the first

Cast-Iron Community: Your Chance to Sponsor TPRC 2026

Furnished content.

“Perl is my cast-iron pan - reliable, versatile, durable, and continues to beever so useful.” TPRC 2026 brings together acommunity that embodies all of these qualities, and we’re looking for sponsorsto help make this special gathering possible.

About the Conference

The Perl and Raku Conference 2026 is acommunity-organized gathering of developers, enthusiasts, and industryprofessionals. It takes place from June 26-28, 2026, in Greenville, South Carolina.The conference will feature an intimate, single-track format that promises high sponsor visibility.We look forward to approximately 80 participants with some of those staying in town for the shoulder days (June 25-29) and a Mondayworkshop.

Give back to the language and communities which have already given so much to you
Connect with the developers and craftspeople who build your tools – the ones that are built to last
Help to ensure that The Perl and Raku Foundation can continue to fund Perl 5 core maintenance and Community Grants

Sponsorship Tiers

Only 1 sponsorship is available at this level
Premium logo placement on conference website
This donation qualifies your organization to be a Bronze Level Sponsor of The Perl and Raku Foundation
5-minute speaking slot during opening ceremony
2 complimentary conference passes
Priority choice of rollup banner placement
Logo prominently displayed on conference badges
First choice of major named sponsorship (Conference Dinner, T-shirts, or Swag Bags)
Logo on main stage backdrop and conference banners
Social media promotion
All benefits of lower tiers

Logo on all conference materials
One complimentary conference pass
Rollup banner on display
Choice of named sponsorship (Lunch or Snacks)
Logo on backdrop and banners
Dedicated social media recognition
All benefits of lower tiers

Logo on conference website
Logo on backdrop and banners
Choice of smaller named sponsorship (Beverage Bars)
Social media mention
All benefits of lower tier

Name/logo on conference website
Name/logo on backdrop and banners

All Sponsors Receive

Logo/name in Update::Daily conference newsletter sidebar
Opportunity to provide materials for conference swag bags
Recognition during opening and closing ceremonies
Listed on conference website sponsor page
Mentioned in conference social media

Named Sponsorship Opportunities

Exclusive naming rights available for:

Conference Dinner ($2,000) - Signage on tables and buffet
Conference Swag Bags ($1,500) - Logo on bags
Conference T-Shirts ($1,500) - Logo on sleeve
Lunches ($1,500) - Signage at pickup and on menu tickets
Snacks ($1,000) - Signage at snack bar
Update::Daily Printing ($200) - Logo on masthead

About The Perl and Raku Foundation

Proceeds beyond conference expenses support The Perl and Raku Foundation, a non-profit organization dedicated to advancing the Perl and Raku programming languages through open source development, education, and community building.

Contact Information

For more information on how to become a sponsor, please contact:olaf@perlfoundation.org

Read more here

posted at: 12:00am on 04-Feb-2026
path: /Programming/Perl | permalink | edit (requires password)

0 comments, click here to add the first

Podlite comes to Perl: a lightweight block-based markup language for everyday use

Furnished content.

My name is Alex. Over the last years I've implemented several versions of the Raku’s documentation format (Synopsys 26 / Raku’s Pod) in Perl and JavaScript.At an early stage, I shared the idea of creating a lightweight version of Raku’s Pod, with Damian Conway, the original author of the Synopsys 26 Documentation specification (S26).He was supportive of the concept and offered several valuable insights that helped shape the vision of what later became Podlite.Today, Podlite is a small block-based markup language that is easy to read as plain text, simple to parse, and flexible enough to be used everywhere in code, notes, technical documents, long-form writing, and even full documentation systems.This article is an introduction for the Perl community what Podlite is, how it looks, how you can already use it in Perl via a source filter, and what's coming next.

The Block Structure of Podlite

One of the core ideas behind Podlite is its consistent block-based structure.Every meaningful element of a document a heading, a paragraph, a list item, a table, a code block, a callout is represented as a block. This makes documents both readable for humans and predictable for tools.Podlite supports three interchangeable block styles: delimited, paragraph, and abbreviated.

Abbreviated blocks (`=BLOCK`)

This is the most compact form.A block starts with = followed by the block name.

=head1 Installation Guide=item Perl 5.8 or newer=para This tool automates the process.

ends on the next directive or a blank line
best used for simple one-line blocks
cannot include configuration options (attributes)

Paragraph blocks (`=for BLOCK`)

Use this form when you want a multi-line block or need attributes.

=for code :lang<perl>say "Hello from Podlite!";

ends when a blank line appears
can include complex content
allows attributes such as :lang, :id, :caption, :nested,

Delimited blocks (`=begin BLOCK` `=end BLOCK`)

The most expressive form. Useful for large sections, nested blocks, or structures that require clarity.

=begin nested :notify<important>Make sure you have administrator privileges.=end nested

explicit start and end markers
perfect for code, lists, tables, notifications, markdown, formulas
can contain other blocks, including nested ones

These block styles differ in syntax convenience, but all produce the same internal structure. diagram here showing the three block styles and how they map to the same internal structure

diagram here showing the three block styles and how they map to the same internal structure

Regardless of which syntax you choose:

all three forms represent the same block type
attributes apply the same way (:lang, :caption, :id, )
tools and renderers treat them uniformly
nested blocks work identically
you can freely mix styles inside a document

Example: Comparing POD and Podlite

Let’s see how the same document looks in traditional POD versus Podlite: POD vs Podlite

Each block has clear boundaries, so you don’t need blank lines between them. This makes your documentation more compact and easier to read.This is one of the reasons Podlite remains compact yet powerful:the syntax stays flexible, while the underlying document model stays clean and consistent.This Podlite example rendered as on the following screen:

Inside the Podlite Specification 1.0

One important point about Podlite is that it is first and foremost a specification.It does not belong to any particular programming language, platform, or tooling ecosystem.The specification defines the document model, syntax rules, and semantics.From the Podlite 1.0 specification, notable features include:

headings (=head1, =head2, )
lists and definition lists, and including task lists
tables (simple and advanced)
CSV-backed tables
callouts / notifications (=nested :notify<tip|warning|important|note|caution>)
table of contents (=toc)
includes (=include)
embedded data (=data)
pictures (=picture and inline P<>)
formulas (=formula and inline F<>)
user defined blocks and markup codes
Markdown integration

The =markdown block is part of the standard block set defined by the Podlite Specification 1.0.This means Markdown is not an add-on or optional plugin it is a fully integrated, first-class component of the language.Markdown content becomes part of Podlite's unified document structure, and its headings merge naturally with Podlite headings inside the TOC and document outline.Below is a screenshot showing how Markdown inside Perl is rendered in the in-development VS Code extension, demonstrating both the block structure and live preview: Podlite source, including =markdown block

Podlite source, including =markdown block

Using Podlite in Perl via the source filter

To make Podlite directly usable in Perl code, there is a module on CPAN:Podlite Use Podlite markup language in Perl programsA minimal example could look like this:

use Podlite; # enable Podlite blocks inside Perl=head1 Quick Example=begin markdownPodlite can live inside your Perl programs.=end markdownprint "Podlite active\n";

Roadmap: what’s next for Podlite

Podlite continues to grow, and the Specification 1.0 is only the beginning.Several areas are already in active development, and more will evolve with community feedback.Some of the things currently planned or in progress:

CLI tools
- command-line utilities for converting Podlite to HTML, PDF, man pages, etc.
- improve pipelines for building documentation sites from Podlite sources
VS Code integration
Ecosystem growth
- develop comprehensive documentation and tutorials
- community-driven block types and conventions

If this resonates with you, I'd be very happy to hear from you:

ideas for useful block types
suggestions for tools or integrations
feedback on the syntax and specification

https://github.com/podlite/podlite-specs/discussionsEven small contributions a comment, a GitHub star, or trying an early tool help shape the future of the specification and encourage further development.Useful links:

CPAN: https://metacpan.org/pod/Podlite
GitHub:https://github.com/podlite
Specification
- (HTML): https://podlite.org/specification
- source: https://github.com/podlite/podlite-specs
Project site: https://podlite.org
Roadmap: https://podlite.org/#Roadmap

Thanks for reading,Alex

Read more here

posted at: 12:00am on 28-Jan-2026
path: /Programming/Perl | permalink | edit (requires password)

0 comments, click here to add the first

Announcing the Perl Toolchain Summit 2026

Furnished content.

Announcing the Perl Toolchain Summit 2026!

The organizers have been working behind the scenes since last September,and today Im happy to announce that the 16th Perl Toolchain Summit willbe held in Vienna, Austria, from Thursday April 23rd till Sunday April26th, 2026.This post is brought to you by Simplelists, a group email andmailing list service provider, and a recurring sponsor of the PerlToolchain Summit.

Started in 2008 as the Perl QA Hackathon in Oslo, the Perl ToolchainSummit is an annual event that brings together the key developersworking on the Perl toolchain. Each year (except for 2020-2022), theevent moves from country to country all over Europe, organised by localteams of volunteers. The surplus money from previous summits helps fundthe next one.Since 2023, the organizing team is formally split between a globalteam and a local team (although this setup has been informallyused before).The global team is made up of veteran PTS organizers, who deal withinvitations, finding sponsors, paying bills and communications. They areLaurent Boivin (ELBEHO), PhilippeBruhat (BOOK), Thibault Duponchelle(CONTRA), Tina Mller(TINITA) and Breno de Oliveira(GARU), supported by Les Mongueursde Perls bank account.The local team members for this year have organized several events inVienna (including the Perl QA Hackathon 2010!) and deal with finding thevenue, the hotel, the catering and welcoming our attendees in Vienna inApril. They are Alexander Hartmaier(ABRAXXA), Thomas Klausner(DOMM), Maro Kollr(MAROS), Michael Krll and HelmutWollmersdorfer (WOLLMERS).The developers who maintain CPAN and associated tools and services areall volunteers, scattered across the globe. This event is the one timein the year when they can get together.The summit provides dedicated time to work on the critical systems andtools, with all the right people in the same room. The attendees hammerout solutions to thorny problems and discuss new ideas to keep thetoolchain moving forward. This year, about 40 people have been invited,with 35 participants expected to join us in Vienna.If you want to find out more about the work being done at the ToolchainSummit, and hear the teams and people involved, you can listen toseveral episodes of The Underbar podcast,which were recorded during the 2025 edition in Leipzig, Germany:

Given the important nature of the attendees work and their volunteerstatus, we try to pay for most expenses (travel, lodging, food, etc.)through sponsorship. If youre interested in helping sponsor the summit,please get in touch with the global team atpts2026@perltoolchainsummit.org.Simplelists has been sponsoring the Perl Toolchain Summit for severalyears now. We are very grateful for their continued support.

Simplelists is proud to sponsor the 2026 Perl Toolchain Summit, as Perlforms the core of our technology stack. We are grateful that we can relyon the robust and comprehensive Perl ecosystem, from the core of Perlitself to a whole myriad of CPAN modules. We are glad that the PTScontinues its unsung work, ensuring that Simplelists can continue torely on these many tools.

About the Conference

Why Sponsor?

Sponsorship Tiers

Platinum Sponsor ($6,000)

Gold Sponsor ($4,000)

Silver Sponsor ($2,000)

Bronze Sponsor ($1,000)

All Sponsors Receive

Named Sponsorship Opportunities

About The Perl and Raku Foundation

Contact Information

The Block Structure of Podlite

Abbreviated blocks (=BLOCK)

Paragraph blocks (=for BLOCK)

Delimited blocks (=begin BLOCK =end BLOCK)

Example: Comparing POD and Podlite

Inside the Podlite Specification 1.0

Using Podlite in Perl via the source filter

Roadmap: what’s next for Podlite

Try Podlite and share feedback

Announcing the Perl Toolchain Summit 2026!

Abbreviated blocks (`=BLOCK`)

Paragraph blocks (`=for BLOCK`)

Delimited blocks (`=begin BLOCK` `=end BLOCK`)