First of all congrats to the development team for releasing jruby 1.1! Impressive work!!
I took a brief look at it yesterday and from a user perspective I have a a few initial suggestions for 1.1.x in addition to the areas of Java Integration and performance that you mention (which I think you are right to focus on - ruby 1.9 is not so important yet):
1) Updated documentation: F.x the readme mentions that one only need JDK 1.4 and as I understand you have moved to JDK 1.5+ right ? Another example is that java-support*.txt files which also need updates. Basic info about the new annotation-based binding mechanism and other basic things that new potential jruby developers would need to know would be good. Finally basic info about how to use jruby in a webcontainer as a servlet or with war's would be nice to include right in the distribution.
2)
Official RubyInline aka JavaInline support.
3) Update to rubygems 1.1 which is must faster and which simplified matters and removed a lot of the various gem support files which jruby currently have in the bin directory.
4) Please re-consider the naming of rake, spec, gem and ri tasks in the bin directory. I would like to co-exist with a normal ruby installation so the first thing I normally do after installing jruby is to rename them all to jrake, jspec, jgem, jri etc. so that I f.x. get MRI's gem when I type "gem" and jruby's gem when I type "jgem". The topic has been brought up before and I know there is resistance to this I just never understood why ?
Cheers,
Morten
--- Den søn 6/4/08 skrev Charles Oliver Nutter <[EMAIL PROTECTED]>:
Fra: Charles Oliver Nutter
<[EMAIL PROTECTED]>
Emne: [jruby-dev] Development going forward
Til: dev@jruby.codehaus.org
Dato: søndag 6. april 2008 08.58
Quickly before I get on my flight...let me know what y'all think of this.
- 1.1.x development will proceed on trunk for a while, so 1.1.1 will
include everything that's been fixed on trunk. Barring major rework or
rewrites, I think there's a lot of fixes we can make during 1.1
maintenance cycle before we branch it and it starts to rot (or we have
to constantly merge fixes over).
- We need to consider what version number we might want for
JRuby.next...1.2? 2.0? Tom suggested 3.0 since it wouldn't confuse
people about JRuby 2.0/Ruby 2.0. I think it's open for discussion.
- There are at least two major areas we'll want to start preparing for
in the JRuby.next cycle: Java integration (performance, efficiency, and
perhaps lightweight/Object support throughout
JRuby), and Ruby 1.9
feature support (to whatever extent is appropriate, since Ruby 1.9.x is
still a moving target). As always there will be continuing performance
and compatibility work, but I think these are the two major new areas of
development for the .next cycle.
A few personal goals as well:
- I'd like for us to clearly perform better on 1.9's benchmarks soon. I
think it's possible by putting in similar cheats, but in a way that
doesn't break 1.8 compatibility.
- I want to clean up and unify the entire call path logic so everything
is using the same annotation-based binding mechanism. There's still a
lot of code using callbacks, and block dispatch is still 100%
array-boxed. We could potentially get a big performance boost from both
callback-based methods and blocks if we get then using specific-arity
call paths.
- We need a way to make AOT and JIT-compiled methods support
specific-arity call paths. This could possibly use the annotation
binding logic as well. Also, we need a more efficient call path for
JIT-compiled methods, since they currently just get stuffed inside
DefaultMethod which has its own perf/efficiency concerns.
- I'd like to see us revisit rubinius support once Evan's new VM lands.
I think their opcode list at least has stabilized, and while the list of
primitives has grown extremely long I don't expect it would be hard to
implement them. I'd really like to have a rubinius VM impl on JVM within
the next several months.
Please add to this thread with large areas you think need attention (and
we're always looking for help making things go).
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email |
| Få en billig laptop. Se Kelkoos gode tilbud her! |
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
