I found that funny to discover, in a similar way than openCimetiere (which manage a cemetery in a village... serious stuff).
It has an interesting technology juggling, and it won't break anyone's spoon.
I think the underlying campaign is promotion for everyone: for persons that show their values, for the IDE that shows its reach, for linkedin. By elimination (anyone else that is not mentionned in this), the other tools are left in the dust.
the comparison to Duolingo was interesting (advertise your languages, via what you train), but this one is a bit more contreived.
PECL is now in mode with 'No New Package' so it will not gain new entries.
Previously installed packages are still there, and receive updates, though usually, they are moved to PIE instead, as the authors are keeping the up to date. I expect a wind down period, where packages will gradually leave PECL as is, and move to only use PIE.
#[ReturnTypeWillChange] is actually for PHP native interfaces, as they were initialy not enforced, until they were.
It happens to apply to custom methods too. May be static analysis should report such usage, as it is probably a code smell.
😂
I found that funny to discover, in a similar way than openCimetiere (which manage a cemetery in a village... serious stuff). It has an interesting technology juggling, and it won't break anyone's spoon.
I am expecting a lot more attempts at rewriting PHP with AI to make it faster. This is the first, and I find it refreshingly honest.
I think the underlying campaign is promotion for everyone: for persons that show their values, for the IDE that shows its reach, for linkedin. By elimination (anyone else that is not mentionned in this), the other tools are left in the dust.
the comparison to Duolingo was interesting (advertise your languages, via what you train), but this one is a bit more contreived.
Let see where this goes.
PECL is now in mode with 'No New Package' so it will not gain new entries. Previously installed packages are still there, and receive updates, though usually, they are moved to PIE instead, as the authors are keeping the up to date. I expect a wind down period, where packages will gradually leave PECL as is, and move to only use PIE.
The original RFC: https://wiki.php.net/rfc/adopt_pie_deprecate_pecl
Is it working now?
Another source for this info: https://socket.dev/blog/malicious-postinstall-hook-found-across-700-github-repos
PhpCodeArcheology is actually pretty useful !
#[ReturnTypeWillChange] is actually for PHP native interfaces, as they were initialy not enforced, until they were. It happens to apply to custom methods too. May be static analysis should report such usage, as it is probably a code smell.