On Jun 8, 9:44 ¨Âí¬ ÃèáòìåÏìéöåò Îõôôåò ¼ãèáòìåó®îõô®®®Àóõî®ãïí¾
wrote:
> Victor Reyes wrote:
> > Can JRuby coexist with C-Ruby?
> y-nice.
>
> > Currently I am running Ruby 1.8.7 and on some servers I am playing 1.9. What
> > is the equivalent version of JRuby to the latest level of Ruby?

> Almost nobody is asking for 1.9 features, so we've only taken a marginal
> interest. If people want those features, it wouldn't take more than a
> couple dedicated weeks to get them in.

It seems that Ruby-1.8.7 has many features from ruby-1.9.
I think it's important to support these as soon as possible.
It seems obvious that this is going to come without asking for it.
As you, at sun staff are going a great job around jruby: no need
to ask for obvious feature... we know that it will be done some day
(no emergency).

But, about GUI tool kit, one thing that would be realy (realy) great
is to port the standard Tk tool kit to java. this would make it
possible
to migrate native Ruby/Tk application to Jruby.

The big part of this work seems to already be done by Bruce Johnson
with it's swank package (port of tk to java for use with jacl (port
of TCL language to java)
- http://www.onemoonscientific.com/swank/index.html
- https://swank.dev.java.net/
- http://wiki.tcl.tk/2858
If Tk whould be port to java, then Tk would be easier to install for
jruby
than for ruby!)

About other Gui toolkit, it seems that there is some confusion
between
true Gui user interface with complex event handling abilities
(key, mouse, ...) and power canvas drawing features with event binding
(like Tk and other) and just html forms like toolkit with some
graphic
capabilities.

I think it's easiest to switch a programm from one (stuctures or oo)
language to another language, than to move from one Gui system to
another
one in the same language.
So the choice of a Gui toolkit is important!



About startup jruby time:

>mdiam wrote:
>> ...jruby is still a litle slower than ruby at startup time, because
>> of the JVM)
>
>In 1.1.2 we have hopefully improved that...for me, startup time went
>from 1.5s to about .6s, which is a great improvement. Others have
>reported similar boost, maybe not as great. Work continues.

Yes I confirm the great startup improvemnt of the last jruby version,
but I had
to find some inconvenient of jruby ower ruby (but the big one is
about
native library bindings like Tk!)

-- Maurice