Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74394
Return-Path: <mails@thomasbley.de>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 33699 invoked from network); 20 May 2014 23:02:55 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 May 2014 23:02:55 -0000
Authentication-Results: pb1.pair.com header.from=mails@thomasbley.de; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=mails@thomasbley.de; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain thomasbley.de from 85.13.137.24 cause and error)
X-PHP-List-Original-Sender: mails@thomasbley.de
X-Host-Fingerprint: 85.13.137.24 dd15934.kasserver.com Linux 2.6
Received: from [85.13.137.24] ([85.13.137.24:60943] helo=dd15934.kasserver.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id D6/81-24198-D1FDB735 for <internals@lists.php.net>; Tue, 20 May 2014 19:02:53 -0400
Received: from dd15934.kasserver.com (dd0802.kasserver.com [85.13.143.1])
	by dd15934.kasserver.com (Postfix) with ESMTPSA id E326826082D;
	Wed, 21 May 2014 01:02:49 +0200 (CEST)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SenderIP: 95.91.211.211
User-Agent: ALL-INKL Webmail 2.11
In-Reply-To: <CAGa2bXa1L4-ok-i8k3W-7zbpea-AU0fYJq0bY32fqEbh4DMFVA@mail.gmail.com>
References: <CAEZPtU4mrOiBzbqZdvxbgxseGo3ZzwgiinkqsgLQEZebrAke6w@mail.gmail.com> <CA+9eiLsMtcYVSvzHW_oc1dXNrDBH8RQ-cb1MgKB5ef2i2mQX7g@mail.gmail.com> <CAEZPtU7Tacn2GS0REbikcn8XKQr04vve=LsGQJZrkUh2oHZsuA@mail.gmail.com> <CA+9eiLu8tgsitvZ0DUCqE8ahQPwE9rDhL9JVzQ5P6meVut4H_w@mail.gmail.com> <CAL0xaBHtsKZr=9V7GLg=K=EjMzObnxUoxjNCd_am7nqFZR1vqA@mail.gmail.com> <CAGa2bXZUCtswupfixjpu7=BG0_dajApxmF8vEWUdZs9mtPnn_w@mail.gmail.com> <CAF+90c85gpvXheKuLtPYs0TN7E=ynb9ALqMuckT60zVWXYZoGg@mail.gmail.com> <CAGa2bXZFiJCasezvuuBc+K67j4W5dCgMVartEUqZrZp+z0JrBA@mail.gmail.com> <CAGa2bXbb6YjTXrL61C0cshXEBBbzYg8HQb7MocJ0GsmAy9sz9w@mail.gmail.com> <537BC669.2030704@sugarcrm.com><CAGa2bXa1L4-ok-i8k3W-7zbpea-AU0fYJq0bY32fqEbh4DMFVA@mail.gmail.com>
To: yohgaki@ohgaki.net
Cc: internals@lists.php.net
Message-ID: <20140520230249.E326826082D@dd15934.kasserver.com>
Date: Wed, 21 May 2014 01:02:49 +0200 (CEST)
Subject: Re: [PHP-DEV] Re: 64bit and phpng, votes and plans
From: mails@thomasbley.de

Hello Yasuo,

I know a lot of companies that switched (or plan to switch) to 5.5 only because of better performance.

Regards,
Thomas


Yasuo Ohgaki wrote on 21.05.2014 00:35:

> Hi Stas,
> 
> On Wed, May 21, 2014 at 6:17 AM, Stas Malyshev <smalyshev@sugarcrm.com>wrote:
> 
>> > 64bit int if int is 64bit. I prefer consistency, so array int key is
>> better
>> > to support
>> > 64bit int key. IMHO.
>>
>> Given that 99.9999% of PHP users will never need it, but 100% of PHP
>> users will pay in performance for each size increase, we need to be
>> careful here. "Consistency" is not more magic word than "security".
>>
>> > Similar argument applies to string also. It would be WTF, when users try
>> to
>> > access string offset over 32bit values. Data dealt with PHP is getting
>> > larger
>> > and larger. It would be an issue sooner or later.
>>
>> Not likely, unless somehow PHP becomes language of choice for processing
>> big data. Which I don't see exactly happening. But if it ever happens,
>> we can deal with it then.
> 
> 
> I think many people don't like PHP and/or switching to other languages are
> concerned
> about consistency as language. Users will just switch tool, so these would
> be issues.
> We just loose users(I mean we loose developers).
> 
> I'm really concerned about performance as much as security/consistency like
> you.
> However, average web developers are not. Most developers prefer large and
> slow
> web app frameworks. This is the reality. I think we must face our
> users(developers).
> 
> Regards,
> 
> --
> Yasuo Ohgaki
> yohgaki@ohgaki.net
>