steve wrote: > > I don't think PHP has as much support as you think it does. There is > no big supporter to fund a real development drive like that.
I'd like to think that I've more or less worked out who supports PHP by now. I know I don't go to many conferences but I haven't been living in a cave these past 6 years. > I doubt anyone does I1/D1/L2 cache profiling for PHP. I did a little bit of CPU cache profiling of PHP using oprofile, more out of curiosity than anything. It was a couple of years ago now. http://wikitech.wikimedia.org/view/Oprofile But you don't need oprofile, you can make changes based on theory, and then measure the execution time of the result. > PHP doesn't ship with an optimizer, byte code cache, or JIT. But community members are developing those things nonetheless. eAccelerator has an optimizer, there are several so-called byte code caches, and Roadsend is a promising compiler project. I think you're underestimating the PHP community. > Rasmus had the idea that it should > do simple things and be easy, and if you were going to do anything > else, then you should have the money to do so. Fair enough really. > Rasmus is not the whole community. Sometimes community members have spare time or the freedom to choose what they work on. I put these ideas out on this list in the hopes that someone might be inspired by them. Also it's nice to get feedback in case I decide to have a go at one of them myself. -- Tim Starling -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
