►
From YouTube: Node.js Tooling Group Meeting
Description
A
You're,
like
yay,
okay,
we
are
alive
on
YouTube.
This
is
the
nodejs
tooling
group
meeting,
so
Turner
just
gonna,
okay,
you've
made
me
host,
see
you
later.
Thank
you
for
your
help,
mm-hmm.
A
So
the
agenda
for
this
meeting.
The
first
thing
we
I
wanted
to
talk
about
was
kind
of
the
the
current
initiatives,
and
so
the
only
the
formal
initiative
that
we
had
was
this
recursive
operations
thing
by
formal
I
mean
there's
like
a
file
in
the
repo
and
it's
in
the
initiative.
Stirrer-
and
it
says
you
know,
recursive
file,
system
operations,
and
so
this
is
the
only
thing
we've
bothered
to
to
actually
write
down,
and
so
what's
what's
happening.
There.
A
The
problem
is
that
the
my
implementation
is
written
in
C++
and
the
problem
is
that
it
it
runs
in
serial,
and
so
that
means
it'll
delete
every
file
one
by
one
and
when
I
ran
a
benchmark
against
my
my
code
and
the
rim,
raft
module
and
usual
and
I
found
out
that
in
some
cases
it's
even
you
know
a
little
bit
slower
it.
Basically,
it's
just
it's
not
adding
a
whole
lot
in
terms
of
performance
because
the
usual
end
room
refworks'
parallel.
A
A
A
For
two
reasons,
one
is
that
if,
for
some
reason
you
wanted
to
call
like
a
room
der
sink
and
you
wanted
to
do
it
recursively
well,
we
would
need
to
do
some
sort
of
black
magic,
like
exact
sync,
does,
if
you're
familiar
with
that,
where
it's
actually
an
async
operation
but
node
pretends
it
is
blocking,
and
so
with
with
exec
sync.
So
that's
all
well
and
good,
but
it's
not
firing
off
multiple
operations
at
once,
and
so
it's
kind
of
it
there's
really
no.
A
Precedent
for
this
in
node
right
now,
you
know
exact.
Sync,
obviously
does
this
thing
where
it
it
it
pretends
that
it
is
a
sink,
but
as
far
as
just
launching
a
bunch
of
file
system
operations
in
parallel
I,
don't
think
anything's
doing
that
and
for
me
personally,
like
I
kind
of
suck
at
C++
and
once
I
got
this
far
like
I
just
kind
of
hit
a
wall.
You
know
how
do
I
implement
this?
It's
just
kind
of
it
feels
a
bit
beyond
where
you
know
it's
beyond
my
skill
level.
A
At
this
point,
and
so
I'm
not
like
really
I
got
frustrated
and
kind
of
gave
up
more
or
less
saying
you
know,
I
I,
just
don't
know
how
to
how
to
do
this.
It's
going
so
slow,
I,
don't
know
where
to
start
I
have
so
many
questions,
I'm,
probably
not
the
right
person
to
do
this,
and
so
I
think
we
need
to
kind
of
pull
back
from
that
implementation.
A
I'm
not
saying
we
need
to
you
know
unless
there's
somebody
on
this
call
both
either
one
of
you
who,
who
would
you
know
kind
of,
want
to
look
at
that
and
say
you
know
and
see.
If
you
can
do
that
implementation,
you
know
I
would
say
we
should
scrap
it
and
perhaps
look
to
a
a
JavaScript
implementation,
much
like
the
user,
landrum
Raph
and
then
hopefully
get
the
backend
to
a
point
where
we
can
avoid
some
of
the
like
weird
hacks,
that
that
the
user,
Lander
and
Raph
does
to
work
properly
on
Windows.
A
Landrum
ref
has
to
simply
poll
and
see
if
if
the
directories
actually
been
removed,
and
so
just
like
it
fires
off
a
set
interval
and
and
call
stat
or
something
over
and
over
again
until
the
record
just
exists,
and
so
maybe
there's
something
we
can
do
in
the
backend
about
that.
And
so
you
know
that
that
sort
of
thing
is
no
longer
necessary.
A
A
B
Yeah
I've
implemented
reroute
several
times
in
javascript,
it's
actually
ins
of
being
pretty
straightforward
to
do
it
fairly
quickly.
So
I
I'm
I'm
happy
to
take
a
look
at
doing
it
on
the
JavaScript
side.
That
sounds
good
to
me
and
but
before
I
go
ahead
and
meet
myself
one
more
time
my
guy
bedford
has
joined
and
he
should
probably
be
promoted
to
a
panelist
unzoom.
A
Hello
guy
Bedford,
thank
you
for
coming.
I
was
just
I'm,
not
sure
when
you,
when
you
popped
in
I,
was
just
kind
of
explaining
where
rim
ref
was
at
and
basically
I'm
stuck
on
the
C++
implementation,
because
it's
too
slow
because
it's
in
serial
and
it
will
be
too
much
of
a
pain
in
the
butt
to
implement
to
do
in
parallel.
I
quote.
C
The
the
trail
end
of
that
and
it
sounds
to
me
like
yeah
stuff
that
I
don't
have
much
experience
in
personally
I
didn't
realize
how
much
awfulness
was
involved
in
that
C++
sled,
the
jab
that
I
mean
if
anything,
the
jeaious
implementation
can
be
a
starting
point
and
optimization
can
grow
it
but
time.
Surely,
sir
yeah
absolutely
does
that
make
sense,
work
yeah.
A
B
A
Okay,
well,
I
mean
well,
let's
coordinate
on
that.
I
have
some
very
lilies
some
tests,
you
could
probably
reuse,
but
yeah
so
and
I,
don't
know
if
you've
looked
at
the
the
room
raft
modules
implementation
where
they
do
this.
This
sort
of
windows
hacks
I'm
talking
about,
but
that
would
be
really
nice
to
not
have
to
do
that,
and
you
know
we
can
probably
tackle
some
of
those
things
down
the
road,
but
anyway
so
yeah.
That
was
a
kind
of
the
main.
B
A
B
B
B
B
Can't
really
dig
a
few
up
right
now,
but
I'll
be
sure
to
send
it.
You
know,
make
sure
it
gets
attached
to
the
minutes
and
stuff
long
story
short
talking
about
the
feature
it's
in
bash,
it's
in
Python
and
it's
a
system
call
basically
allowing
you
to
replace
the
process
with
a
completely
different
one.
B
A
Would
you
be
interested
in
in
writing?
Up
kind
of
you
know
why
yeah
just
kind
of
writing
something
up
and
sending
a
PR,
and
so
we
can
like
record
that,
as
a
native
you
know
in
the
tooling
repo.
A
D
E
D
Okay,
I
can
maybe
use
a
little
bit
of
help
with
that
at
some
point,
as
well,
just
in
terms
of
upgrading
those
testing
dependencies,
there's
no
clear
path
forward
with
some
of
them,
specifically
the
Mach
FS
dependency
mm-hmm.
So
yeah
I
wouldn't
mind,
maybe
chatting
about
that
after
sort
of
come
up
with
a
plan
to
move
forward
on
that.
A
I'd
be
willing
to
take
a
look
at
that:
okay,
so
yeah.
Let's,
let's
follow
up
on
that
and
I'll
pull
down
the
repo
and
see
what
you're,
what
you're
talking
about
so
Mach
FS
I,
don't
even
know
what
that
is.
I.
D
A
A
Basically
what
I
did
is
I
went
and
I
downloaded
every
single
minor
version
and
tried
to
make
a
list
of
of
these
flags
that
that
were
allowed
and
I
stuffed
them
into
a
big
JSON
file,
but
pre
node
eight,
and
so
we
just
thought
he
node
six.
There
is
no
node
options:
environment
variables,
so
I
just
kind
of
had
to
make
a
guess
at
what
would
be
allowed.
A
E
A
A
Right
so
one
of
the
things
that
I
wanted
to
talk
about
was
was
like
updating
the
readme
and
I.
Think
that's
what
we
like
thing
that
should
go
in
there
is.
This
is
what
we're,
what
we've
done
so
far
and
yeah.
If
you
have
done
any
sort
of
shimming
or
polyfill
type
work,
it
should
go
in
there
and
in
general
I
would
love
to
kind
of
make
that
read
me
more.
A
E
Continue
to
be
doing
some
of
the
test
coverage
stuff
to
just
try
to
get
test
coverage
working
as
a
native
node
feature,
rather
than
like,
like
code
rewrite,
which
is
how
Istanbul
works
right
now,
I'm
down
a
rabbit,
hole
I'm
actually
like
have
a
patch
on
v8
again,
which
always
takes
months
so
I'm,
it's
my
ever.
It's
my
never-ending
work
around
v8
and
node
to
get
test
coverage
working
I'm
optimistic
about
this.
E
It
basically
instruments
the
the
bytecode
as
its
as
it's
being
run
by
v8
and
then
gives
you
test
coverage
at
the
other
side.
So
it
should
work
for
modules
or
es6
code
or
whatever
the
big
issue
right
now.
That's
blocking
me
on
the
node
end
of
things
is
that
regular
e
CJ
s
code
has
a
wrapper
added
to
it,
which
adds
a
ton
of
extra
bytes.
Before
and
after
the
file
that's
being
executed
and
ESM
code
does
not
have
a
wrapper
around
it.
E
So
there's
just
byte
offset
differences
off
by
off
by
n
issues,
depending
on
whether
you're
a
module
or
not
a
module,
and
also
depending
on
whether
you're,
using
the
new
module
loader
system
to
load,
CGS
modules
or
the
old
module
loader
system
or,
if
you're
like,
if
you're,
using
a
shim
like
like,
like
the
ESM
shim.
That
provides
the
shimming
for
modules
that
John
David
Dalton
did.
That
has
a
different
header
size
than
the
CGS
header
size,
which
is
different
than
the
ESM
header
size.
E
C
E
I,
don't
think
that's
a
bad
idea.
I
mean
I'm
kind
of
hopeful
that,
like
there's
a
couple
poor
request.open
on
node.js
that
remove
the
wrapper,
because
the
wrapper
is
actually
an
additional
API
call.
Now
in
v8,
you
can
say,
run
this
code
and
this
code
should
have
this
wrapper
around
it
and
it
slipped
the
note
into
two
parts.
E
So
if
we
move
node
towards
doing
that,
then
everything
should
be
a
zero
offset
and
then
everything
gets
easier,
but
that
yeah
I
can
share
some
links
guy
after
I'll
share
them
in
a
second,
but
that
doesn't
solve
the
problem
of
John
David
Dalton's
shim,
because
that
key
would
need
to
switch
his
shim
to
using
this
new
v8,
API
and
I'm,
not
sure
what
that
would
look
like.
So.
But
if.
A
C
As
we
moved
her
world,
we
were
thinking
of,
like
principle
of
least
responsibility
from
a
security
perspective
in
modules.
If
every
module
modules
naturally
have
an
encapsulated
environment
because
they
only
have
access
to
the
bindings
that
they
import,
we
don't
need
Global's
as
a
mechanism
to
share
API
capabilities.
So
the
idea
is
that
if
you
can
lock
down
a
module
and
then
we
get
things
like
frozen,
realms
and
future
etc
that
it
could
be
quite
a
useful.
C
You
know,
you
know
you.
It
starts
to
become
a
security,
secure
environment,
but
process
and
buffer
expose.
A
lot
of
very
low-level
capabilities
process
has
higher
resolution
timers.
It
also
has
access
to
things
like
all
the
bindings
and
all
the
native
bindings,
so
I
was
hoping
to
aim
for
a
path
to
see
if
we
can
deprecated
these
by
basically
making
the
global
dub
process
and
level
buffer,
getters
a
warning
and
then
adding
them
into
the
wrapper
for
the
CJS
wrappers.
C
So
this
is
why
I
just
mentioned
it,
because
you
brought
up
the
rapid
changes,
so
have
them
come
through
in
the
wrapper,
they're
always
going
to
be
in
CGS,
and
then,
if
you
access
them
on
global,
the
process
or
global
dub
buffer
you'd
get
a
warning
and
then
eventually
a
deprecation
path
and
I.
Don't
know
if
that
is
that
all
associated
with
this
group
or
not,
but
every
just
to
mention
it
to
see.
If
that's
something
that
anyone
has
any
thoughts
on
as
well.
Well,
we
had
that
moment.
A
C
E
My
main
thing,
like
my
main
thing
with
modules
right
now,
is
I:
don't
I'm,
not
I'm,
don't
do
much.
Front-End
coatings
and
I
don't
have
much
of
a
use
for
modules,
but
I
really
want
test
coverage
to
work
properly
for
them,
so
that
this
weird
weird
edge
case
use
of
them,
where
I'm
just
trying
to
make
sure
that
everything
I
write
works
properly.
What's
that
new
world
I.
A
Cool
all
right,
so
a
thing
was
and
I
wrote
this
down
and
I
don't
know
if
anybody
cares
about
this,
but
I'm
kind
of
a
me
of
the
opinion
that
we
don't
really
need
anything
like
this
right
now,
but
I'm
wondering
if
people
want
a
more
formal
like
decision
making
process
or
what
have
you
I
feel
like
it's
a
little
bit
too
early
for
that.
But
you
may
disagree.
A
A
A
I,
don't
know
as
far
as
decisions
that
this
group
is
actually
making
I
think
that's
kind
of
the
this
decisions
insofar
as
yes,
we
want
to
work
on
thing
X
and
you
know
any
decision
there
has
has
really
no
bearing
on
whether
any
individual
member
of
this
group
goes
off
and
does
it
anyway.
You
know
what
I
mean,
so,
even
if
it's
not
something
that
the
group
would
want
to
get
behind,
I
mean
it
certainly
doesn't
you
know,
maybe
it's
for
reasons
that
you
know
it
doesn't
necessarily.
Maybe
we'd
actually
disagree
with
it
entirely.
A
I
don't
know,
but
it's
just
kind
of
I
feel
like
the
decisions
that
we
have
to
make
are
more
of
the
okay.
What
what
should
we?
What
should
we
put
our
name
on
variety
at
the
moment
in
the
future?
I
would
love
to
and
and
we're
already
seeing
I'm
already
seeing
some
of
this
where
people
are
see
seeing
nodejs
tooling
on
some
of
the
issues
and
that's
great
I
mean
I'm,
not
sure
what
to
do
with
that
necessarily
other
than
off.
E
The
idea
that
we'd
have
bench
really
present
a
bit
of
a
roadmap
for
some
of
the
stuff
we
have
on
our
mind,
which
I
unfortunately
have
been
shipped
around
the
u.s.
for
the
last
couple
months
and
have
not
done
like
I,
said
I
would
so
I
apologize,
but
I
think
it
could
be
good
to
say,
like
you
know,
we
eventually
intend
to
finish
up
rim
raff
and
we
have
these
shims.
E
We
were
working
on
and
we
and
we're
interested
in
moving
into
this
area
to
just
just
to
give
people
an
idea
of
the
scope
of
work
were
thinking
about
doing,
and
it
just
kind
of
keeps
us
I,
don't
know,
I,
think
a
few
more
wins
for
the
working
group
would
be
good
because
I
think
we'll
kind
of
be
just
psychologically
good
for
us
and
kind
of
demonstrates
to
other
folks
on
the
node
project.
What
our
area
of
interest
is.
A
C
Yeah
I
mean
I.
The
only
process
I
had
experience
with
is
the
the
modules
group
at
the
moment
and
and
miles
is
you
know
very
good
at
running
that
and
has
has
a
lot
of
good
ideas
with
that
stuff,
so
I
mean
as
I
just
posted
there
I
believe
the
list
of
members
that
is
forms
the
quorum
is
maintained
by
an
automated
tool.
C
So
it
kind
of
makes
sure
that
it's
I
think
I,
don't
know
how
the
exact
rules
play
out,
but
it's
it
could
be
worth
chatting
to
miles
to
point
out
about
that,
but
it's
updated
with
a
PR
periodically
and
then
those
who've
attended.
The
meetings
based
on
their
actual
attendance
ends
up
forming
the
the
ongoing
group
and
the
quorum
available.
So
it's
it's
all
worked
out
pretty
well
and
then
every
decision,
every
PR
decision
to
the
main
repo
has
to
get
a
vote
from
quorum.
C
So
the
first
thing
we'll
do
in
the
meetings
is
go
through
the
the
PRS
and
if
we
have
quorum,
get
them
merged
in
we
don't
a
quorum,
then
we'll
wait
until
we
do
have
quorum
to
have
to
sort
them
outs.
But
if
we
get
enough
approvals
based
on
quorum
than
we
can
can
get
those
Piazza
and
outside
of
the
main
zoo
meetings
as
well
and-
and
that
seems
to
be
working
for
us
and
the
memberships
changed
over
time-
it's
evolved
over
time,
but
the
the
people
in
quorum
has
has
evolved
with
that.
A
It
sounds
reasonable
to
me,
you
know
no,
no
reason
to
do
something
from
scratch.
That.
E
Cool
yeah,
no,
that
makes
sense
to
me
too,
and
it
fits
within
the
existing
project,
which
is
that
you
know
you
have
what
sign-up
for
two
collaborators.
If
you
want
to
land
something.
So
we
already
the
folks
who
are
involved
in
the
project
to
our
collaborators
already
have
that
option
available
to
them.
E
Just
wondering
I
I,
don't
hate
that
idea,
I'm
just
wondering
like
what.
How
would
it
be
presented
it
would
if
you'd
like
to
say
that
you
were
the
champion
for
RIM
raft
Chris
like
would
it
would
we
still
have
some
sort
of
unified
document,
it's
just
that
your
name's
attached
to
that
which
you're
pushing
for
or
might
wonder
what
that
process
looks
like.
E
E
That
makes
it
yeah
that
makes
sense
to
me
too
I.
Think
there's
like
you
say
we
don't
want
a
ton
of
product,
like
you
know,
minimal
process
like
for
one
thing,
my
one
concern
I
have
is,
if
we
like,
if
we
get
too
hung
up
on
an
RFC,
we
might
get
sick
of
arguing
for
a
feed
sugar.
If
there's
contention
before
we
even
get
to
the
point
of
doing
any
work
on
the
features,
so
sometimes
I
think
there's
a
benefit
to
pull
request
driven
process.
E
What
I
also
do
think
maybe
like
it
would
have
been
smart
to
do
an
RFC
for
McGirt
before
we
did
mid
dirt,
so
I
don't
know.
Maybe
maybe
when
do
we
feel
like
as
a
group?
Do
we
want
to
reach
consensus
before
works
done,
or
do
we
want
to
move
towards
consensus
after
a
little
bit
of
reference?
Work
has
already
been
done
on
issues.
C
Maybe
have
two
phases,
investigation
and
PR,
or
you
know
like
if
we're
gonna
update
the
read,
meets
up
to
list
the
actual
proposals
and
then
kind
of
have
maybe
three
headings
and
say
completed
proposals,
experimental
proposals
or
under
consideration,
PRS
or
current
PRS
was
something
like
that.
I've.
A
Yeah
I
think
we
need
to
I
think
we're.
Are
we
looking
42
I?
Don't
know
why
I
saw
a
later
time,
but
okay,
so
we
have
about
20
minutes
or
so,
but
yeah
I
think
we
should
definitely
okay,
so
I
wonder
if
guy
or
band
would
be
interested
in
kind
of
writing
this
down
in
in
terms
of
maybe
that
needs
to
just
be
a
PR
to
the
readme.
For
now
this
is
how
we
work
yeah.
E
Does
that
mean?
So
if
I
was
to
summarize
what
I
say
like
we're
going
to
have
a
proposal
phase,
which
is
just
like
really
anyone
can
do
and
as
a
group,
we
decide
whether
or
not
we're
actually
jazzed
about
a
proposal
Lanson,
probably
in
our
FCS
folder
and
then
the
next
phase
of
work
is
that
there's
a
pull
request
that
were
just
got
that
we're
actually
working
around
that
makes
sense.
I
think
we
can
start
simple
of
just
a
proposal
and
then
a
pull
request
that
falls
on
to
it.
C
E
I
mean
I
I
feel
like
we
just
throw
a
folder
in
the
tooling,
been
the
tooling
repo
and
and
then
like,
like
a
anonymous
observer,
suggested
like
we
can
even
probably
crib
some
of
the
format
from
was
it
tc39
TCS
or
what's
the
W?
What's
the
working
group,
the
WS
G's,
something
or
other
I
always
forget
the
acronym,
but
that
a
bunch
of
like
that,
the
URL
RFC
is,
is
being
worked
on
around
I
need
to
look
it
up.
C
C
You
know
it
passed
out.
Relative
is
a
very
common
use
case
in
node
modules.
We
are
using
URLs
to
refer
to
or
modules
URLs
file
URLs
so
and
it's
something
that
I've
also
hits
many
times
in
in
writing
servers
is
you
often
want
to
do
relative
URL
stuff
and
especially
since
the
effectively
isn't
the
current
URL
API
deprecated?
You
know
for
the
for
the
what
work
API
instead,
so
is
there
a
euro
relative
that
is
available
at
the
moment?
E
C
Will
do
basically
that
gives
you
pasta
result,
but
it
does
not
give
you
pasta
relative.
It
gives
you
pop
that
resolving
path
of
join
because
you
can
do
new
URL
and
then
you
can
create
a
euro
relative
to
another
URL
and
it
will
do
relative
resolution.
But
if
you
want
to
get
the
relative
URL
from
one
to
another
with
with
the
right
amount
of
backtracking
or
whatever,
there
isn't
a
nice
API
to
do
that,
and
other
thing
is,
if
you
are
using
pasta
relative
to
do
that,
then
you've
got
to
swap
out
your
room.
C
You'll
pass
separators
forward,
slashes
and
if
you
don't
have
a
dog
at
the
beginning,
you've
got
to
add
your
your
initial
dog
forward.
Slash,
which
is
I,
mean
just
work
that
feels
like
he
gets
repeated
and
the
sort
of
thing
that
from
a
tooling
perspective,
seems
like
something
that
can
be
refined,
so
I
mean
I'd,
be
interested
in
working
on
something
like
that.
Yeah,
yes,.
E
E
What
I
find
kind
of
interesting
with
that
is
that
there's
a
real
chance
for
us
to
like
I
mean
one
of
the
things
I
think
is
valuable
about
the
tooling
initiative.
Is
that
but
sorts
of
challenges
that
people
working
on
command-line
tools
and
node.js
run
into
are
different
than
the
types
of
challenges
in
some
cases
that
people
run
into
doing
module
development.
So
there's
room
like
in
this
case
I
would
say:
there's
almost
room
for
us
to
even
start
the
conversation
on
the
white.
E
Wake
repo
and
say:
listen
this
the
specifications
most
of
what
we
need
for
a
lot
of
our
use
cases
on
the
on
the
node
project,
but
there's
one.
This
once
was
a
feature
that
we
feel
is
lacking.
Would
you
be
open
to
you
know,
in
addition
to
the
specification
that,
because
I
think
one
of
the
goals
with
with
the
URL
rewrite
was
to
be
having
standardized
on
specification?
E
C
E
E
C
C
E
Makes
sense
to
me
yeah
if
it
becomes
an
interesting
question
to
like
like
is
this
actually
is
a
fight?
It's
a
file
fragment
actually
a
URL,
or
are
we
just
using
the
URL
parser
on
file?
Fragments
I
mean
there's
a
file
colon
forward,
slash
forward,
slash
specification,
so
I,
don't
know
this
is
an
interesting
question
or
are
we
hung
up
on
standards
and
node.js
is
not
a
web
browser,
so
it
should
have
api's
that
aren't.
C
Going
forward
with
sense
encoding
in
the
URLs,
so
you
know
in
the
current
replacement
for
double
underscore
file.
Name
in
modules
is
import
dominated
or
URL.
We
may
well
get
a
import,
omitted
file,
name
or
something
like
that,
but
for
now
it's
important
minute
or
URL,
which
we'd
have
percent-encoding
all
of
the
URL
functionality.
So
as
soon
as
you
want
to
move
that
into
the
file
system.
In
word,
that's
why
we
have
these
new
functions
like
URL
to
file
posts
and
things
like
that.
A
E
D
E
E
A
D
C
C
E
Couple
random
topics:
a
conversation
I
had
we
had
another
rim
raft,
pull
request
open
that
I'm
gonna
guess
stalled,
because
it's
such
a
contentious,
I
didn't
actually
look,
but
it's
such
a
it's
it's
a
hard
feature
to
build
and
I
bet
it
created
a
lot
of
controversy.
Do
we
want
to
go?
Did
he
keep
an
eye
on
that
other
graph?
That
was
open
Christy?
Should
we
go
champion
full
request
or.
A
That
PR
would
still
have
the
same
issues
that
that
my
implementation
does,
which
is
that
it
it
works
in
serial,
and
so
you
know
that
implementation
will
be
slow,
looks
like
the
the
tests
were
a
little
more
complete,
and
so
those
might
be
worth
like
pulling
in,
but
yeah
it
didn't.
Look
like.
There
was
a
lot
of
excitement
around
or
on
merging
that
specific
PR,
so
yeah.
It's.
A
E
Bullish
on
us
trying
to
figure
out
why
the
heck
rym
rafts
are
why
the
heck
libuv
does
not
do
a
good
job
of
I'm
linking
on
Windows
like
if
we
could
address
that
issue,
even
if
it's
only
on
newer
versions
of
Windows,
and
we
accept
that
that's
a
fact.
I
don't
find
what
it
looks
like.
Maybe
there's
some.
E
Maybe
we
do
a
JavaScript
userland
implementation
in
JavaScript
of
rim
ref,
but
can
solve
a
couple
of
the
things
that
makes
it
really
slow,
which
are
like
the
fact
that
it's
waiting
on
asleep
on
Windows
until
I
call
it
until
it
can
confirm
that
the
file
has
been
unlinked.
There's
just
silly
little
things
like
that.
E
E
Sorry,
it's
a
bunch,
it's
called
hackle
annoy
and
it's
basically
it
happens
at
the
Champaign
Urbana
campus
and
it's
a
bunch
of
college
students
and
the
weekend
programming
with
open-source
maintainer
z'
in
a
hackathon
kind
of
environment,
but
with
mentorship
happening
with
the
goal
being
to
contribute
to
kind
of
marquee
open-source
projects
like
node
and
there's
a
Python
representation.
A
rust
was
there
last
year,
I'm
gonna
be
at
this
again
in
February
I
think
it
would
be
maybe
neat
to
do
a
task
from
the
tooling
working
group
as
one
of
the
things
we
do
like.
E
E
I
could
probably
get
an
invite
to
someone
else
in
the
working
group
as
well
with
a
stipend
for
travel.
Potentially
so
I
think
it
could
be
cool
might
be
a
good
way
to
get
some
momentum
and
it's
coming
up
pretty
soon.
So
I
don't
know
how
people
feel
about
that.
But
maybe
we
say
rim
Raph
could
be
a
really
fun
thing
to
have
come
out
of
that
hackathon.
So
if
rim
Raph
is
kind
of
still
sitting
on
the
sidelines
by
then
maybe
we
could
make
that
our
project,
the.
A
A
Commandlineoptions
an
option
parsing
and
coming
up
with
a
better
story
for
that,
but
you
know
we
don't
necessarily
need
to
throw
out
all
these
ideas
here.
I
mean
you
just
go
into
the
into
the
repo
and
make
an
issue
and
say
you
know,
discuss
amongst
yourselves,
but
I'm
definitely
interested
in
that
one.