Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71628 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 61709 invoked from network); 27 Jan 2014 07:52:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jan 2014 07:52:42 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.183 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.183 smtp183.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.183] ([67.192.241.183:51463] helo=smtp183.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/DF-12631-94016E25 for ; Mon, 27 Jan 2014 02:52:41 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp8.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id DF7F980DA; Mon, 27 Jan 2014 02:52:38 -0500 (EST) X-Virus-Scanned: OK Received: by smtp8.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 8A45D80D2; Mon, 27 Jan 2014 02:52:38 -0500 (EST) Message-ID: <52E61045.9000800@sugarcrm.com> Date: Sun, 26 Jan 2014 23:52:37 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Rasmus Lerdorf , PHP Internals References: <52E29253.2000801@lsces.co.uk> <52E2924B.6080002@ajf.me> <52E299D4.6040102@garfieldtech.com> <52E2C98C.6010005@lerdorf.com> In-Reply-To: <52E2C98C.6010005@lerdorf.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Ruminations on PHP 5++ From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > And yes, I know these are much harder and less sexy than adding a couple > of tokens to the yacc grammar, but when we start looking at a new major > release this is what I hear from people who are running PHP in > production environments are looking for. Language features are nice, if > they are well thought out, but significant infrastructure improvements > are nicer. I wholeheartedly agree. There were a lot of attention lately to adding new syntaxes, and not as much attention at all to adding new APIs and improving existing APIs, and in my opinion, language APIs matter no less than syntax, especially in a glue language like PHP, maybe even more. Figuring how to do databases uniformly and take PDO into 21st century would be a huge boon, people could stop reinventing the bicycle of database abstraction layer over and over. We though PDO would take this niche but looks like it wasn't enough. Adding more capabilities like nonblocking operations, or more APIs that now are being reimplemented in each app separately (autoloading? escaping? logging? here feedback from major projects could be very useful). -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227