Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56856 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47283 invoked from network); 9 Dec 2011 16:46:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Dec 2011 16:46:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:35656] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 66/F0-41208-47B32EE4 for ; Fri, 09 Dec 2011 11:46:45 -0500 Received: from [192.168.2.230] (ppp-93-104-54-47.dynamic.mnet-online.de [93.104.54.47]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 6B4EB5FCB3; Fri, 9 Dec 2011 17:46:41 +0100 (CET) To: Rasmus Schultz Cc: internals@lists.php.net In-Reply-To: References: <4EE14E10.5050403@lerdorf.com> <4EE1534A.5070701@lerdorf.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 09 Dec 2011 17:46:36 +0100 Message-ID: <1323449196.2602.17.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Phalanger From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Fri, 2011-12-09 at 08:58 -0500, Rasmus Schultz wrote: > What I'm proposing (and what Phalanger does) is to compile PHP code to > CLR > bytecode, and running it directly on the VM - I'm not saying run an > interpreter under the VM. That would be pointless. For *this* group there's little sense in migrating away - barely anybody here is used to writing C# code and even less knowledge bout CLR internals. We're quite used to C, though. Therefore another group has to do such an implementation (and obviously does) and then users may decide. So in the end you have to ask users why they won't migrate. Some reasons I can see are - PHP in it's current implementation is ubiquitous - It is proven - There are people who can administer it - It is known to be able to scale quite a lot - It can easily be extended with C to get machine performance where that matters or to connect to C/C++ libraries - Tons of existing applications are known to work on that platform - ... btw. there's not only Phalanger but also Quercus or HiHop, and some others none of those sees to really attract masses of users. johannes