Cool, thanks for the tip.<br><br>In other words, your argument (again) boils down to "reject GREAT, because we've already got GOOD ENOUGH."<br><br>You're not solving the problem, you're minimizing it.<br>
<br><br><br><br><div class="gmail_quote">On Sun, Jul 3, 2011 at 2:34 AM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com">otto@ottodestruct.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Sun, Jul 3, 2011 at 2:32 AM, Darren Slatten <<a href="mailto:darrenslatten@gmail.com">darrenslatten@gmail.com</a>> wrote:<br>
> An extra HTTP request obviously doesn't come free, so...yes, a 308-byte<br>
> script really does slow down your page loads.<br>
><br>
> I'm not sure what you're basing your "caches everywhere" statement on, but I<br>
> know that l10n.js is packaged with WP and served from each site's respective<br>
> directory (as opposed to being served from a public resource like<br>
> Google-hosted jQuery). Therefore, whether or not it is cached depends on<br>
> each server configuration--most of which follow the default behavior, which<br>
> is to NOT cache the file.<br>
<br>
</div>If you don't set up your server to send caching headers for static<br>
files properly in the first place, then you haven't even begun to<br>
start to think about optimizing your site for speed. That's like step<br>
1. It's not like it's hard to do. Heck, you can copy-pasta some<br>
htaccess rules to do the job.<br>
<div><div></div><div class="h5"><br>
-Otto<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</div></div></blockquote></div><br>