Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124150
Precedence: bulk
MIME-Version: 1.0
References: <CAEUnE0fGZ3jFiBG=GyvnhBzH5a0iO4=n75PM=3+6zLAMrumEvA@mail.gmail.com>
 <CADK1yX+E9mvaM_CHJ8tmEx=O70hf8xasbvngh4wvNM8ce8KKGQ@mail.gmail.com>
 <B5DC69B8-E044-47FB-B81C-307E2C19CB66@newclarity.net> <1917CF7C-26D8-4DBE-B05C-5AA650AC6C9F@rwec.co.uk>
 <551cd5b0-1c00-4818-a9ca-97f6b7e8c3dc@app.fastmail.com> <CAEUnE0fNxSHN4QGfm6ETMVdE5Mcm1AEebmWs7i9xDNgcWnvQvw@mail.gmail.com>
 <39B496F8-062E-4848-9B3B-529BE8D3415A@newclarity.net> <CAEUnE0fOfU1tJNKXuBqbSm8jsp7gqe_JY-SiipdUKNztcx0Rog@mail.gmail.com>
 <856F4F70-DC81-4098-82DD-5F6D47CDF3F0@newclarity.net> <CAEUnE0c0fW9xnQOtLgj1zTpvdfixSHuLeLA7HOqDTkpr4hJ84g@mail.gmail.com>
 <CAEUnE0dSUY2VKji_o-AgQ-YZMf7viwCZh1sa8ScHdS7ihUgfUQ@mail.gmail.com>
 <217db044-e356-4e18-ba68-c18dce6381a5@app.fastmail.com> <CAOyH9yRptLsZ_zuW1aEkbmV+z+8qz8p0ARqMpvg3FCb4VaEN=g@mail.gmail.com>
 <8D065175-9383-4110-A245-7E876AF88281@rwec.co.uk>
In-Reply-To: <8D065175-9383-4110-A245-7E876AF88281@rwec.co.uk>
Date: Tue, 2 Jul 2024 02:03:08 +0900
Message-ID: <CAOyH9ySnjP71kikrB=2DX--AfasNDp-rTeMgUPeHd_xKhKTHZg@mail.gmail.com>
Subject: Re: [PHP-DEV] Iteration III: Packages (was Re: [PHP-DEV] [Initial
 Feedback] PHP User Modules - An Adaptation of ES6 from JavaScript)
To: "Rowan Tommins [IMSoP]" <imsop.php@rwec.co.uk>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: alex.pravdin@interi.co (Alexander Pravdin)

On Tue, Jul 2, 2024 at 1:20=E2=80=AFAM Rowan Tommins [IMSoP]
<imsop.php@rwec.co.uk> wrote:
> On 1 July 2024 15:37:49 CEST, Alexander Pravdin <alex.pravdin@interi.co> =
wrote:
> >I personally support the movement from the current "plain-text
> >template-first" language to a "coding-first" language, where files
> >contain code by default.
>
> I honestly don't read the <?php at the top of files as an "opening tag" a=
ny more, just as a "magic number" that indicates it's a PHP file, like the =
doctype at the top of an HTML file. It might as well be "I <3 PHP".
>
> Any suggestion to add a special of avoiding those 4 characters scores a b=
ig shrug from me.

The issue is that without this legacy "magic number" the PHP file
contains plain text/html/whatever. This is weird. This means PHP is a
template processor in the first place. And adding some code is a
feature on top of the template processor. I was actually talking not
about avoiding 4 chars for the sake of avoiding 4 chars, but about
making the PHP source file a programming code file, not a template.
And in addition, cut some weird legacy allowing further engine
optimizations. Historical/legacy/BC reasons pop up regularly in
discussions about something that can not be optimized/improved. What
is the percentage of files containing PHP code only and pure PHP
templates in an average project? 100% vs 0%? 99% vs 1%? Who uses plain
PHP templates today? Why programmers should care about templating
legacy in each and every PHP file? I think it's time to switch from
"templating PHP" to "programming PHP".

Alexander