Meta tags:
description=Hand-curated PHP reading for developers who value signal over noise.;

Headings (most frequently used words):

php, the, to, in, no, behind, rust, excellent, writing, hand, picked, buzzwords, ads, nonsense, curated, by, stefan, priebsch, and, sebastian, bergmann, of, thephp, cc, as, free, service, community, structures, software, who, do, talk, rewriting, reflection, with, immutable, versions, on, packagist, staying, control, rebuilding, tcpdf, after, 25, years, trying, port, psalm, running, coding, agents, sandbox, work, what, foundation, delivered, 2025, case, against, erased, generics, exploring, friend, classes, for,

Text of the page (most frequently used words):
the (40), and (27), php (24), how (12), picked (10), #sebastian (10), stefan (10), this (7), bergmann (7), #priebsch (7), for (7), not (6), that (6), issue (6), code (5), generics (5), foundation (5), rss (5), our (5), rust (5), has (5), about (4), 2026 (4), but (4), work (4), without (4), with (4), dev (4), static (4), analysis (4), tools (4), its (4), feed (4), coding (4), one (4), sandbox (4), into (4), psalm (4), library (4), thephp (3), article (3), language (3), contributions (3), community (3), could (3), support (3), friend (3), classes (3), making (3), scherzer (3), case (3), runtime (3), visible (3), what (3), are (3), behind (3), agents (3), can (3), step (3), project (3), com (3), llm (3), after (3), years (3), software (3), version (3), versions (3), immutable (3), packagist (3), people (3), ben (3), archive (2), selected (2), because (2), evolves (2), through (2), author (2), access (2), them (2), examines (2), clear (2), than (2), their (2), issues (2), core (2), erased (2), type (2), makes (2), introducing (2), instead (2), report (2), development (2), funding (2), year (2), 2025 (2), transparency (2), from (2), matter (2), must (2), change (2), way (2), agent (2), get (2), working (2), matt (2), test (2), suite (2), rewrite (2), been (2), original (2), port (2), tool (2), nicola (2), asuni (2), many (2), tcpdf (2), rebuilt (2), control (2), july (2), stable (2), daniel (2), implementation (2), reflection (2), existing (2), line (2), does (2), contribute (2), ramsey (2), structures (2), latest (2), curated (2), writing (2), privacy, imprint, suggest, post, importance, feature, itself, demonstrates, explores, allowing, private, protected, members, public, compares, attribute, based, approach, class, level, syntax, semantic, problems, each, option, introduces, exploring, treating, design, problem, rather, leaving, semantics, offers, counterpoint, position, featured, two, ago, developer, gina, banyard, argues, conflict, established, system, depend, too, heavily, optional, she, incrementally, checked, against, gpb, moe, contribution, gives, useful, detail, used, significant, which, marked, thirtieth, anniversary, helped, deliver, released, pie, began, modernizing, streams, layer, accounted, roughly, commits, impact, details, 730, 534, were, collected, spent, delivered, surface, these, articles, together, they, reveal, something, broader, institutional, careful, debate, across, june, capable, become, thing, charge, own, machines, using, helps, keep, let, autonomously, giving, full, machine, locks, shows, database, included, inside, running, einenlum, writes, honestly, got, right, where, had, himself, would, have, gamble, brown, creator, wanted, know, whether, his, mostly, months, iteration, hefty, token, bill, pzoom, runs, ten, times, faster, passes, almost, entire, trying, mattbrown, few, maintainers, reflect, quarter, century, much, world, depends, done, yet, kind, dedication, deserves, gratitude, looks, back, history, pdf, generation, started, workaround, commerce, ended, projects, continuing, patch, everything, scratch, rebuilding, tecnick, features, maintainer, ported, locked, different, stories, common, thread, developers, stay, staying, number, identify, body, forever, removes, ambiguity, users, security, processes, made, metadata, once, published, git, reference, longer, silently, changed, while, deleted, remain, explanation, actions, such, blocked, retags, recorded, log, blog, valuable, even, when, never, intended, replace, experiment, produced, deeper, understanding, current, rewrote, extension, learning, exercise, examining, uncovered, eighteen, old, bug, missing, validation, documentation, errors, opportunities, simplify, optimize, rewriting, lack, willing, lacks, paths, proposal, interesting, starting, point, further, discussion, eager, always, give, place, begin, proposes, chartered, groups, make, responsibilities, membership, communication, decision, explicit, new, hierarchy, who, talk, shaped, only, write, around, find, deeply, understand, implementations, guarantees, infrastructure, provides, ecosystem, organizing, continued, view, all, buzzwords, ads, nonsense, free, service, excellent, hand, why, reads, worth, your, time,

Text of the page (random words):
php reads curated php writing worth your time latest archive why about rss excellent php writing hand picked no buzzwords no ads no nonsense curated by stefan priebsch and sebastian bergmann of thephp cc as a free service to the php community rss feed latest issue view all issues rss feed issue 16 the structures behind the software 14 july 2026 software is shaped not only by the code we write but by the structures around it how people find their way into a project how deeply we understand existing implementations and what guarantees our infrastructure provides this issue examines how the php ecosystem is organizing its continued development stefan sebastian ben ramsey dev who do i talk to php has people eager to contribute but it does not always give them a clear place to begin ben ramsey proposes chartered working groups that make responsibilities membership communication and decision making explicit without introducing a new hierarchy picked by stefan priebsch php does not lack people willing to contribute it lacks visible paths into the work ben s proposal is an interesting starting point for further discussion scherzer dev rewriting reflection with rust daniel scherzer rewrote php s reflection extension in rust as a learning exercise examining the existing implementation line by line uncovered an eighteen year old bug missing type validation documentation errors and opportunities to simplify and optimize the c code picked by sebastian bergmann a rewrite can be valuable even when it is never intended to replace the original daniel s experiment produced a deeper understanding of the current implementation blog packagist com immutable versions on packagist packagist has made stable version metadata immutable once a version has been published the git reference behind it can no longer be silently changed while deleted versions remain visible with an explanation and actions such as blocked retags are recorded in a transparency log picked by stefan priebsch and sebastian bergmann a version number must identify one body of code forever making stable versions immutable removes ambiguity for users tools and security processes rss feed issue 15 staying in control 7 july 2026 this issue features a library rebuilt by its maintainer after 25 years a static analysis tool ported to rust by an llm and a coding agent locked into a sandbox different stories one common thread no matter how our tools change we developers stay in control stefan sebastian tecnick com rebuilding tcpdf after 25 years nicola asuni looks back on the history of tcpdf the pdf generation library that started as a workaround in an e commerce project and ended up many software projects instead of continuing to patch the code he has rebuilt everything from scratch picked by stefan priebsch few maintainers get to reflect on a quarter century of one library nicola asuni has many years on a library that much of the php world depends on and he is not done yet that kind of dedication deserves our gratitude and support mattbrown dev trying to port psalm to rust matt brown the original creator of psalm wanted to know whether an llm could port his static analysis tool to rust it could mostly after months of iteration and a hefty token bill pzoom runs ten times faster than psalm and passes almost the entire test suite picked by sebastian bergmann matt writes honestly about what the llm got right and where he had to step in himself without psalm s test suite this rewrite would have been a gamble einenlum com running coding agents in a sandbox how can we let coding agents work autonomously but without giving it full access to our machine the author of this article locks the agent into a sandbox and shows step by step how to get a php project database included working inside it picked by stefan priebsch and sebastian bergmann no matter how capable coding agents become one thing must not change we are in charge of our own machines using a sandbox helps us to keep it that way rss feed issue 14 the work behind php 23 june 2026 on the surface these articles are about funding generics and friend classes together they reveal something broader how php evolves through institutional support careful debate and contributions from across the community stefan sebastian thephp foundation what the php foundation delivered in 2025 in a significant year for php which marked its thirtieth anniversary the php foundation helped deliver php 8 5 released pie 1 0 began modernizing the streams layer and accounted for roughly 42 of php core commits the foundation s 2025 impact and transparency report details how 730 534 in contributions were collected and spent picked by stefan priebsch this report makes the foundation s contribution to php s development visible and gives useful detail on how its funding is used gpb moe the case against erased generics in php php core developer gina banyard argues that runtime erased generics conflict with php s established runtime type system and depend too heavily on optional static analysis tools she makes the case for incrementally introducing runtime checked generics instead picked by sebastian bergmann a clear case for treating generics as a language design problem rather than leaving their semantics to static analysis tools this article offers the counterpoint to the position we featured two issues ago scherzer dev exploring friend classes for php the author explores how php could support friend classes allowing selected code to access private or protected members without making them public he compares an attribute based approach with class level language syntax and examines the semantic problems each option introduces picked by stefan priebsch and sebastian bergmann we selected this article not because of the importance of the feature itself but because it demonstrates how the language evolves through the work and contributions of the php community 2026 thephp cc about archive suggest a post imprint privacy