►
Description
- Change of plans
- y-rb goes multi-platform
A
Hey
and
welcome
to
another
update
of
real-time
editing
of
issue
descriptions
this
week
with
not
so
good
news,
because
there's
a
change
of
plans
and
an
update
on
how
the
ruby
why
ruby
multi-platform
efforts
are
going.
Why
do
I
say
like
change
of
plans?
A
I
was
about
to
ship
the
awareness
feature
to
the
sidebar
like
a
couple
of
weeks
ago
and
till
I
realized,
or
actually
not
realized
until
it
was
pointed
out
to
me
that
there's
a
whole
team
working
on
making
the
sidebar
less
cluttered
and
improved
the
ux
there
and
the
team
was
really
hesitant
to
ship
another
thing
to
the
sidebar
before
their
work
is
done.
A
So
after
a
bit
for
from
back,
we
came
to
the
conclusion:
it's
not
feasible
to
ship
the
awareness
feature
as
it
is
to
the
sidebar
today
and
therefore
we
need
to
find
another
way
to
to
build
it,
because
the
awareness
feature
is
a
prerequisite
for
real-time
collaboration.
A
There
is
another
project
in
another
team
working
on
what
I
call
the
work
item
stream.
The
work
item
workstream.
It's
probably
not
called
like
that,
but
this
is
just
the
way
I
interpret
it
and
they
have
a
very
interesting
ux
principle,
and
I
want
to
elaborate
it
here.
It's
collaborating
in
real
time,
and
this
is
exactly
what
I'm
working
on.
A
A
This
should
make
my
life
much
easier
because
there's
a
it's
more
like
a
green
field,
environment
and
there's
not
so
many
dependencies
and
it's
probably
a
bit
easier
to
just
work
with
this
team
as
they
are
building
this
this
user
interface,
so
things
that
are
going
well
are
the
efforts
of
getting
by
ruby
into
like
getting
multi-platform
releases
for
by
ruby.
Since
I
started
to
work
on,
the
white,
ruby
chamber
was
always
this
thought
about.
A
How
can
we
make
sure
that
it
does
not
cause
any
troubles
to
our
customers
and
one
step-
and
I
talked
about
this
in
the
previous
update-
was
to
migrate
from
rooty
to
magnus
as
our
ruby,
rust,
binding
library,
and
the
next
step
is
to
actually
ship
multi-platform
champs
if
you're
familiar
with
rails,
you
probably
have
seen
or
you're,
probably
aware
of
a
gem
called
nokogiri,
and
this
champ
was
somewhat
in
famous
for
breaking
install
routines
on
on
on
developers
on
developer
machines,
because
the
developers
did
not
have
the
necessary
tooling
available
in
order
to
build
the
negative
extension
and
nokogiri
and
the
team
behind
it
solved
this
in
a
really
nice
way.
A
A
So,
with
your
m1
mac,
with
your
probably
a
bit
older
x60
for
mac
and
on
a
on
a
regular
linux
machine,
you
should
be
able
to
use
by
ruby
with
a
gem
installed
by
ruby
in
the
specific
version,
and
there
should
be
no
compilation
step
like
it
should
just
work
out
of
the
box.
A
few
more
platforms
need
to
follow.
In
particular,
I
have
I
had
issues
to
get
this
running
on
alpine
containers,
which
are
also
quite
popular.
A
That
is-
and
this
is
also
a
shout
out
to
the
community
around
the
ruby
rust
ecosystem-
there's
a
lot
of
help
from
from
those
folks
to
make
this
work,
and
it
turns
out
that
I
might
be
able
to
get
the
the
alpine
linux
to
to
work
nicely
together
with
the
gem
as
well.
But
it's
a
bit
of
an
additional
work
and
yeah.
Then,
eventually,
we
will
have
these
lines
just
working.