Re: Function caching...

At 18:45 9/12/2000, Kristian Koehntopp wrote:

Zeev Suraski wrote: I think we've been through this before - what you describe is simply not PHP. But it should be. Will you please accept that PHP has being used for large and complex projects for some years now, and that there is considerable demand for such solutions? Will your company please accept that it is catering to a market that demands scalability?

Let's keep unrelated issues separated please. PHP is not that, and it *shouldn't* be that. The fact PHP is being used for things it's not designed to do, doesn't mean that it should be redesigned to do them. It means that either you picked the wrong tool for the job, or that the right tool for the job does not yet exist. I haven't said in a single word that your ideas are bad. And Zend Tech, as well as other companies, may step into this realm in the future. I do know that wearing my PHP hat, I'll do my best to prevent PHP from becoming what it was never designed to do, and losing the advantages that brought it to where it is today.

It's changing the whole approach PHP is based on. Yes it is, because it needs to. Just look at the problems PHP _has_ in scaling:

IT DOESN'T MATTER! PHP's first design consideration is *EASE OF USE*. If that means that there's an arbitrary limit beyond PHP cannot scale (which it doesn't, IMHO, but lets assume it does) - so be it. Everything you say is all fine and dandy, except it contradicts the first design consideration of PHP, which means it won't make it into PHP. Creating other applications based on the same language syntax, embedding the same scripting engine, is possible, but they won't be PHP. From reading what you say, I'm really not sure why you're even using PHP - all you say is 'this should be redesigned and changed completely, making XXX obsolete'. That's fine - except (at the risk of being repetative) - it's not, it *shouldn't* and it won't be PHP. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/