Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:22828 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14770 invoked by uid 1010); 18 Apr 2006 10:53:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 14753 invoked from network); 18 Apr 2006 10:53:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Apr 2006 10:53:35 -0000 X-Host-Fingerprint: 81.103.221.49 mta09-winn.ispmail.ntl.com Solaris 8 (1) Received: from ([81.103.221.49:45401] helo=mtaout03-winn.ispmail.ntl.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 3F/78-19715-D25C4444 for ; Tue, 18 Apr 2006 06:53:33 -0400 Received: from aamtaout03-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20060418105329.FUYD27969.mtaout03-winn.ispmail.ntl.com@aamtaout03-winn.ispmail.ntl.com>; Tue, 18 Apr 2006 11:53:29 +0100 Received: from [192.168.0.20] (really [86.2.124.185]) by aamtaout03-winn.ispmail.ntl.com with ESMTP id <20060418105329.IMTL16286.aamtaout03-winn.ispmail.ntl.com@[192.168.0.20]>; Tue, 18 Apr 2006 11:53:29 +0100 Message-ID: <4444C529.4010601@fission.org.uk> Date: Tue, 18 Apr 2006 11:53:29 +0100 User-Agent: Thunderbird 1.5 (X11/20060309) MIME-Version: 1.0 To: James Crane CC: php internals References: <2a8d4a710604180325m68d7b779x880fafbf0be1f48d@mail.gmail.com> In-Reply-To: <2a8d4a710604180325m68d7b779x880fafbf0be1f48d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] "Pushing PHP Into The Web 2.0 Generation" From: gareth@fission.org.uk (Gareth Ardron) James Crane wrote: > I've written a short paper on the future of PHP and I'd appreciate it > if you folks would take a look at it and exchange your thoughts with > me. > > http://www.maraby.com/papers/pushing_php_into_the_web_20_generation > > Don't be too skeptical. ;) > Not being funny, but the one thing you seem to suggest is "everything as objects within php" - Quite aside from totally disagreeing with your logic in this, I don't see the point. One of the strengths of php is that it can be used both as a procedural and OO language (or anywhere inbetween) - what you're arguing for can all be accomplished within userspace. I really dont' get what you're trying to achieve with this - maybe I've just totally missed the point, but just saying that PHP is blind to inherent dangers without saying either why they are dangers or in what way php is blind to them doesn't do anything to convince me that this is anything more than your personal preference on how you would like to see the language working. "web2.0" or whatever is afterall, bloody hard to impliment in a real-world situation when dealing with corporate clients. Fine for home users but it's all high-level client side stuff like javascript doing the real interface stuff. Given that loads of corporations outright ban javascript, this causes quite a problem. I don't see why php needs to do anything on this front really, it's a userspace issue.