On Wed, May 24, 2017 at 9:29 AM, li...@rhsoft.net <li...@rhsoft.net> wrote:
> > > Am 24.05.2017 um 17:11 schrieb Levi Morrison: > >> On Wed, May 24, 2017 at 9:04 AM, Larry Garfield <la...@garfieldtech.com> >> wrote: >> >> On 05/24/2017 04:31 AM, li...@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.
