Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122341
MIME-Version: 1.0
References: <CAK=iT=UrMCPw5ydCnxa_87ws6xKRO5Y3qJnmchczgDds8u660A@mail.gmail.com>
 <CABigaAUjSx3-vEaQhPk-toJTSg+J3CLrO3otpm1g6hqbYyQKvw@mail.gmail.com>
 <CAK=iT=WgsEZjyu3Y2wTWvycqCsYH7MrLsZgERZK3u75U08ePpA@mail.gmail.com>
 <CAL0xaBHfEMs1BVAMZOuFCUpb9orNSRD0YDhu=3wJAGK7K0_=dg@mail.gmail.com>
 <CAK=iT=XDVcs+y4XDmGu2re137i2yD9LiEj1-HLvyxxxrb8jFUw@mail.gmail.com>
 <CAK=iT=UDUjCZ-25k_MkHFO7uKdWAqoJxdWLVBGM2_SYDk-JyAg@mail.gmail.com>
 <742f202d-7990-4f51-b903-7a15e3fd33c2@app.fastmail.com> <CABigaAW2KeGxf7HnzpcOeS=CL31=UNGZnqpZvoJsJg4miBTBGw@mail.gmail.com>
 <1cd8fa7b-ab62-4563-bf13-bb7801f1ce8d@app.fastmail.com> <CAK=iT=X5XKdSZ1D=+SEU4=12hJK+oPn+XBWxA54yyQsxAixx8A@mail.gmail.com>
 <CAOyH9yT5NQQYgq=5O5q==BaTpm-JJRDUcAsX2Tc36hbXLdH5vw@mail.gmail.com> <CAK=iT=W7xzS_9FZj-Cd1uUBaLtX=157t81_KOkr999bRyTcDjw@mail.gmail.com>
In-Reply-To: <CAK=iT=W7xzS_9FZj-Cd1uUBaLtX=157t81_KOkr999bRyTcDjw@mail.gmail.com>
Date: Thu, 8 Feb 2024 17:37:24 +0900
Message-ID: <CAOyH9yQKA+RnhXFHvH=dVHT8UWfyF_A89p_c9wES1k4kKstBtA@mail.gmail.com>
To: =?UTF-8?B?0JPRgNC40LPQvtGA0LjQuSBTZW5pb3IgUEhQIC8g0KDQsNC30YDQsNCx0L7RgtGH0LjQuiBXZWI=?= <6562680@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Feature request: https://github.com/php/php-src/issues/13301
From: alex.pravdin@interi.co (Alexander Pravdin)

On Thu, Feb 8, 2024 at 4:02=E2=80=AFPM =D0=93=D1=80=D0=B8=D0=B3=D0=BE=D1=80=
=D0=B8=D0=B9 Senior PHP / =D0=A0=D0=B0=D0=B7=D1=80=D0=B0=D0=B1=D0=BE=D1=82=
=D1=87=D0=B8=D0=BA Web
<6562680@gmail.com> wrote:
>
> JIT I've had this solved, not only the application, but a way to.
>
> Am sharing my experience without labels "bad", "cood", "truth" or "correc=
t", like you did.
>
> Your arguments are based on your principles and I don't see in your words=
 any point to discuss, so - use pm or share here secret of error-free code,=
 if you have ideas how to solve "my" application if "you know what is the c=
orrect design".
>
> I think the people who use labels usually never share their experience.

I already shared my experience - to use PHPStan with the highest level
of assertion to catch a lot of errors, warnings, and possible issues
in the code and fix them before the code even runs on a server. Did
you read my message? Did you try PHPStan? If you tried, what was the
result? Please share it.

When you say SOLID prevents from solving business needs quickly, you
should know that business always needs everything yesterday. The
problem is not in SOLID or PHP language. The problem is in a bad
design/architecture that led to a lot of errors and warnings in
unpredictable places that require super custom collection of them on
EVERY request. Properly designed applications do not require
language-level changes to fulfill business requirements and monitor
edge cases.

If you have a super legacy code, why the language should care about
it? Is it the purpose of the language? Just drop this legacy code if
it requires custom error and warning collection. Explain to the
business that the code state is so weird that it requires a lot of
time to refactor or to reimplement it from scratch. This is a very
common problem of legacy rubbish code and it is not specific to the
PHP language.

Switching the discussion to a flame with personal offense is not a
good style here, please don't do this.