I am interested in many of the improvements, but I want to put my votes out for 
startup performance and AOT compilation (which hopefully also provides startup 
time improvements). In particular, startup performance for embedded usage (so, 
nailgun won't work).

Some JAR size reduction would be nice too, which may also be accomplished by 
AOT compilation + modularization.

Peter 

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of 
Charles Oliver Nutter
Sent: Saturday, February 28, 2009 3:12 PM
To: [email protected]
Subject: [jruby-dev] Setting priorities for 1.3

With 1.2 almost out the door, we should talk a bit about where to go
with 1.3. There's always more work to do, but in this case there's a few
directions we could probably go.

Some obvious items will continue to see work:

* 1.9 libraries, interp, compiler, parser
* 1.8.6 bugs

But there's others that we may need to prioritize:

* Ruby code execution performance
* Specific library performance (YAML, IO, Java)
* More Java integration refactoring (esp. subclassing)
* "Compiler #2" to produce normal Java classes from Ruby
* Improvements to AOT compilation (all-at-once, eliminate runtime codegen)

And there's a number of internal chores to work on too:

* Start generating most of the call path, to reduce duplicate code
* Specific-arity optimizations for block yield (could be big)
* Compiler cleanup and refactoring
* Modularization of core classes that aren't valid on applet, Android,
secured envs, etc; also may allow shipping smaller runtimes
* More startup perf work; I have a few ideas

As always, there's way more work than the few of us committing can do,
so I think we need to hear from users what's important. Any of these?
Other items?

- Charlie

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to