Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:91330 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62358 invoked from network); 19 Feb 2016 20:05:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2016 20:05:30 -0000 Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.28.125 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.28.125 mx204.easyname.com Received: from [212.232.28.125] ([212.232.28.125:59048] helo=mx204.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BB/C2-36948-78577C65 for ; Fri, 19 Feb 2016 15:05:28 -0500 Received: from cable-81-173-133-29.netcologne.de ([81.173.133.29] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aWrIq-0003Ir-Lt for internals@lists.php.net; Fri, 19 Feb 2016 20:05:24 +0000 Reply-To: internals@lists.php.net To: internals@lists.php.net Message-ID: <56C77575.4090906@fleshgrinder.com> Date: Fri, 19 Feb 2016 21:05:09 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] [RFC Proposal] var keyword deprecation/removal From: php@fleshgrinder.com (Fleshgrinder) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2/18/2016 10:53 PM, Stanislav Malyshev wrote: > This is all generic advice which is nice and well if we would be > designing language anew. As it is, we are not - we already have > lots of code using var. For code not using var, removing var does > not do anything. For code using var, removing var means no upgrade. > It is unnecessary breakage for the sake of feeling that we follow > the advice somebody put on the website. That feeling is not worth > very real work that people would have to do to achieve what they > already have now. I would not say that the information that the Nielsen Norman Group puts on their website falls in the category of "somebody putting something on a website". https://www.nngroup.com/about/ https://en.wikipedia.org/wiki/Nielsen_Norman_Group Additionally there is other scientific work that supports what I stated, e.g.: http://www.eecs.yorku.ca/research/techreports/1999/CS-1999-08.pdf On 2/18/2016 10:53 PM, Stanislav Malyshev wrote: > Yes, PHP has aliases. Nothing wrong with that, provided you bother > to look in the manual once, and then you are enlightened forever. > [...] It only wastes their time if they don't read the manual but > instead chat on Stackoverflow :) Which I have nothing against, it's > just not the reason to introduce BC breaks because somebody asked a > question about it. A lot of things are wrong with this (see above reasons) and the RTFM argument is a thought-terminating cliché. Duplication harms the overall design of a language, it results in a maintainability burden for the developers, hell, even this discussion is only happening and wasting our time due to these duplications. I am not saying that your arguments about breaking changes and more complicated upgrades for a small user base are wrong; I am saying that these are weak arguments compared to the scientific facts and the overall progress for the PHP programming language. After all, we are talking about an upgrade path of several years. Anyone should be able to adopt by that time and they probably have other problems until then with their old systems. - -- Richard "Fleshgrinder" Fussenegger -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWx3V1AAoJEOKkKcqFPVVrc4cQAINj1zV9lXZAaMGCHrTWjtK8 RC04cjsYzG0XMUa+8wexxmQCkgMSBkRLOWaDa8VyCTbUabHSHi70Zf2mj0qyFQcM rv6DxYVorWDx5ty0odnv+8vgnBra2LHc4OntRGe0GWsM0Z4aQ2QfriMzaAt+diBn gSCC5yPxfE3jjqi4TYuT7eshQ3Kz0SeTAarY19fApi7f80JDwChHeerUiGFMZE3x GUUJi02NeKUnfqliAM0k9VGgAP4qGjmPiVFWjoQKZ9rYPvGRqztLO7c2V+65DlY7 He/vibZDsmvbQZXVcszi2cWNhhzn43XXTwF+jiFuKhlXNLwJJDcJbanfJtQJpEiI MB5adPIROxTtgJdrOBTZ8PMT0IKk4P1i19IUqL6sne4AJtcn3UYEoNUiUiO2TJfP 1zgNfTOAnlmf14jtij2g1wj8XPscjA38zo/2QWzGxadqgsQX6m2NgqlzMV+D6WbH C5KToC5EiF/WNWd/vsViYLCEPusuFzHDx8qWFH0ZiNBdhsMTX6yB+Rt5mKZ2hauY o4+5z4308JPrI8Ao6oroVJ3TqiGN7R8nWUlE3J5/v9psgYVdFMyIe1vXmhtROBo9 N382klHxZHVISis0290HnmdlP8t/g6AevdF3uGHbLEUA8Jzs9LwzrAlUtSBkCNlx 3Yeby46U03XVb3zCZzm3 =1iGy -----END PGP SIGNATURE-----