►
Description
Discussion for Chapter 10: JRuby: Ruby on the JVM & Chapter 11: Rubinius: Ruby Implemented with Ruby.
A
Do
you
manage
to
make
it
through
both
chapters?
Nope
did
you
I
just.
I
really
pushed
myself
today,
but
yeah
just
barely
like
right
right
before
this.
I
just
finished
the
summary
of
chapter.
Was
this
11
12
whatever
it
is
yeah
every
venus
yeah.
B
So
I
read
about
halfway
through
and
somehow
today
turned
into
like
six
hours
of
meetings
so
yeah
they
were
all
good
and
interesting
meetings,
but
as
I
was
trying
to
catch
up
right
before
this,
I
was
like
nah.
I
just
wasn't
absorbing
anything.
So
I
read
the
summary
and
went
for
a
walk
so.
B
A
A
A
A
I
think,
like
initially,
my
perception
of
jruby
was
like
oh
java.
People
just
wanted
to
be
on
java
so
that
they
could
do
java
things,
and
I
kind
of
understood
that
there
might
have
been
a
slight
performance
increase.
But
I
was
like
I
don't
know
if
it's
gonna,
you
know
like
last
forever,
if
mri
will
catch
up
or
whatever,
like
kind
of
like
with
the
whole
node
versus
what
was
it.
A
I
feel
like
there
was
a
slightly
different
one
for
a
while,
and
then
it
came
back
to
node
anyway,
I
don't
know
or
even
like
in
the
early
days
of
rails.
I
think
there
was
a
a
separate
framework
and
then
it
kind
of
got
merged
back
into
rails.
Three,
I
think-
and
it's
just
like,
oh
so,
somebody's
making
some
improvements
like
it
wasn't
moving
fast
enough
on
the
mainline
mri,
so
they're
going
to
make
their
own
improvements
some
other
way
and
then
it'll
probably
make
its
way
back.
A
But
I
don't
know
this
this
kind
of
made.
It
seem
like
the
jruby.
One
is
really
much
more
efficient,
much
more
performant
and
there
are
actually
some
really
good
selling
points
in
that
you
know
the
jvm
has
been
really
like
scrutinized
and
worked
on
meticulously
for
like
20
years
or
whatever
like
it's.
You
know
I
mean
that's
you
think
about
it
like
java
is
sort
of
the
like
e-commerce
or
whatever,
like
it's
or
the
enterprise
like
it's
like
the
standard
for
that
kind
of
thing,
and
there's
a
reason
for
that.
A
So
yeah
kind
of
made
a
lot
of
sense,
and
so
I
was
like
thinking
like
what
would
it
take
for
git
lab
to
experiment
with
moving
to
jruby?
What
would
that
look
like?
But
I
also
wonder,
like
you
have
the
main,
ruby
right,
mainline,
ruby
and
I
think
it's
all
open
source
or
whatever.
It
could
probably
happen
mostly
simultaneously,
but
I
imagine
you're,
like
ruby.
Three
comes
out
like
how
long
does
it
take
for
jruby,
3.0
or
whatever
to
come
out
after
that?
A
B
Interesting,
I
didn't
even
think
about
that.
The
one
big
thing
I
took
away
from
that
is
the
line
about
making
it
easier
to
do
ruby
on
environments
where
it's
harder
to
set
up
ruby
and
I'm
just
immediately
thinking
of
like
windows
development,
so
it
just
makes
boom.
Yeah,
jruby
and
jvm
makes
it
easier
to
do
the
ruby
development
and
deployment
on
non-unix
and
on
mac
boxes
and
saw
a
bunch
of
that
at
puppet.
B
A
A
That's
a
weird
example
to
choose
yeah,
because
at
first
it
definitely
did
not,
and
then
it
was
only
after
what
was
it
like
over
a
hundred
thousand
close
to
a
million
times
that
it
finally
did,
and
it
seems
like
it
did
it
marginally
yeah,
even
though
that's
like
a
logarithmic
scale
or
whatever
like
it's,
it's.
It
still
feels
like
they're,
very
close
and
they're,
just
like
keeping
in
touch
then
after
that
and
I
was
like
that,
doesn't
seem
worth
it
and
then
they
did
the
other
one
later.
What
was
it
something
with
string?