Hi all, I didn't answer this question and would like to make my point of view clear.
On Thu, Oct 20, 2016 at 9:41 PM, Stephen Reay <php-li...@koalephant.com> wrote: > Why is your concern so focussed on solving problems for inexperienced > developers, who are effectively using functions incorrectly, at the expense > of experienced developers who are doing the right thing? The reason why I'm focusing on problems for inexperienced developers is productivity with PHP. IMHO, it is better to remove gocha whenever it is possible. It's okay to read manual and search net to solve "obvious problem in code". However, if 10K developers spend 10 hours to solve a problem, 100K hours of productivity with PHP is lost. The change may have small impact, but small things add up. As long as there is reasonable alternative way to implement advanced behaviors and small impact on existing codes, it is better to provide easy and safe default behaviors. Making PHP easy to use and a productive language worths in the long run. This is the reason why some of my proposals are focusing on making PHP easy to use and safe to use by default. e.g. Provide correct and safe session management by default, prevent insane session usage and raise errors for them, add DbC support, make uniqid more unique, consistent function names, disallow script inclusion attacks, keep/improve URL rewriter rather than depreciating it (URL rewriter is _very_ useful to keep private site private, i.e. Disallow all cross site requests, therefore disallow CSRF, XSS completely. PHP 7.1 has dedicated output buffer and setting for user URL rewrite. It's easier and safer to use with PHP 7.1), etc. PHP is popular because it is easy to use and productive. Let's keep this and improve! Other languages/platforms are catching up. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
