Re: [RFC] [Discussion] UUID
| From: | Levi Morrison | Date: | Wed, 24 May 2017 15:11:01 +0000 |
| Subject: | Re: [RFC] [Discussion] UUID | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99145@lists.php.net to get a copy of this message | ||
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.
>
> --Larry Garfield
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.