Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:52489
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain garfieldtech.com from 66.111.4.28 cause and error)
Message-ID: <4DD6B136.6060508@garfieldtech.com>
Date: Fri, 20 May 2011 13:21:42 -0500
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110414 SUSE/3.1.10 Thunderbird/3.1.10
MIME-Version: 1.0
To: internals@lists.php.net
References: <4DD693BB.7030300@garfieldtech.com>	 <1305909198.1318.13.camel@guybrush>  <4DD69AB2.8050005@garfieldtech.com> <1305910898.1318.21.camel@guybrush>
In-Reply-To: <1305910898.1318.21.camel@guybrush>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Porting PECL to userspace
From: larry@garfieldtech.com (Larry Garfield)

On 05/20/2011 12:01 PM, Johannes Schlüter wrote:
> On Fri, 2011-05-20 at 11:45 -0500, Larry Garfield wrote:
>> If the long term result is that PECL gets more attention and usage as
>> people realize the advantages of C-based code, even better.
> I think it's the exact opposite - the less C code we need the better.
> Developing C code is more work. Maintaining C code is more work.
> Distributing C code is more complicated. The less this is needed, the
> faster PHP is, the better for everybody (except C programmers ;-) )
>
> johannes

Unless the C code already exists and is already tested, as is the case 
with existing PECL modules.  Wasn't that the original intent with PHP, 
to stitch together C libraries that you could use more easily?

--Larry Garfield