I'm anxious to see more 1.9 support.
I'd also love to see some of the java integration bugs get fixed, but
I think that ball is in my court for getting specs to produce said
bugs, and I don't know how many users are utilizing these features
right now (the amount of Monkeybars users could probably be counted on
my hands). In short, it would be nice, but I expect other things will
reasonably take higher priority (:
On Feb 28, 2009, at 2:11 PM, Charles Oliver Nutter wrote:
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
