On Thu, Oct 30, 2014 at 2:30 PM, Florian Margaine <flor...@margaine.com> wrote:
> > > I find this very... useless. Sure, interfaces are not useless. But I don't > think php-src is there to dictate what userland code should look like. It > should provide *implementations*, not interfaces. > Well, let's look at how well providing implementation has worked out for PHP so far. GPC variables are implementation. They pose rigidity to userland code for a number of reasons. For example, if you do send a PUT request to PHP, PHP will not bother populating GPC at all. Instead it leaves the user to define their own handling from the input stream directly. If you do send GET/POST requests to PHP, the variable names can be mangled and $_GET/$_POST are treated differently for encoding as one is run through url_decode and the other is not. $_FILES is also an awkward one as the array is backwardly multidimensional in that $_FILES['userfile'][$meta] are each partitioned rather than having a more intuitive structure wherein one can iterate over the $_FILES['userfile'] array directly. Takeaway: PHP offering up implementation makes userland more rigid. PHP offering up an interface makes userland inherently more appealing and extensible. Take the session interface as one example where we one with interface over implementation. > > > The other thing I don't like in your RFC is the removal of superglobals. > Sure, they're not the best interface out there, but breaking *every single* > codebase out there is not the way to go. Especially if we don't want a > perl6/python3-like failure to adoption. > > I think pitting the Perl 6 and Python 3 scenarios as failure to adoption is like lumping together the Betamax with the Blackberry. Perl 6 failed for a number of reasons, not one of which was an effort to revamp antiquated interfaces. Calling Python 3 a failure to adopt, is a bit ambitious. I don't think people have failed to adopted Python 3. I will tell you what will surely lead to failure, though. When we begin ignoring the problem. Because then we are insisting that the proposed solutions are useless since there is no problem to solve. There is an evident problem in the way PHP handles the incoming Http Request and how it makes it accessible to userland. Whether or not this solution is optimal remains to be seen, but to say that the problem itself is non-existent is pure denial without basis. A failure to act is worse than an act of failure. > Regards, > > -- > Florian Margaine >
