On Tue, Feb 24, 2009 at 7:29 PM, Brion Vibber brion@wikimedia.org wrote:
On 2/24/09 4:17 PM, Sergey Chernyshev wrote:
As mentioned already, I'm not sure if localization is the best for
candidate
for being held in JavaScript, but other things mentioned, e.g. single request, minified and infinitely cached JS is what I'm looking at for overall MW infrastructure - so far it's a big performance problem for MW
[snip]
Mmm, did you see the thread "Javascript localization, minify, gzip & cache forever" including proof of concept code which is covering this ground?
Yes, of course - I checked it out and that's why I quoted it in my original email. My brief overview made me feel that it wasn't enough.
I just didn't want this to be only in context of localization as performance is more related to overall user experience then to multilingual support.
I'll try to summarize what might be the goals of front-end performance optimizations.
How do we go about doing this? Can it be tied into Usability project (
That is far outside the scope of the usability project.
Yes, I took a look at the project and it seems that UI performance wasn't deemed important in this Usability initiative. This is not necessarily good, but I can understand why it concentrates on navigation, colors and editing UI.
-- brion
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l