i18n in Frameworks, the lightweight version

[Stephen Kelly]

Aaron J. Seigo wrote:

> On Tuesday, December 6, 2011 14:14:44 Chusslove Illich wrote:
>> > [: Aaron J. Seigo :]
>> > when there is already one implementation that comes bundled with Qt and
>> > does everything needed/wanted, it is simply impossible to justify that
>> > kind of dependency on a small device. [...] in this case, another
>> > option is to not remove translation scripting on such systems (and
>> > therefore the dependency), but that would be a shame imho.
>> 
>> Frankly, I'm inclined to completely ignore such a limited device in any
>> decision concerning a general piece of software.
> 
> you are free to ignore it. hopefully i am free to not ignore it, however.
> :)
> 
> with plasma active, our mid-term goal is to get disk and memory usage down
> to the point where we can confidently put it on devices with 256MB of RAM
> and less than 1GB of storage and have something pleasant and usable. we
> have a ways to go yet (obviously :), but if we get blocked from making
> these kinds of changes in frameworks code then we're unlikely to achieve
> success.
> 
> so if the optimization can be made without side effects and someone is
> willing to do the work, how can we justify saying "no, please don't
> improve the code"?
> 
> as a team collaborating on frameworks, we need to be sensitive to the
> needs and goals of each other and accomodate those goals when they don't
> conflict with our own. and when they do conflict, we should work on
> finding compromise if possible.
> 
> hopefully that makes sense to everyone :)
> 

It makes sense to me at least.

By the way with Qt 5 and QtScript you will already be using two JS 
interpreters: JSC in QtScript and v8 with declarative/webkit. KJS would be a 
third.

Thanks,

Steve.