My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it
65 points - last Tuesday at 8:53 PM
SourceSander_Marechal
today at 6:56 AM
There is nothing as permanent as a temporary fix that works.
jakeasmith
last Tuesday at 8:58 PM
Author here, happy to answer any questions. I never imagined a polyfill for http_build_url would gain so much traction. After 12 years, deprecating it feels like the right move, especially given the new options from the community and PHP itself.
We used to work together at AOL. Glad to see you on here; I hope you're doing great!
Reading this threw me back to 2014 - how was working for AOL back then?
For a package with that kind of install base, is there a final release that prints the migration options in a deprecation notice? People will find it years from now through old Stack Overflow answers.
The package is marked as abandoned on Packagist [1]
> This package is abandoned and no longer maintained. No replacement package was suggested.
Both adding it as a dependency using composer and installing it from a lockfile results in:
$ composer require jakeasmith/http_build_url
[…]
Package jakeasmith/http_build_url is abandoned, you should avoid using it. No replacement was suggested.
[…]
$ rm -r vendor/
$ composer install
[…]
- Installing jakeasmith/http_build_url (1.0.2): Extracting archive
Package jakeasmith/http_build_url is abandoned, you should avoid using it. No replacement was suggested.
[…]
[1]
https://packagist.org/packages/jakeasmith/http_build_url
Codefrontier
today at 6:42 AM
Love you kept it alive this long
It hasn't been updated in 11 years. Not sure I'd call that "keeping it alive".