Hello, On Mon, Jul 27, 2026 at 11:27 PM Jakub Zelenka <[email protected]> wrote:
> I think this should have not been proposed for deprecation yet. There are > significant users of it and I just didn't have time to properly look into the > issues. So there might be options to get it fixed properly. So I think it > should wait till it's properly investigated. I took a bit of time to actually check what is used, realistically, beyond keywords presence stats. I think there is some data/stats misinterpretation here. Being present in a code base does not automatically mean it is used. For example, Symfony's native http client disable it by default as it fails/failed to work correctly with stream_select, according to the inline comment in https://github.com/symfony/symfony/blob/bb5999123482057647a0831010d14b6b34fe443c/src/Symfony/Component/HttpClient/NativeHttpClient.php#L227 Guzzle and Symfony default to curl too. As curl is optional, I would be surprised if a large majority of users do not have curl. Even more surprised as, it is also a composer required dep. Some SAPIs or php servers like FrankenPHP take over this as well before PHP gets a hand on it. Please correct me here if my memory fails here :) >From a http "end user" perspective, I would rather define that as effectively not used. The only part the deprecation does not address directly is the fopen&co internal usages. I would go with keeping that deprecation, and if anything went off the radar, the major frameworks components will surely, or hopefully, provide the feedback required to revisit this deprecation before RC1. Cheers, -- Pierre @pierrejoye
