Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:89623
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain anderiasch.de designates 81.169.138.148 as permitted sender)
To: Sebastian Bergmann <sebastian@php.net>, internals@lists.php.net
References: <039701d12dce$c67982a0$536c87e0$@lool.fr>
 <CAMUwpuS_z2Nf11edEZ7smhYZr7i9a5EcK93m0G_w8E400MSvNQ@mail.gmail.com>
 <56605D5E.5050001@php.net>
 <CAEZPtU7+BE3r9Er8pbc8XTyLfeOALoDwANvafipwMLOGT_UhHw@mail.gmail.com>
 <5660CB92.1030703@gmail.com> <56616B0D.1050000@php.net>
Message-ID: <5661D315.2030409@anderiasch.de>
Date: Fri, 4 Dec 2015 18:53:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56616B0D.1050000@php.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP 7.0.0 final RTM delay
From: ml@anderiasch.de (Florian Anderiasch)

On 04.12.2015 11:29, Sebastian Bergmann wrote:
> Am 04.12.2015 um 00:09 schrieb Stanislav Malyshev:
>> Windows as a platform is different from Linux/Mac in several aspects
> 
>  True. But why does the PHP Project have to provide Windows binaries on
>  php.net? Microsoft should be treated as any other downstream vendor: let
>  them build their binaries on their infrastructure and let them distribute
>  their binaries through their channels.
> 
>  Again, my intention is not to "bash Microsoft". I appreciate and
>  respect everything they have done to make PHP on Windows more robust.
>  I just think that the PHP project would be better off to focus on
>  one release artifact: the source tarball.

While I'd love to share your view on this I think it's just unrealistic
in regards to ease of use towards anyone who's not a hardcore windows
developer.

a) building a php.net release tarball on a freshly installed
Ubuntu/CentOS/Debian/whatever box:

- it's literally 1 copy/pastable command line to install all
dependencies, then unzip, configure make.

b) building this on Windows:

- to be honest, I don't even know how many steps exactly are involved,
I've given up years ago. And in my team I am usually the one most
confident to develop *anything in any language* on Windows.

I hate to say it, but not providing an official Windows build is kind of
sticking the finger to everyone using Windows for PHP (not the language)
development. Yes, this could be alleviated with builds from external
sources, but most language teams release for "more platforms". And I
stand to what I said above. On Linux (and maybe also on OS X?) you can
get 90% of users non-versed in C development to build their PHP quite
easily, on Windows.. maybe possible, but not worth the hassle.

Greetings,
Florian