On Mon, Jun 25, 2018 at 9:30 PM, Zeev Suraski wrote:
>
> Thoughts?
>
Since PHP 8 is going to open more doors for general purpose scripting
usages, how about reconsidering "Default embed mode always"?
i.e. Execute PHP script without "https://wiki.php.net/rfc/nophptags
https://wiki.php.net/rfc/sou
> On Jun 27, 2018, at 1:48 AM, Dmitry Stogov wrote:
>
> Hi Niklas,
>
> Fibers are the major feature we're looking forward to, because it
> allows async I/O in places that do not account for async, e.g. also
> re-using interfaces designed for sync applications. Apart from that,
> we want to avoi
Hi Niklas,
On Jun 26, 2018 11:36 PM, Niklas Keller wrote:
Hey Dmitry,
>
> hi Aaron,
>
>
> On Jun 25, 2018 10:49 PM, Aaron Piotrowski wrote:
>
> > On Jun 25, 2018, at 7:30 AM, Zeev Suraski wrote:
> >
> >
> > 2. Better support long-running, async-based, microservices-focused
> > execution model
Hey Dmitry,
>
> hi Aaron,
>
>
> On Jun 25, 2018 10:49 PM, Aaron Piotrowski wrote:
>
> > On Jun 25, 2018, at 7:30 AM, Zeev Suraski wrote:
> >
> >
> > 2. Better support long-running, async-based, microservices-focused
> > execution model. It's probably no secret that one of the key reasons Node
hi Aaron,
On Jun 25, 2018 10:49 PM, Aaron Piotrowski wrote:
> On Jun 25, 2018, at 7:30 AM, Zeev Suraski wrote:
>
>
> 2. Better support long-running, async-based, microservices-focused execution
> model. It's probably no secret that one of the key reasons Node is gaining
> popularity is beca
On Mo, 2018-06-25 at 16:14 -0700, Alice Wonder wrote:
> As a packager github is a fracking nightmare.
>
> Frequently what we do is include a hash of the release tarball in our
> build and require that it matches so that people rebuilding our
> package (e.g. to add a patch they need) don't have to
On 26/06/18 00:14, Alice Wonder wrote:
git is for code management but when a release it tagged, creation of the
source tarball should be done by the developer, and released by the
developer, preferably with sha256 or sha512 sums posted in an easy to
find location (which github doesn't do)
Or
On 06/25/2018 07:13 AM, Johannes Schlüter wrote:
On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote:
3. Foreign Function Interface support.
Related to this on a non-PHP-code and strategic matter I would like to
rethink PECL. Currently maintenance and installing extensions using it
is a pita.
On 25/06/2018 21:42, Larry Garfield wrote:
What will definitely bring benefit to real world workloads is preloading,
which (if we manage to do it) will dramatically reduce the per-request
initialization stage. It could bring us much of the benefit of async-IO
long running processes without sacri
> -Original Message-
> From: Larry Garfield [mailto:la...@garfieldtech.com]
> Sent: Monday, June 25, 2018 11:43 PM
> To: internals@lists.php.net
> Subject: Re: [PHP-DEV] PHP 2^3
>
> That's certainly a good argument for the people doing deep engine work to
&g
On Monday, June 25, 2018 2:12:22 PM CDT Zeev Suraski wrote:
> > When we speak of "typical web loads" not getting much benefit here, are we
> > really talking about CGI-style "reboot every request" type loads rather
> > than
> > "IO-bound work"? Because it's been observed many times in the past t
> On Jun 25, 2018, at 7:30 AM, Zeev Suraski wrote:
>
>
> 2. Better support long-running, async-based, microservices-focused execution
> model. It's probably no secret that one of the key reasons Node is gaining
> popularity is because it can handle a huge number of concurrent connections
>
On Mon, Jun 25, 2018 at 8:52 PM Larry Garfield
wrote:
> On Monday, June 25, 2018 11:16:31 AM CDT Sara Golemon wrote:
>
> > > First, I'll admit that there's definitely some of that happening. But
> to
> > > paraphrase my daughters - "I didn't start it!". In other words -
> people
> > > are very
On Monday, June 25, 2018 11:16:31 AM CDT Sara Golemon wrote:
> > First, I'll admit that there's definitely some of that happening. But to
> > paraphrase my daughters - "I didn't start it!". In other words - people
> > are very actively looking for ways to run PHP in a Node-like manner, and
> > w
On Mon, Jun 25, 2018 at 7:16 PM Sara Golemon wrote:
> Yeah, like I said, I must have completely missed that entire
> paragraph. Mid-2020, following a late-2019 release of a "light" 7.4
> with deprecations is reasonable, though I don't think it'd be such a
> bad idea if we kept it on schedule to
On Mo, 2018-06-25 at 09:58 -0500, Ralph Schindler wrote:
> On 6/25/18 9:13 AM, Johannes Schlüter wrote:
> >
> > On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote:
> > >
> > > 3. Foreign Function Interface support.
> > Related to this on a non-PHP-code and strategic matter I would like
> > to r
On Mon, Jun 25, 2018 at 9:58 AM, Zeev Suraski wrote:
> Note that I did propose that we actually have a thin depredations-only PHP
> 7.4 (to give credit where credit's due, that's Dmitry's idea). This gives
> us ample time without having to rush deprecations into 7.3
>
I apologize. I had missed th
Thanks for taking the time to respond!
On Mon, Jun 25, 2018 at 5:27 PM Sara Golemon wrote:
> 1/ Pushing 8.0 as 7.3 + 1 means we're going to rush deprecations into
> 7.3 which is already in fire-hose mode of last-minute, under-planned
> "hey I want this toy" requests. Yes, deprecations are a lit
On 6/25/18 9:13 AM, Johannes Schlüter wrote:
On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote:
3. Foreign Function Interface support.
Related to this on a non-PHP-code and strategic matter I would like to
rethink PECL. Currently maintenance and installing extensions using it
is a pita. Thi
On Mon, Jun 25, 2018 at 7:30 AM, Zeev Suraski wrote:
> As I mentioned a few days ago I intended to send it slightly later - but as
> Nikita brought up the topic of PHP 8, this is probably as good a time as any
> to start the discussion.
>
> Please note: The goal of this email isn't to discuss i
On Mon, Jun 25, 2018 at 3:31 PM Zeev Suraski wrote:
> 1. JIT. As most of you probably know, we've invested heavily in re-doing
> JIT on top of the PHP 7 infrastructure. There are good news and bad news.
> The good news is that - like the JIT POC we did back in 2014 - the results
> for CPU inten
On Mo, 2018-06-25 at 12:30 +, Zeev Suraski wrote:
> 3. Foreign Function Interface support.
Related to this on a non-PHP-code and strategic matter I would like to
rethink PECL. Currently maintenance and installing extensions using it
is a pita. This should be doable in a nicer way.
(i.e. pecl
As I mentioned a few days ago I intended to send it slightly later - but as
Nikita brought up the topic of PHP 8, this is probably as good a time as any to
start the discussion.
Please note: The goal of this email isn't to discuss in detail each and every
topic that's mentioned, but rather to
23 matches
Mail list logo
