Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103940
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=turbo-smtp; d=php.net;
	h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type;
	b=PBcqg4gCJKtxckSv4A5omKkGe2Q8o8M5YRBnV/vFQSD/yW+ZBnYJ7LLSNIXhj1
	2u1kvoN1YUVecOkHwsZmfWuR4lRvpv1Nif+o5+jdzA0dirpuqJ7eoc/ZQfS9mW4C
	J2q6/tLVKW31fjY3X161x10Oj3ex8oj9y8pL+gFMoJLYs=;
MIME-Version: 1.0
References: <DM6PR02MB59326E10841277F34E4EFF75BF910@DM6PR02MB5932.namprd02.prod.outlook.com> <CAF+90c-Ck7zgU+Z=VX8ewny2s=xrr5RYRC86r_0FJ_gFUM-cmw@mail.gmail.com> <8d9dffd5-ea2c-e642-b777-4a4fd76b261a@zend.com> <CAJW__o2JZ_E3UpoanaFNEEM8ufWhHzsJDEdYhecfe7639U4-oA@mail.gmail.com>
In-Reply-To: <CAJW__o2JZ_E3UpoanaFNEEM8ufWhHzsJDEdYhecfe7639U4-oA@mail.gmail.com>
Date: Thu, 31 Jan 2019 19:04:03 +0200
Message-ID: <CAJHtznxfJF--Fz3Ga+6Bo1O6exg0utOW4LvPv5UNN7x014sF0g@mail.gmail.com>
To: Kalle Sommer Nielsen <kalle@php.net>
Cc: Dmitry Stogov <dmitry@zend.com>, Nikita Popov <nikita.ppv@gmail.com>,  PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000002b27190580c404b7"
Subject: Re: [PHP-DEV] [RFC] JIT
From: zeev@php.net (Zeev Suraski)

--0000000000002b27190580c404b7
Content-Type: text/plain; charset="UTF-8"

On Thu, Jan 31, 2019 at 6:47 PM Kalle Sommer Nielsen <kalle@php.net> wrote:

> Without my usual Windows bias, I do believe it is a considerable fact
> like Nikita pointed out as Windows is a first class citizen in terms
> of operating systems we support. While PHP on Windows may not have the
> speed that the Unix counterpart have, it is still a very important
> development platform. Many developers develop on Windows and deploy on
> a Unix based system, being unable to test such an important feature in
> a development environment is also a large question mark.
>

As long as we can agree that very few actually *deploy *on Windows, I think
we're on solid grounds.
As the JIT implementation is likely to have at least *some* significant
differences compared to Linux, I'm not sure what testing it on Windows
would give you.  JIT is supposed to be entirely transparent, and the
performance characteristics - as well as the bug patterns - are likely to
be quite different on Linux vs. Windows, at least in many cases.
Is it really that important to have?

I'm honestly a bit perplexed by how many people here viewing Windows
support as a must have, while at the same time I think we all agree PHP is
very scarcely found on production Windows servers, and JIT is a
predominantly production feature.

I'm personally interested in taking a look at it (and I'm certain
> Anatol does too), but simply dismissing is a no-go for me.


It'd be interesting to evaluate the cost associated with supporting
Windows.  Bare in mind, we're proposing to vote on this as a production
feature for PHP 8 - which realistically means almost two years from now *at
the earliest*.  I'm sure we'd have Windows support a lot sooner than that
if we decide that it's a must have.  I agree with Nikita that the key
question is in fact, do we or do we not want to introduce JIT in - with the
main question being the maintenance cost.  Let's tackle this question
first, otherwise - why send Dmitry (and maybe others) for doing more work
(Windows support) if we are likely to flush it all down the toilet?

I think that if we reach the conclusion that Windows support is a must, we
can condition the inclusion of JIT based on having it.  Let's first agree
on whether we want it in the first place.

Zeev

--0000000000002b27190580c404b7--