Date: 12/09/00
- Next message: Zeev Suraski: "Re: [PHP-DEV] Function caching..."
- Previous message: Apis Hytt: "Re: [PHP-DEV] --- PHP QA 4.0.4RC3 Build & Bugs Summary --- [06-Dec-2000]"
- In reply to: Kristian Koehntopp: "Re: FW: [PHP-DEV] Function caching..."
- Reply: Sebastian Bergmann: "Re: FW: [PHP-DEV] Function caching..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 21:46 9/12/2000, Kristian Koehntopp wrote:
>Zeev Suraski wrote:
> > >I think it will kill PHP if you take away any (great) possibility to
> evolve
> >
> > I agree, except Kristian is talking about a revolution, not evolution.
>
>I don't. Or maybe I do, regarding some internals of the
>language. If it is visible from the outside, the implementation
>would be a failure, though.
>
>Clearly the migration path should be as easy as possible: You
>should be able to take PEAR classes, phpmyadmin, PHPLIB,
>QuickCMS and things like that and install them in the
>application server execution model with no or minimal changes.
>This will not kill anything, if done right.
I think you underestimate how far you went with your revolution. Suddenly,
you'd have to begin worrying about using too many variables or resources,
because they'd never get cleaned/destroyed. I don't think any reasonable
PHP application will work efficiently on that appserver you propose without
serious rewrites.
I'm not sure if you noticed, but the whole argument I have with you is
whether this appserver should be PHP (or rather, the other way around). My
answer is a clear and definite 'no'. It doesn't mean that such an
appserver shouldn't exist. Call it FooHP. Call it Zend AppServer. Call
it whatever you want, just don't say it's PHP, because it isn't. PHP
should remain what it was, a scripting language for developing dynamic Web
sites.
>Of course, to take full advantage of the application servers
>advantages, you'd have to rewrite parts of these applications,
>but that is another issue.
As I mentioned, I think it's more like 'to make your applications run
reasonably well, you'd have to rewrite large parts of it'.
>Nobody is cutting anything here. I don't cut roots, and the
>current mod_php does not cut it when it comes to enterprise
>league application deployment.
To some extent you're right. It doesn't mean we should change mod_php
though, as it fits the vast majority of usages other than those specific
enterprise application requirements.
Zeev
-- Zeev Suraski <zeev <email protected>> CTO, Zend Technologies Ltd. http://www.zend.com/-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Zeev Suraski: "Re: [PHP-DEV] Function caching..."
- Previous message: Apis Hytt: "Re: [PHP-DEV] --- PHP QA 4.0.4RC3 Build & Bugs Summary --- [06-Dec-2000]"
- In reply to: Kristian Koehntopp: "Re: FW: [PHP-DEV] Function caching..."
- Reply: Sebastian Bergmann: "Re: FW: [PHP-DEV] Function caching..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

