Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2700
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: ilia@prohost.org
To: Dan Kalowsky <dank@deadmime.org>,
 internals@lists.php.net,
 Philip Olson <philip@cornado.com>
Date: Tue, 24 Jun 2003 10:24:04 -0400
User-Agent: KMail/1.5
References: <1056335922.11754.20.camel@hasele> <20030623134526.A82269-100000@x-wing.brouda.com>
In-Reply-To: <20030623134526.A82269-100000@x-wing.brouda.com>
Organization: Prohost.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200306241024.04414.ilia@prohost.org>
Subject: Re: [PHP-DEV] enabling sqlite by default
From: ilia@prohost.org ("Ilia A.")

On June 23, 2003 01:48 pm, Dan Kalowsky wrote:
> As always I'm against any enable by default thinking.
> Why, oh why, are we making this wonderful configure script
> completely useless?

In a perfect world nothing would be enabled by default and each user would 
enable just the extensions they wont. In reality however, most people use 
shared webhosts and have no control over PHP and in many cases web hosts will 
refuse to modify their PHP installation. The same webhosts (judging from my 
personal experience with at least 4-5 dosen hosting companies) usually rely 
on the default configuration options, with only non-default options being the 
ones relating to safe_mode. What this means if we disable MySQL by default, 
the stock php will no longer come with a built-in database support. This IMHO 
is very bad, since large number of php scripts require a database of some 
sort.
Enabling by the extension by default would also accelerate it's addoption by 
distributable script authors, who won't have to worry about availability of 
the extension. I think we can all agree that MySQL's popularity with PHP is 
largely the result of it nearly always being avaliable.

Ilia