--- Comment #5 from Merlijn van Deen <> ---
(In reply to Niklas Laxström from comment #4)
> I can understand that, but I'm not convinced it is a bottle neck currently.

As I mentioned, I *measured* the time needed to parse JSON files. For Mediawiki
core, this takes *multiple seconds*. That's *multiple seconds* during *startup*
of *each* script.

Currently, each script needs to read a single file, that's also in a format
that's loaded quickly (the python bytecode is cached).

(In reply to Niklas Laxström from comment #4)
> I am weighing this against the development effort needed in Translate to
> support it.

I assume you are aware this switch won't exactly be free in terms of *our*
time, either, right? I'd rather work on site-based configuration, or python 3
support, instead of changing a file format for the sake of changing it.

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to