Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68098
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.192.178 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <51DF0CDD.7060108@sugarcrm.com>
References: <CAA9esyS0YL=biVS37ix-yBea7RmZXPnhVk_xKjfz6x+gfN5LNw@mail.gmail.com>
	<CAL+t6cF9JTr9e=A15LvhfgN0DaV8_k4SuEDxQ408fNAAx=8Z_A@mail.gmail.com>
	<CAOX1NOfBPTggj6-WA=ArXjw1UvhUbVC=+FjCYvk6Bgp856biFg@mail.gmail.com>
	<CACwt+Je1vS7MkqShM8+FaDJmAoyaTDCWtTSOuOwG4iWUnyvKHA@mail.gmail.com>
	<CAMUwpuRC8WfrR26W+1hVgXDMt28OQXek68w=9YEGs2ueEiOewg@mail.gmail.com>
	<CACwt+JfoZPuTYk0S3stoDdAftcRB1hAspXNQU4EBkVaX2uiStw@mail.gmail.com>
	<CAH-PCH4BMFrjmNXDJXJ96QT9deWTi7P8P8OR-ZGcr6j=VQ5sig@mail.gmail.com>
	<1372258135.2410.22.camel@guybrush>
	<CAA9esyT854FV6PSxR9pTX3AZ05AJhaYchDmHyBb+Fq_r8rz1xA@mail.gmail.com>
	<CAESVnVqZ2MBej6btO8=KJPVTKD5mOQD+Dzqn_zcZb7XqFSo7+A@mail.gmail.com>
	<CAKUjMCWU1AJhYi9GSPAZyU1U3Gh3paKOAw=fDidSeW96OSvUKA@mail.gmail.com>
	<CAESVnVry6r-=ttASy=xM_X5g+=TRQ84dB4cZ5PRQ=BQH29-rcA@mail.gmail.com>
	<CAA9esyTeURYzngd2cszYyKLYp1=4W63np+OxzyhZBWaMP_s+ow@mail.gmail.com>
	<51DF0CDD.7060108@sugarcrm.com>
Date: Thu, 11 Jul 2013 13:27:24 -0700
Message-ID: <CAESVnVqZX=e46GuJZfyryo-iNsAffhw_zb6S2SfRSySxS=pNXw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Florin Patan <florinpatan@gmail.com>, "RQuadling@gmail.com" <RQuadling@gmail.com>, 
	PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b111eadd47d2204e142383f
Subject: Re: [PHP-DEV] Request for comments - new PHP feature: return typing
From: pollita@php.net (Sara Golemon)

--047d7b111eadd47d2204e142383f
Content-Type: text/plain; charset=ISO-8859-1

> While HHVM is a very interesting project, their use case is pretty
> specific and narrow, and, as I understand, connected to a single
> application (albeit running huge traffic numbers). So I'm not sure
> copying whatever they do is necessarily good for PHP as a whole. HHVM
> case is basically static compilation of monolithic application, as far
> as I remember, which is not how PHP is usually run. It is true that such
> mode negates many arguments against static typing, but it negates them
> only for specific narrow case of HHVM, not for PHP as a whole.
>

Incorrect on a few points:

1) HHVM isn't just running FB.  A number of sites have either already
started using HHVM, or intend to soon.
2) The "static compilation" description is grossly outdated information.
 HHVM behaves the same way as PHP when it comes to running an application.
 There's an optional "precompile to bytecode" step, but that's a minor
optimization overall.  In general, you just point it at your webroot and it
compiles to bytecode on demand (just like PHP) caches the compiled bytecode
(just like APC or ZO+), and JITs to machine code as needed.
3) We mitigate the arguments against strict typing in other ways than you
think, evidently. :)

I won't suggest that PHP should follow HHVM, if anything I'll usually (and
have frequently) rallied for the other way around.  In this case, however,
as with Generators, I think that we should endeavor to keep the
implementations close together by the most appropriate means.  I don't want
two versions of PHP syntax.

-Sara

--047d7b111eadd47d2204e142383f--