Ola Bini wrote:
1.1.2: (3-5 weeks from now?)

For Railsconfish then...seems pretty good to me.

- general bug fixes
- serial numbers for classes or method named, used for flushing caches

Seems a little big, but it's doable. It's a little invasive but unlikely to cause critical failures even if it's a total wash.

- respond_to? call site (based on above)

1.2: (July?)
- greatly improved Rails performance

Sounds like a great feature!

- 1.8.7 compatibility
- Rubinius simplified support

Is this basically Rubinius bytecode support? Hopefully by summer they'll have settled it down a bit. I'm really interested in doing a full port of the VM layer of Rubinius too, so we have all the primitives and can run the kernel files...but the motivation for doing so is more for entertainment than any real need.

- AOT compiler ready enough to actually be usable, including tool support

Tool support is probably the biggest missing bit here, along with some general refinement. I'm hoping for current jrubyc users to help a lot with that.

- VM API implementation

Do you mean solidification of our public APIs?

2.0: (Fall?)
- Full 1.9 compatibility

Doable. Hopefully 1.9 will have settled down by then too.

- Full Rubinius support

...

- Java integration totally rewritten

I think we need to start on parts of this now, and we could probably do it as a parallel library (java2) until we're ready to flip the switch and make it the default. We'd need wrappers until lightweights are in place, but otherwise we could design it to have a MOP that's independent of the actual object wrappers.

- Light weights (not only in JI)?

Big, big job, but the benefits would be pretty huge. We need to start putting the frameworks in place to support this, like method-binding code generation that can work with arbitrary types and a more "independent" MOP instead of the version we have now that's tightly intertwined with Module and Class.

- Charlie

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

   http://xircles.codehaus.org/manage_email


Reply via email to