Re: Compressessed Smarty class

On Tue, 6 Jul 2004 16:02:46 -0700 (PDT), you wrote:
>Sorry--I meant that rhetorically. I guess I should have added a smiley
>:) A decent opcode cache should remove any concerns over whitespace and

:)

And I was possibly too diplomatic in my comments trying to
cover the attitude: "doesn't that *.* reallly understand the way
an opcode cache really works"  :) :)

>Evidently, not everyone has the luxury of using such a service (but
>particularly with Smarty, every attempt should be made to use one, even
>on "lowly" machines) so there is certainly merit in squishing your code

That's very true. On the other hand the three dozen or so applications
we have written are in-house ones and we have a small Sun server
running idle most of the time, Loading three or four classess (of
which Smarty is the biggest) is not a problem for us. I understand,
though, people who must write and run software in public servers
with hundreds or thousands of simultaneous users and that is where
saving every millisecond may be meaningful.

The only true problems with PHP I have come across so far are
related to very complex string handling where PHP really sucks
in comparison with Java, for instance.

-- 
Smarty Development Mailing List (http://smarty.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php