Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101075 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16254 invoked from network); 7 Nov 2017 10:21:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Nov 2017 10:21:19 -0000 X-Host-Fingerprint: 62.31.75.76 76.75-31-62.static.virginmediabusiness.co.uk Received: from [62.31.75.76] ([62.31.75.76:28551] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E2/CE-09857-E19810A5 for ; Tue, 07 Nov 2017 05:21:19 -0500 Message-ID: To: internals@lists.php.net References: <64.21.07742.EF158F95@pb1.pair.com> <71.50.09857.3BBEAF95@pb1.pair.com> <6643d10b-8703-693c-15c2-da338022ef41@rhsoft.net> <18.19.09857.3E54CF95@pb1.pair.com> <941fd347-4a17-78b6-1bd7-4a5519aa722b@rhsoft.net> <67.8E.09857.7D58DF95@pb1.pair.com> <6A.75.09857.9F6EEF95@pb1.pair.com> <55fb932f-7f61-33eb-1fd9-aa425bc6ff27@rhsoft.net> <748869f7-13bb-5bdd-6fec-399a33b790b3@rhsoft.net> In-Reply-To: <748869f7-13bb-5bdd-6fec-399a33b790b3@rhsoft.net> Date: Tue, 7 Nov 2017 10:21:15 -0000 Lines: 2 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Newsreader: Microsoft Windows Live Mail 16.4.3564.1216 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3564.1216 X-Posted-By: 62.31.75.76 Subject: Re: [PHP-DEV] Re: RFC - Array Of for PHP 7 From: TonyMarston@hotmail.com ("Tony Marston") wrote in message news:748869f7-13bb-5bdd-6fec-399a33b790b3@rhsoft.net... > > > >Am 06.11.2017 um 12:09 schrieb Tony Marston: >> wrote in message news:55fb932f-7f61-33eb-1fd9-aa425bc6ff27@rhsoft.net... >>> Am 05.11.2017 um 11:24 schrieb Tony Marston: >>>> wrote in message >>>> news:d70cc49d-c397-3f09-d08d-b79b31014271@rhsoft.net... >>>>> it depends on the implementation and just beause you say so does not >>>>> prove anything and even if you need to measure, optimize and make >>>>> decisions based on technical facts - what you do is "mimimi i say" >>>> >>>> I have worked on software which provided lots of different options, >>>> which means that you have to keep testing if an option is being used or >>>> not. This is an overhead whether you like it or not. >>> >>> maybe your implementation was bad >> >> Everybody knows that carrying around code which is either rarely used or >> not used at all is an overhead > >everybody knows that claims without measure the impact are worthless Some things are so obvious that they do not need scientific proof. For example, in a motor vehicle the power-to-weight ratio is important as it affects engine performance and fuel economy. In other words, for a given engine size the lower the weight of the car and the better the fuel consumption. The more weight you add the lower the performance. Your car has a heater which you only use when it's cold. It also has an air conditioner for when it's hot. It has windscreen wipers, and a motor, for when it's raining. When the temperature is mild and it's not raining it means that you are not using any of this equipment, yet you are still carrying their weight, and this weight is affecting your car's performance. I do not have to supply any figures as proof as the car manufacturers keep telling us that cars that weigh less perform better, which is why they try to reduce the weight of as any components as possible. It is the same with software. The more code you carry around that is not being used then the worse it will perform. Esoteric code which uses clever features to perform tasks which can already be performed with simple code is, IMHO, an unnecessary complication which benefits only those lazy programmers who are obsessed with reducing the number of keystrokes. Taking out the rarely used complicated stuff and concentrating on making the commonly used stuff as fast and efficient as possible is what drove the efforts in the RISC architecture. I was around when that happened, so I know what I'm talking about. -- Tony Marston