> However, I think that an encoder > should not be part of the default php distribution, because it would > *force* people to use the encoder supplied
and > Also, it would seem that PHP was endorsing one product over another, and > such things are never good. Yes. The problem that you are describing comes from the fact that there actually are those products. Had that functionality been in the PHP from start, nobody would notice. A burden from history, it is now. It would be certainly bad for the individual encoding products if PHP developers decided now to create the encoding right into PHP core, for example, but, I think it would be good for PHP language to have that feature by default. How is there going to be any big business in shrink wrap PHP software if there isn't a way to protect the source code, other than buying & installing some additional software to go with it. Maybe this thread belongs to php.evangelism... > What I'm afriad is if things like "why don't we include x in the default > php install" start, then soon we'll have "why don't we include y in the > default php install", which would lead to unecessary bloat Well, a new feature cannot be turned out just because it would add some more kilobytes. That feature needs tu be judged by what benefits it would bring along those kilobytes. JS Disclaimer: I may sound strict and intimidating, but my bread & butter may depend on things like this. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
