Re: Function caching...

On Sat, 9 Dec 2000, Zeev Suraski wrote the following to Björn Schotte : > Well, you have to go back to the definition of the PHP project, and remind > yourself all the time that PHP is not Zend's toy. So in theory, even if I > agreed with you that PHP's design is faulty and we should say 'screw the > average user, let's create an enterprise-oriented-only language', I > wouldn't have been able to convince the rest of the PHP developers to do > that, and I'm happy it's that way. Especially as I disagree with you and > believe that PHP's design should remain as it is. > > I'm not sure how many times I repeated this today, but here's another one: > - PHP's design is not faulty, and should/will remain intact. > - Components that complement, extend or reuse parts of PHP are very likely > to come out in the future, that would address various concerns you > had. They will do that without chopping down the branch we're all sitting on. > > Zeev I want to throw my $0.02 in here. It has been said over and over by both Zeev and Rasmus that PHP is not intended as an application server. It is not what it was designed to be, and I do not want to see it go in that direction. I *would* love to see an application server written that accepts PHP syntax, and can load modules written that were written for PHP. But that's not what I want PHP itself to become. IIUC, Such an application server could theoretically be written using the Zend engine as its backend. But since the OOP support in Zend has some holes (as all of the Core team has admitted repeatedly), perhaps a new engine should be written, so that it is compatible with Zend and PHP modules. In either case, I do not think that we need to beat up on PHP because we are trying to use it for things it was never intended for. No one suggests fixing Excel because I cannot use it as a full-fledged word processor (although it is close ;). Instead, they use a word processor to do word processing. The same holds true for PHP/Application Server, IMHO.