Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106425
MIME-Version: 1.0
References: <CAFPFaML19B_RehrUQLEy_oFae-H5r3+BpUGg=GF1js83cJpJqQ@mail.gmail.com>
 <CAOWwgpn=9HZ8j2xMn-ENwZ5caAO4VRFJ5MLk0f=GLhjzHO7Czw@mail.gmail.com>
In-Reply-To: <CAOWwgpn=9HZ8j2xMn-ENwZ5caAO4VRFJ5MLk0f=GLhjzHO7Czw@mail.gmail.com>
Date: Wed, 7 Aug 2019 15:57:02 -0400
Message-ID: <CAPKYkKw2b1pgRHMJSF3Kk+w55hch6yu3WdyEC0yAe0Z7Hh=8tA@mail.gmail.com>
To: Nicolas Grekas <nicolas.grekas+php@gmail.com>
Cc: "G. P. B." <george.banyard@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000ef0e5a058f8c589f"
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags, again
From: chasepeeler@gmail.com (Chase Peeler)

--000000000000ef0e5a058f8c589f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 7, 2019 at 1:14 PM Nicolas Grekas <nicolas.grekas+php@gmail.com=
>
wrote:

> Le mar. 6 ao=C3=BBt 2019 =C3=A0 13:34, G. P. B. <george.banyard@gmail.com=
> a =C3=A9crit :
>
> > The voting for the "Deprecate short open tags, again" [1] RFC has begun=
.
> > It is expected to last two (2) weeks until 2019-08-20.
> >
> > A counter argument to this RFC is available at
> > https://wiki.php.net/rfc/counterargument/deprecate_php_short_tags
> >
> > Best regards
> >
> > George P. Banyard
> >
> > [1] https://wiki.php.net/rfc/deprecate_php_short_tags_v2
>
>
>
> The counter-arguments are a really nice addition to the process.
>
> Reading them made me think there is a big missing "pro" argument: perceiv=
ed
> complexity of the engine.
>
> When there is no choice to make (short tags on/off, magic_quote on/off,
> etc), then there is only one thing to teach, one thing to learn, one thin=
g
> to (not have to) agree on when deciding for some conventions, etc.
>
> When there are N binary options (and not all options are binary), there a=
re
> 2^N things to teach, learn, etc.
>
> In this case, claiming a slippery-slope is a logical fallacy. We aren't
talking about opening it up so that we can add even more opening tags in
the future. The odds are pretty much zero that keeping short tags would
lead to it in the future. We're talking about two possible ways to begin a
block of PHP code. <? and <?php. Pretty much everyone (if not actually
everyone) that is against this RFC has stated that they don't actually use
short tags, and do not advocate that anyone else use them either.


> That's a major cost put on the community. Choices that were made years ag=
o
> when PHP was not what it is today were certainly fine, but nowadays, this
> imposes significant a burden on everyone. Each option individually are
> maybe minor, but the 2^N becomes quickly big. I think we should make such
> things way simpler so that we can free the brains of many to do the next
> things that matter.
>
> I think the cost put on the community to fix existing instances of short
tags is a MUCH higher burden than asking them know about the existence of
short tags should they encounter them one day. I'm in charge of maintaining
a very large legacy code base. The majority of the legacy code is "leave it
alone code" that is slowly getting re-written. The code is horrendous.
Things have broken in the past from running PhpStorm's auto-formatting on a
file. The effort required to update all of that code in order to upgrade
would be so high that it's likely I would never get approval from my
superiors to spend that much time on it.


> I don't have a vote, but if I were I would vote "yes". Instead, I encoura=
ge
> "no"-voters to reconsider, and others to vote "yes" too :)
>
> Cheers,
> Nicolas
>


--=20
Chase Peeler
chasepeeler@gmail.com

--000000000000ef0e5a058f8c589f--