Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115122
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
In-Reply-To: <326d6cda-c007-f82c-469f-566e1a34e248@processus.org>
Date: Thu, 24 Jun 2021 12:08:05 -0400
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <6F2B8C05-45A4-4933-A88D-87A1C39FC8FE@newclarity.net>
References: <0BBAA2F7-02D7-4AEE-B48A-97436A0D8E5D@gmail.com>
 <DM6PR07MB6618813BEFF21B9A91EE1924F9079@DM6PR07MB6618.namprd07.prod.outlook.com>
 <CABdc3WqAEWLGbnv-rU8xT5YFebnngvz_DJQiBoj4Rdyh3SwoNA@mail.gmail.com>
 <326d6cda-c007-f82c-469f-566e1a34e248@processus.org>
To: Pierre <pierre-php@processus.org>
Subject: Re: [PHP-DEV] [RFC] clamp
From: mike@newclarity.net (Mike Schinkel)



> On Jun 24, 2021, at 7:59 AM, Pierre <pierre-php@processus.org> wrote:
>=20
> Le 24/06/2021 =C3=A0 11:44, Micha=C5=82 Marcin Brzuchalski a =C3=A9crit =
:
>> I get an impression that we constantly add things into standard =
library
>> which are from a language perspective irrelevant
>> and that all could be developed in userland with no harm.
>>=20
>> Cheers,
>> --
>> Micha=C5=82 Marcin Brzuchalski
>=20
> Hello,
>=20
> I respectfully do not agree with this last statement. A simple method =
such as this one entirely belong to the standard library. I wouldn't =
want to end-up with a NPM-like ecosystem where I'd have to choose =
between clamp-php, php-clamp, php-bound-int, int-php-bound, etc...

>=20
> The more the standard library will be complete, the less projects will =
need dependencies, which is better for your projects long term =
maintenance. You often end-up in dependency resolution hell because =
library A use library B, which use foo/clamp which is not compatible =
with another C library you use, or because it doesn't support PHP core =
version X or Y.
>=20
> A simple function such as clamp in standard library makes much sense, =
anything like it must go into standard library, this way the userland =
ecosystem can focus on domain related stuff, or more complex topics, =
without worrying too much about this kind of detail. Having a great and =
complete standard library lowers community fragmentation, and that's for =
the best !
>=20
> Moreover, it also ensures that all developers speak the same language =
regarding primitives provided by the standard library, and makes =
communication more efficient within community.

This.  All of this.

-Mike