Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39525 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27620 invoked from network); 1 Aug 2008 10:12:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Aug 2008 10:12:03 -0000 Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6 Received: from [89.208.40.236] ([89.208.40.236:36962] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D4/D0-21097-071E2984 for ; Fri, 01 Aug 2008 06:12:01 -0400 Received: from [192.168.3.91] (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTP id 38F2E6400BD for ; Fri, 1 Aug 2008 14:11:57 +0400 (MSD) Message-ID: <4892E15D.1080004@daylessday.org> Date: Fri, 01 Aug 2008 14:11:41 +0400 User-Agent: Thunderbird 2.0.0.14 (X11/20080421) MIME-Version: 1.0 To: php-dev Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: enabling everything by default From: tony@daylessday.org (Antony Dovgal) Hello all. I'd like to express my feelings on the "let's-enable-it-by-default" mood that has emerged lately. Extensions enabled by default in 5.2: ctype date dom filter hash iconv json libxml pcre PDO pdo_sqlite posix Reflection session SimpleXML SPL SQLite standard tokenizer xml xmlreader xmlwriter ----- Total: 22 extensions Extensions enabled by default in 5.3: ctype date dom ereg fileinfo - new, untested. filter hash iconv json libxml pcre PDO pdo_sqlite Phar - new, untested posix Reflection session SimpleXML SPL SQLite sqlite3 - new, untested standard tokenizer xml xmlreader xmlwriter ------ Total: 26 extensions All of the newly enabled extension are still in development and none of them are known to be stable enough to be even included into the core, but for some weird reason they got even enabled by default (i.e. officially recommended). So we now have 3 (three) SQLite extensions, all of them too slow to be used in real life (because SQLite itself is slow), two PDO extensions (unmaintained, known to cause crashes), json (author's gone for a burton; stability and necessity is arguable), fileinfo extension with no tests and poorly written bundled lib known to cause crashes and we in fact *officially recommend them* by enabling them all by default. So why should we even bother disabling something? Let's enable everything by default, most of the users use --disable-all anyways! I can agree that disabling something that was already enabled in 5.2 might create some confusion, but why enable scarcely created extensions by default, especially if they are known to cause lost of obscure problems in the past (like Phar)? I mean completely no offense to the developers of these extensions, but I would like them (extensions) to be thoroughly tested and mature first, after that we can discuss the question of adding them to the core. And no, they must not be enabled by default unless they bring some extra-useful functionality that the engine lacks (like SPL and reflection do). -- Wbr, Antony Dovgal