M C wrote:
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.
Documentation is certainly a weak point right now, and we'd love to get
help with patches and wiki updates. If we've got docs that are just
perenially out of date, perhaps they should just point at the wiki.
Patches are welcome for anything here. I know we need to improve this.
2) Official RubyInline aka JavaInline support.
I'm not sure what direction to go with this. The java_inline I have
right now works pretty well, but I don't have any tests for it other
than simple scripts. I'd feel better about it being part of RubyInline
proper, but I'm not sure if Ryan Davis is interested in including it
since for his releases he'd have to test against JRuby (I don't think
he's a fan). I could release a separate gem you can install that works
with RubyInline...perhaps that's the best way. At any rate I'd rather
not include this in core, since it's easy enough to get, and we ship
enough stuff already.
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.
I believe that's been done on trunk already by Vladimir.
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 ?
Others have commented, but largely it's the fact that we'd have to patch
RubyGems to add a "j" to every script installed in that dir, and that
seems *really* ugly to me. jruby -S <bin script> works fine,
manipulating path works fine, adding your own shell aliases and
filesystem links works fine.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
