Just have had several ideas I wanted to dump somewhere, and this seemed
like as good a place as any.
1. We could reduce the number of binding classes we create if we stacked
them up; so if you have method A that takes one arg and method B that
takes two, we could generate them both into the same class and reuse
that invoker. Not sure how much it would gain us.
2. I posted a sample of what static compilation to a "real live Java
class" might look like here: http://gist.github.com/37000. The idea is
that you'd decorate the class with a little extra Java information, and
then a compiler could create this Java class that exposes everything a
Java application would need to construct it as a normal object. I think
it could probably be written all in Ruby, without too much difficulty.
Thoughts?
3. We could use pack200 to reduce the size of the JRuby download
somewhat. Currently the JRuby jar we ship compresses to about 7MB. If we
pack200 it would be around 2.5MB. We would then add logic to the startup
scripts to unpack it the first time. Thoughts?
4. Tom had the idea to ship rdocs in an archived format, possibly as a
JavaDB database. Currently the share/ri/1.8/system dir takes up 36MB on
my system with 512k blocks; on a system with larger blocks it would
waste a lot of space. Shipping as a single file would be much more
compact and maybe even faster. Thoughts?
That's all for now!
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
