The language module is a 1.5MB JavaScript beast and people routinely complain about 150KB frameworks on HN. Are there plans to have a whole program optimisation pass to prune dead parts of that module (a ceylon webpack or ceylon closure command) ?
It seems to me that the best solution here is to split the single file into one js file for each package. A big part of that file is the implementation of the metamodel, and it's very likely that a lot of people won't even want to use that on the client side.
We've even discussed the pros and cons of actually splitting the metamodel into its own separate module, ceylon.metamodel, or whatever.
P.S. My tests with uglify-js suggest that minification probably isn't the most fruitful path here.
Once minified and gzipped it's less than 200K. But yeah, I can see how a packing command would be useful with program analysis, except that'd rule out any use of the metamodel for dynamic programming.
marvelous|10 years ago
The language module is a 1.5MB JavaScript beast and people routinely complain about 150KB frameworks on HN. Are there plans to have a whole program optimisation pass to prune dead parts of that module (a ceylon webpack or ceylon closure command) ?
gavinking|10 years ago
We've even discussed the pros and cons of actually splitting the metamodel into its own separate module, ceylon.metamodel, or whatever.
P.S. My tests with uglify-js suggest that minification probably isn't the most fruitful path here.
UnFroMage|10 years ago