Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121069
Date: Fri, 15 Sep 2023 17:54:50 +0200
To: internals@lists.php.net
Message-ID: <20230915175450.61e0b394@platypus>
In-Reply-To: <CANLbj-q0nhwTVarfqdwhSQ7b3gOrEGvZMau6LoN9YCs0VGQwWw@mail.gmail.com>
References: <a7bb8acf-7fcf-f490-ed3b-4e84bb9bb3bb@derickrethans.nl>
	<CAEwRQKaSozjGN+ivfKWV+PC+OJHgFPo+qzGj633-G6cft3H7DQ@mail.gmail.com>
	<CANLbj-q0nhwTVarfqdwhSQ7b3gOrEGvZMau6LoN9YCs0VGQwWw@mail.gmail.com>
Organization: Paheko.cloud
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Proposal to unbundle imap/pspell/oci8 extensions for
 PHP 8.4
From: php@bohwaz.net (BohwaZ)

> Considering the lack of updates from upstream as Derick mentioned,
> lack of OAuth support (which webklex/php-imap supports), and a
> somewhat lackluster documentation for ext-imap in php.net, I think
> unbundling ext-imap (along with the other extensions in the proposal)
> makes sense.

I don't think that OAuth support is an argument, as most providers
don't support OAuth, so the imap package might still be relevant for
people who are not using Google.

Also, the package currently works, IMAP is a stable protocol, maybe
this library is just stable?

I'm not against the removal, but having to rely on user-space libraries
probably means we'll lose some performance over using the C library.

Also, some widely-used libraries like php-imap use it:
https://packagist.org/packages/php-imap/php-imap

Personally I'm using curl for IMAP, as it is more widely available, but
I think removing php-imap might be a bit too early, except if keeping
it does require a lot of time / effort?