Transpiling dragonmantank/cron-expression from PHP to JS: timezones, DST, PHP date formats, and a cache for Intl.DateTimeFormat
https://t.co/QXGXlOdoQ9
@developedbyjosh@laravelphp@vuejs@inertiajs@nuxt_js Looks solid. Curious how teams using setups like this think about the long-term path, staying on Laravel forever or eventually moving the backend to Node to be on JS E2E.
Part 1 looked at the people you can hire to write PHP. Part 2 looks at the architecture they would inherit on day one. PHP's defining choice, shared-nothing process-per-request, was the right answer for the 2005 web. In 2026 it is a structural tax that the rest of the stack has stopped paying.
https://t.co/IvdofSejL6
A recap of what shipped during the week of 27 April. Six items this week: a complete audit of the math module against every PHP version since 4, two more Pure Utilities packages converted at 100%, a deep analysis of string literal encodings, an experimental TypeScript output mode in the transpiler, and initial support for static variables inside functions.
https://t.co/699BR2n18S
Everyone asks if AI killed our PHP-to-JS transpiler.
Wrong question. AI canβt migrate a PHP codebase. Not because itβs not smart enough, because itβs solving the wrong problem.
Hereβs what we learned building Pext for 3 years
The mental model:
β’ Migration = mechanical, must be correct, deterministic transpiler
β’ Improvement = creative, can be iterative, AI
Using AI for migration is asking it to do the hard part without the foundation. Using it for improvement is using it where itβs strongest.
Pext's math module reached full PHP parity this week. That label means something specific: every public function, every constant, the new RoundingMode enum, on every PHP version from 4 forward, with every documented edge case checked. The road there ran through the gaps between JavaScript's Math, IEEE 754, C99, and twenty years of PHP compatibility decisions. This post walks through the parts worth knowing about.
https://t.co/iOOX1slwQb