On 24 September 2012 14:16, Keith B. [email protected]
wrote:
anything. We should feel humbled by, and grateful for, their generosity,
and hopefully even be motivated to give of ourselves as well.
- We beneficiaries of this are responsible to do our part – in this case,
as was suggested, to file a bug report. This will take a little time,
especially if done right – that is, expressed precisely, clearly, and with
examples, and with a search first to see if the issue has already been
reported. That is one small but helpful thing we can do to assist the
authors. Even better would be to write up the documentation you wish would
have been there, and include a link to it in the bug report.
Nicely put Keith. There was a minor typo in my email. I meant to say
“you
can contribute, if you feel…”. Obviously, it’s not mandatory, and not
everyone has the time, motivation or skills necessary to do so.
On Mon, Sep 24, 2012 at 6:16 AM, Keith B. [email protected]
wrote:
using rvm, it works out of the box.
Not sure I’d go that far
Out of curiousity fiddled with this a little yesterday. On my Mac OS X
(10.7.5) running various JRuby versions included 1.7.0.preview2, I
can start the ng server fine, and starting e.g. irb is quick – but
that’s
as far as it goes. Even something as simple as puts 'foo'
simply
hangs. (def hangs = till my patience runs out and I CTRL-C it).
I no longer have a client using JRuby so I’m not eager to put a lot of
time into figuring it out, but “works out of the box” certainly doesn’t
apply to my experience…
FWIW,
Hassan S. ------------------------ [email protected]
twitter: @hassan
Hassan -
I wish we could get more data points…it seems like you and I are the
only ones in this discussion who have used Nailgun with rvm.
It would be interesting if you could at least revisit your problem
enough to show me a command line that hangs. (You didn’t type it in the
same terminal in which you ran the server, did you?)
And the puts foo didn’t really have backticks, did it? How about if you
try something like this?:
jruby --ng -e “puts(123)”
If it’s at all possible that it wasn’t a Nailgun bug, then we may be
unfairly condemning Nailgun.
To Robin and Mauro, if you have the curiosity and the time (it only
takes a few minutes), it would be interesting to see if you have those
problems with JRuby installed with rvm.
I’ve had a look at the nailgun website now and it makes no pretence to
being a “solid” product –
“In other words, consider this a platform for experiments.”
Its probably my fault but I didn’t get that impression from the original
post here or from the link on it.
I am a very strong believer in JRuby - but I am rather disappointed that
it continues to live in the shadow of MRI Ruby even though it has many
additional strengths and can be so much simpler to use. I will happily
put up with the startup delay.
On 24 September 2012 23:29, Keith B. [email protected]
wrote:
If it’s at all possible that it wasn’t a Nailgun bug, then we may be unfairly
condemning Nailgun.
To Robin and Mauro, if you have the curiosity and the time (it only takes a few
minutes), it would be interesting to see if you have those problems with JRuby
installed with rvm.
I don’t use rvm.
On Mon, Sep 24, 2012 at 2:29 PM, Keith B. [email protected]
wrote:
I wish we could get more data points…it seems like you and I are the only ones
in this discussion who have used Nailgun with rvm.
14:55 ~ $ cd projects/testcases/jruby/pogo
Using /Users/hassan/.rvm/gems/jruby-1.7.0.preview2 with gemset pogo
14:55 ~/projects/testcases/jruby/pogo $ jruby --ng-server
NGServer started on all interfaces, port 2113.
// Open another terminal tab:
14:56 ~ $ cd projects/testcases/jruby/pogo
Using /Users/hassan/.rvm/gems/jruby-1.7.0.preview2 with gemset pogo
14:56 ~/projects/testcases/jruby/pogo $ jruby --ng -S irb
jruby-1.7.0.preview2 :001 > puts “123”
Over 2 minutes later, nothing further has happened…
Let me know if there’s something I can do to expand on that
And for the record:
rvm 1.10.3
java version “1.6.0_35”
Java™ SE Runtime Environment (build 1.6.0_35-b10-428-11M3811)
Java HotSpot™ 64-Bit Server VM (build 20.10-b01-428, mixed mode)
H*
Hassan S. ------------------------ [email protected]
twitter: @hassan
On Wed, Sep 26, 2012 at 12:22 AM, Robin McKay [email protected]
wrote:
Sorry, I don’t use RVM - its not necessary with JRuby though it was
essential back in the day when I used MRI Ruby and had not discovered
the delights of JRuby.
Apologies for the thread semi-hijacking but –
MRI vs. JRuby seems totally orthogonal to using RVM (or not).
Can you explain?
–
Hassan S. ------------------------ [email protected]
twitter: @hassan
Hassan S. wrote in post #1077631:
MRI vs. JRuby seems totally orthogonal to using RVM (or not).
Can you explain?
Very simple.
I have a copy of the downloaded the JRuby .zip (or tar.gz) file. If I
want to start a new JRuby project I just create a new directory for it
and extract the .zip into it. If I have a few versions downloaded I can
extract whichever version I want. I have a short shell script which I
double-click to open a terminal at the project directory with the JRuby
/bin directory in the path. Then everything just works - jruby -v and
gem install xxx for example. Each project is completely self contained.
If I want to run the project on another computer (including on Windows)
I can just copy the whole project directory. The other computer just
needs the JVM.
As far as I know you can’t install MRI Ruby like that - hence the need
for RVM which makes managing MRI Ruby pretty painless.
And you certainly can’t easily copy an MRI Ruby project to another
computer.
Msan M. wrote in post #1077405:
To Robin and Mauro, if you have the curiosity and the time (it only takes a few
minutes), it would be interesting to see if you have those problems with
JRuby
installed with rvm.
Sorry, I don’t use RVM - its not necessary with JRuby though it was
essential back in the day when I used MRI Ruby and had not discovered
the delights of JRuby.
And (to return to a different theme) RVM has great documentation.
Tim U. wrote in post #1077701:
… if you want to waste the disk space.
If you can buy a 500GB drive for £50 then 20Mb of disk space costs less
than a penny. How much of your time should you waste trying to save a
penny?
And you certainly can’t easily copy an MRI Ruby project to another
computer.
You can fudge it if it’s the same architecture especially with bundler
but it’s not the same level of ease as the JVM provides.
My ideal is to have something you can give to Aunt Bertha on a USB stick
which she sticks in her laptop and double-clicks and “it just works”.
You can do that with JRuby (including with a Swing GUI program) but I
have never heard anyone suggest you can do it with MRI Ruby.
[Ok you may have to talk Aunt Bertha through downloading the JVM - but
that’s easy-peasy compared to RVM, MRI Ruby, Bundler etc.]
My ideal is to have something you can give to Aunt Bertha on a USB stick
which she sticks in her laptop and double-clicks and “it just works”.
You can do that with JRuby (including with a Swing GUI program) but I
have never heard anyone suggest you can do it with MRI Ruby.
That’s exactly what I did on windows. It was a self contained
directory which contained the app, ruby, all the gems you needed to
run your app. I think the same thing might be possible in linux if
the architecture is the same.
[Ok you may have to talk Aunt Bertha through downloading the JVM - but
that’s easy-peasy compared to RVM, MRI Ruby, Bundler etc.]
The JVM erases all the architecture problems and makes it a lot easier.
Tim U. wrote in post #1077749:
That’s exactly what I did on windows. It was a self contained
directory which contained the app, ruby, all the gems you needed to
run your app. I think the same thing might be possible in linux if
the architecture is the same.
I presume you were using JRuby.
The JRuby test (or demo) app that I created ran on Windows (both XP and
7) unchanged from the Ubuntu version. The only thing I needed to do was
to create a Windows batch file that was equivalent to the Ubuntu shell
script.
As far as I know you can’t install MRI Ruby like that - hence the need
for RVM which makes managing MRI Ruby pretty painless.
Actually I once did that with ruby on windows. I copied everything
over except the RI, docs etc as well as some libs I didn’t need and it
worked great. I think it was about 10 megs or so but there was a lot
of gems in there too.
I am sure the same thing can be done on linux but I haven’t tried it.
I am pretty sure it’s possible to have a completely isolated ruby and
gem env if you want to waste the disk space.
And you certainly can’t easily copy an MRI Ruby project to another
computer.
You can fudge it if it’s the same architecture especially with bundler
but it’s not the same level of ease as the JVM provides.