Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120345
MIME-Version: 1.0
References: <CADK1yX+aYifoOTwPGnuL3=xDL_NYgFgvZmFAvBfOK333Ohxwrw@mail.gmail.com>
 <000201d9897f$aa9f9fa0$ffdedee0$@roze.lv> <CADK1yXK4U=-POE2h5zu5de1NS0pQE7Rppa6QNxboEeRuOMDYJw@mail.gmail.com>
 <000301d98997$239562c0$6ac02840$@roze.lv>
In-Reply-To: <000301d98997$239562c0$6ac02840$@roze.lv>
Date: Thu, 18 May 2023 13:13:10 -0300
Message-ID: <CADK1yX+U-2538ue1U37CnJvzeOv=3q7msuqCJHWBY5OGdaW34A@mail.gmail.com>
To: Reinis Rozitis <r@roze.lv>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d3c84205fbfa1651"
Subject: Re: [PHP-DEV] PHP Package for PHP
From: deleugyn@gmail.com (Deleu)

--000000000000d3c84205fbfa1651
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, May 18, 2023 at 11:43=E2=80=AFAM Reinis Rozitis <r@roze.lv> wrote:

> > I have worked with PHP for 14 years now and I know nothing about PEAR.
> It either says something about me or about PEAR.
>
> Then the next logical question would be do you know what PECL is? :)


>
> But to be short my point is - before attempting to get new function(ality=
)
> in core it (seems to me) that more realistic if you really want to achiev=
e
> that is at least by presenting some kind of working base blocks especiall=
y
> when there are all the means to extend the language both on low level
> (being an extension) or a pure-php package in any of the existing channel=
s
> (composer / push for repopulation of PEAR? etc).
>

My wish here is not to present a new functionality to core, but rather
start a project which lowers the barrier for getting basic things into
core. Sure, I could write a new Str class and fix all the problems I think
the `str` and `str_` lib has. In fact, everyone can do that [1][2][3][4].
PHP current state actually encourages the language to have multiple
competing implementations for the same thing because some past decisions
are hard to be fixed and introducing things to the language are also hard.
The competition and the diversity addressing all sort of problems is a
strength in the PHP Community, but also a weakness in PHP's ability to
provide a bare minimum that help newcomers to get started and veterans to
only reach for deviation when it is made necessary.


>
> There is usually the argument - "if this is not in core no one (people on
> shared environments/hosting) won't be able to use it" and so on.. The
> counter to that are things like Imagick / redis / memcache(d) / APCu whic=
h
> are vastly popular but still live outside core (obviously those are not
> language rather than engine features).
>
> rr
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php


I wouldn't argue in favour or against shared hosting. I haven't used that
in a decade so I'm really not the best person to talk about that universe.
If someone were to create a PHP Extension to rewrite some of PHP's
functionality and/or cover PHP's standard library gaps, I know I wouldn't
spend a minute of my time looking into it or installing it. I imagine that
it would take many years until someone could actually build up a reputation
and a library quality until it could start being considered for adoption.


[1] https://github.com/spatie/string
[2] https://laravel.com/api/9.x/Illuminate/Support/Str.html
[3] https://symfony.com/doc/current/components/string.html
[4] https://github.com/azjezz/psl/tree/next/src/Psl/Str

--=20
Marco Deleu

--000000000000d3c84205fbfa1651--