On Tuesday, June 24, 2003, at 10:56 AM, Ilia A. wrote:
On June 24, 2003 10:40 am, George Schlossnagle wrote:I dig including it in ext, and bundling the full sqlite sources as well. I just don't think it should be enabled by default.
Enabling sqlite by default has virtually no performance impact. Your binary is
increased by roughly 100k and you initialize a dosen or so constants on
startup. Comparatively speaking it is much 'nicer' then tokenizer (enabled by
default) which initialized couple hundred constants at start up.
I'm not approaching this from a performance standpoint, but from one where statically compiled extensions slow the overall release process, make it difficult for users to incrementally upgrade their extensions, and generally contribute to bloat.
Most users don't care much about incrementally upgrading their extensions. Those that do it today are still the exception to the rule, and my estimate is that they'd stay the exception to the rule even when PECL becomes user-friendly, too (whether they're 0.1% or 5%, they're still a small minority). Letting the majority enjoy an out-of-the-box SQL solution far outweighs the need for this minority to add --without-sqllite.
About slowing down the overall release process - I don't see why it should be related. It was discussed a lot of times, we can simply ship the latest version that's tagged stable of each extension that we choose to bundle.
I never dug into the lean-and-mean approach, I still think that finding the features which are most important and enabling them by default is one of the reasons for PHP's tremendous success.
Zeev
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
