Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:99148
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.66 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <c8bfba41-d490-a08f-ceb4-aab3d47ea9e3@rhsoft.net>
References: <e71637c6-db4a-7f29-ae08-89625eae8b53@fleshgrinder.com>
 <CA+kxMuTV7p14HbDpEQrwJKG3soUgxXV5BEs6WHgPtSOmjc2grQ@mail.gmail.com>
 <f9c91d81-097b-680e-904a-126ffee16b19@rhsoft.net> <ba50cf2d-6744-e78f-18be-e1d65990f0d9@garfieldtech.com>
 <CAFMT4NpNmkpfcWXsMydxDbULV9iNTe9BJxYdFdHdD1H36P1p6w@mail.gmail.com> <c8bfba41-d490-a08f-ceb4-aab3d47ea9e3@rhsoft.net>
Date: Wed, 24 May 2017 09:57:01 -0600
Message-ID: <CAFMT4NoiD-9tPt1_pJXTmpX1tN9FdSe01TmQyaz8kAQotdaVtw@mail.gmail.com>
To: "lists@rhsoft.net" <lists@rhsoft.net>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c118994a84baf0550472793"
Subject: Re: [PHP-DEV] [RFC] [Discussion] UUID
From: levim@php.net (Levi Morrison)

--94eb2c118994a84baf0550472793
Content-Type: text/plain; charset="UTF-8"

On Wed, May 24, 2017 at 9:29 AM, lists@rhsoft.net <lists@rhsoft.net> wrote:

>
>
> Am 24.05.2017 um 17:11 schrieb Levi Morrison:
>
>> On Wed, May 24, 2017 at 9:04 AM, Larry Garfield <larry@garfieldtech.com>
>> wrote:
>>
>> On 05/24/2017 04:31 AM, lists@rhsoft.net wrote:
>>>
>>>>
>>>> Am 24.05.2017 um 11:27 schrieb Dan Ackroyd:
>>>>
>>>> Hey internals!
>>>>>
>>>>>>
>>>>>> I haven't written the RFC yet,
>>>>>>
>>>>>
>>>>> Please don't forget to include in the RFC a justification for why this
>>>>> should be part of PHP core, rather than a library
>>>>>
>>>>
>>>> because as developer in reality you can not use and rely on features
>>>> which needs to install some pecl-library when it is supposed to be used
>>>> on
>>>> typical hosting packages
>>>>
>>>
>>> It doesn't have to be a PECL library.  I agree that a project requiring a
>>> PECL library greatly limits its potential reach, but with Composer
>>> user-space libraries are totally easy to install. There's a nice and
>>> popular UUID implementation already:
>>>
>>> https://packagist.org/packages/ramsey/uuid
>>>
>>> Note: That doesn't mean adding UUID functionality to PHP core/standard
>>> lib
>>> is a bad idea; discussing that is fine.  But the "no one will be able to
>>> use it otherwise" argument is substantially less compelling than it was
>>> even 5 years ago.
>>>
>>> By the way there already is a PECL package for a UUID library:
>> https://pecl.php.net/package/uuid. I would like to see compelling reasons
>> why we shouldn't rally around that package
>>
> because when you end in a library/extension for each and every trivial
> function your codebase becomes a mess - why not PECL i have explained
> before the post you quoted and why composer as it is working nwo is a no-go
> in the follow-up response
>

You misunderstood my message. Why would we write a new UUID package written
in C when there is already a UUID package in PECL? Why is the existing UUID
package in PECL is insufficient?

I understand the user experience improvement for having a package for UUIDs
in core; I'd like that myself. I just want to know why we haven't discussed
the existing UUID package and made a new one.

--94eb2c118994a84baf0550472793--