Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111976
To: Nikita Popov <nikita.ppv@gmail.com>,
 Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP internals <internals@lists.php.net>
References: <ME2P282MB02272021544EFDBE6BF44A23F2300@ME2P282MB0227.AUSP282.PROD.OUTLOOK.COM>
 <940131FA-19B3-406C-8982-0AD276FD1879@gmail.com>
 <CAF+90c8y6dpqMg8s+X-ndQwp52CDL7Q9oHL_DwDQ1OS-k1GR9w@mail.gmail.com>
Message-ID: <142da816-f3bf-2f05-6147-ccd2117e1dfd@gmail.com>
Date: Thu, 1 Oct 2020 17:13:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c8y6dpqMg8s+X-ndQwp52CDL7Q9oHL_DwDQ1OS-k1GR9w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: execution opcode file without php source code file
From: dik.takken@gmail.com (Dik Takken)

On 01-10-2020 14:30, Nikita Popov wrote:
> It would be good to know what the actual use-case for this is. If the goal
> here is to distribute pre-compiled PHP code without the source code, then
> this is not going to work without making the opcode format stable (which, I
> think, is pretty unlikely.) If the goal is improving cold startup
> performance, then I wonder what the benefit over the existing file cache is.

The only use case I see is to package commercial closed source
applications as Docker containers. That allows the packager to ship the
compiled code along with the exact PHP version and configuration that
can run it reliably.

Regards,
Dik Takken