|
You're getting something seriously wrong here. As NiLuJe said, you're comparing apples with oranges.
Having these "unused" language-specific jar files in the classpath has negligible impact on CPU performance and zero impact on memory requirement.
Why? Because classes are looked up and loaded exactly once in, namely when they are first needed. Say you want to load a ResourceBundle named "squirrel", and your language is ja_JP. Then (at most), the following three classes will be loaded: squirrel_ja_JP, squirrel_ja, squirrel.
While looking up these classes, yes, the "unneeded" jars will be searched. But this is fast, because one only has to look at the jar file's central directory.
So, while I appreciate your effort, I think that this is a really bad idea. You are not gaining anything (except for a speedup that can probably be measured in milliseconds, or at most seconds, over the entire runtime of the Kindle), but you're breaking functionality.
|