[josm-dev] .jar file size is too big

Frederik Ramm frederik at remote.org
Wed Jul 15 19:39:20 BST 2009


Devs,

    I am a bit concerned about the fact that the JOSM .jar file has 
grown from 1.7 MB to 5.5 MB in the last 12 months, that's factor 3.2. 
With all due respect, I do not think that JOSM is now 3.2 times as good 
as it was one year ago - it certainly is better but on average we seem 
to be suffering from bloat - the size of the program grows faster than 
its use.

This is going to come back to haunt us if we want to do JOSM as a Java 
web start application, or even as an applet, one of which is likely 
going to happen when the API allows users to configure which editor they 
would like to see behind the "edit" tab.

So everyone please think twice before you add that cool extra library 
into JOSM. Do we need

images/styles/standard/rendering/cliff.png

with 26 kBytes? Or

images/styles/standard/rendering/track/mini_round.png

with the same size?

Who has added the com/drew/imaging and com/drew/metadata stuff - does 
the JOSM *core* really have to have special knowledge about 
"CasioType1MakerNote"s?

Can we perhaps think of a way to dynamically load the language support 
instead of burdening *every* downloader with megabytes of translations 
in languages he will never select? This is very unlikely to scale well.

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"




More information about the josm-dev mailing list