Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:98024
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.177 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
In-Reply-To: <CAKws9z2x1wz_WA9_XWOjbf-M9m917DN=zWzhXw3JNqdewyL_9g@mail.gmail.com>
References: <CAKws9z2x1wz_WA9_XWOjbf-M9m917DN=zWzhXw3JNqdewyL_9g@mail.gmail.com>
Date: Sun, 29 Jan 2017 19:04:40 +0000
Message-ID: <CAEKnhAFrgh30fj8Hjm-OEOKkdyPkGbYfeSbxci4a9+5sja-c_Q@mail.gmail.com>
To: Scott Arciszewski <scott@paragonie.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=94eb2c03616cfa30020547405e9f
Subject: Re: [PHP-DEV] [RFC] libsodium (PHP 7.2)
From: bukka@php.net (Jakub Zelenka)

--94eb2c03616cfa30020547405e9f
Content-Type: text/plain; charset=UTF-8

Hi,

On Wed, Jan 11, 2017 at 6:22 PM, Scott Arciszewski <scott@paragonie.com>
wrote:

> Hi all,
>
> I'm resurrecting my RFC to add libsodium as a core extension to PHP 7.2.
>
>
I'm still not sure why it needs to be in the core. As I said before, there
are lots of healthy extension that are not in the core and it certainly
doesn't make them less used (e.g. redis, xdebug or mongo driver). At the
end it's all about packaging...

I think libsodium has lots of really good features and it's a very nice
lib. However what makes me a bit uneasy about libsodium is that it's
basically a one dev library which is even clearly visible in here:

https://github.com/jedisct1/libsodium/graphs/contributors

It is certainly a bit more risky to support such lib if it all depends on
on one person rather than a team of developers. I'm not saying that it's
the same but mcrypt used to be also just one developer lib...

Cheers

Jakub

--94eb2c03616cfa30020547405e9f--