>> Then is there any reason not to add all code compatible in php license >> terms >> into php core? > > What are you talking about? Who said that we have to add any php > licensed code to the core? I only said that the license is a critical > part of the decision. Nothing else.
APC can be added, this fact does not mean that it should be added. So the license compatibility argument is neutral for adding or not adding APC. >> This approach will only reduce competition and will shrink the market. > > As of now the only competitor actually reducing competition is Zend > (no offense meant to the Zend guys), and the reasons are not technical > but marketing related. I don't think we can do anything like that or > anything against that. I didn't see any attempts from Zend to add NOT REQUIRED PHP MODULES into the core. They are going by a clear way and their efforts can't be underestimated. As I see they are changing the core in a right way: check for example zend_vm_xxx added in 5.1, check the proposed and implemented improvements in memory management etc. This all makes php position on the market stronger, so the competition between php and the other web-languages is NOT reduced by Zend efforts. Competition between opcode caches for php will definitely be reduced by adding APC into the core, so the market will shrink, of course. What can be further done for php performance improvements (if you care of it at all) is garbage collector, copy-on-write, and possibly jit compiler for some platforms. These techniques will put php on par with the best propriatary languages available for the web, or may be will make php even better. Meanwhile the benefit comming with php is a balance between cost, features, and stability. Don't break it. As of adding APC into the core, I expect more problems to come and nothing would be solved. -jv -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
