Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106610
Message-ID: <1098C07D-3CFD-45A4-9AAA-68F83CA40E4A@benramsey.com>
Content-Type: multipart/signed;
	boundary="Apple-Mail=_A1D6B3CF-086E-4FA7-AFF9-64E750109961";
	protocol="application/pgp-signature";
	micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Wed, 14 Aug 2019 12:22:40 -0400
In-Reply-To: <alpine.DEB.2.21.1908141608160.29731@singlemalt.home.derickrethans.nl>
Cc: PHP Developers Mailing List <internals@lists.php.net>
To: Derick Rethans <derick@php.net>
References: <alpine.DEB.2.21.1908141608160.29731@singlemalt.home.derickrethans.nl>
Subject: Re: [PHP-DEV] Vote: Straw poll for P++ feasibility
From: ben@benramsey.com (Ben Ramsey)

--Apple-Mail=_A1D6B3CF-086E-4FA7-AFF9-64E750109961
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On Aug 14, 2019, at 11:14, Derick Rethans <derick@php.net> wrote:
>=20
> Hi,
>=20
> In the last week(s) there has been a lot of chat about Zeev's P++ =
idea.
> Before we end up spending this project's time and energy to explore =
this
> idea further, I thought it'd be wise to see if there is enough animo =
for
> this. Hence, I've created a document in the wiki as a poll:
>=20
> https://wiki.php.net/rfc/p-plus-plus


I voted "no." While I've not contributed to the discussions here, I've
been following them and also reading what many on Twitter have been
saying.

I'll admit, I liked the idea of P++ for the novelty of it, but as the
past has proven, we can continue to provide greater type safety in PHP,
while retaining the dynamic character and flexibility that many enjoy.
In short, the internals team has done a great job of allowing us to
have our cake and eat it, too.

Sara shared this a few days ago, and I=E2=80=99d like to reiterate it:

> Strict(er) typing - I'm not sure, on the surface, what future =
expansions
> we'd plan for in this area which couldn't fit into standard PHP in a =
non
> BC-breaking way.

There have been a few people on Twitter floating up the idea of
something like TypeScript for PHP. This might be a better approach for
those who want to significantly diverge from PHP proper. Already, it is
possible to build something like this and have it transpile to PHP. In
the future, perhaps it could even compile down into Zend opcodes that
could be loaded directly into the PHP interpreter. Either way, it
wouldn't change PHP itself, but it could provide the syntactic sugar
and improved type-safety that folks are looking for. More importantly,
it wouldn't split the community or internals.

Cheers,
Ben

--Apple-Mail=_A1D6B3CF-086E-4FA7-AFF9-64E750109961
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQToXQMR3fpbrPOmEOewLZeYnIwHGwUCXVQ1UAAKCRCwLZeYnIwH
Gz9iAP40PDCG/3mhaiLmAA21q3+Uvz19w9f+MqhFDBiM/DsxPAD/d8SO4VHV7Qb1
iRuDzT9sJktq/1/kt+BGz5xC1Y+RJis=
=XzPa
-----END PGP SIGNATURE-----

--Apple-Mail=_A1D6B3CF-086E-4FA7-AFF9-64E750109961--