But it should be. Will you please accept that PHP has being used
for large and complex projects for some years now, and that
there is considerable demand for such solutions? Will your
company please accept that it is catering to a market that
demands scalability?
I agree with Kristian, Ulf, Björn and numerous others. What PHP originally was designed for and what it is now is not the same. I have had similar problems using PHP for complex applications (in fact I have started to design a simple "function caching" function too a year before or so), while my problems were based on reference/OO implementation limitations. A kind of "strong typed OO" extension on top of the current situation already has been discussed and IIRC it was considered reasonable.
PHP at the moment is no longer running personal home pages. It
is running large webshops, is doing SAP integration and
strategic backend duties. It is running large content management
systems.
The users of PHP - YOUR CUSTOMERS, do you get that! - are
planning to deploy it into the enterprise. They see PHP as a
direct competitor to ASP+ and .NET.
You have condemned yourself and your investors to provide the
scalability and performance they need to do this. You won't cut
a thing at this level without the exact architecture I described
above for the reasons I described. You won't get a sniff of
enterprise level business without an object framework properly
done.
I can only duplicate the above.
Remember, the primary concern for PHP is usability and ease of
use, and performance does come in second.
There is no need for such a static order. If performance drains are getting such massive it becomes a primary objective
than to hire&train more people, and have longer development
times. In my opinion, the day performance becomes more
important than ease of use, would be the starting day of PHP's
downfall.
disagreeing. if a large number of low-end scripts experience a performance drain due to a high-end extension/modification which improves the situation for high-end scripts dramatically,
well, who cares???? these low-end scripts simply do not need every percent of performance they had in plus before.
who cares if a 5000 forms on 5000 different pages are processed a few ms slower?
who cares if 5000-* users are waiting 2-*s longer getting their content on mid/large scale sites?
whenever I have time surfing through the web I wonder how many mid/large scale sites are using PHP and I bet all of them would greatly welcome some of these features discussed before.
the current sitution is, that PHP allows anyone to build mid-scale sized apps and the more complex these apps become from that point on the more problems the developers run in
regards,
andré