Re: Class Destruction / Reloading
| From: | Rasmus Lerdorf | Date: | Thu, 01 Jan 1970 00:00:00 +0000 |
| Subject: | Re: Class Destruction / Reloading | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-12246@lists.php.net to get a copy of this message | ||
On Wed, 18 Aug 2004, Sean Coates wrote:
The fact that various features and add-ons exist that make PHP useful outside of the web space does not in any way imply that focus is shifting away from web applications as the primary use of PHP. Things that can be done that don't intefere with that primary use and model and are generally useful to people will be done. Things that in any way hamper that primary use face a stiff uphill battle when it comes to being accepted. All this talk of PHP becoming Java or other such nonsense is getting annoying. PHP is getting stronger in order to provide more powerful tools to solve the same set of problems people have been using PHP for all along. -RasmusMy chicken and egg comment was this logic: Marcus: the reason we don't need this is because we don't have [an application server] that would require it. Sean: the reason we need it is because I'd like to develop [an application server] Where [...] could be anything. I understand the common use of PHP. Do we expect PHP to grow into a general purpose language? (if not, then I think I misunderstand the CLI SAPI).I think Sean is talking about creating an application server _in PHP_.I understood that.