►
From YouTube: Node.js Tooling Group Meeting
Description
B
A
We
have
a
few
issues
that
were
we
have
a
few
topics:
where's
RIM,
wrap,
sitting
usual
and
shims,
which
I
think
we
didn't
make
a
huge
amount
of
progress
with
future
meeting
cadence
and
someone
from
tc39
was
interacting
with
us
trying
to
see
if
we
could
have
more
collaboration.
What's
their
project,
I
I
was
asking:
are
there
any
new
agenda
items
that
folks
would
like
to
bring
up
her
on
the
call
I.
A
B
Essentially
yeah,
so
I
I
had
a
a
C++
implementation
that
basically
just
went
and
it
removed
files
and
directories,
but
it
did
it
you
know
in
serial,
so
it
would
just
do
one
at
a
time.
It
wouldn't
say
you
know
spawn
for
threads
or
whatever
to
go,
delete
four
at
a
time.
It
would
only
do
one
at
a
time
and
performance
was
I,
would
say
similar
to
user
Landrum,
wrath
and
and
and
that's
in
some
cases
worse.
So
it's
just
if
that's
not
going
to
cut
it.
B
So
the
the
sepal,
simple
implementation
to
to
spawn
multiple
threads
and
do
all
this
stuff
is
node
number
one
there's
nothing
quite
like
that.
That
I
saw
anyway
in
in
node
core
and
the
other
concern
is.
If
you
do
a
synchronous,
room
Raph,
you
know
you're,
you
may
be
in
the
same
boat
where
you
have
to
as
what
was
it
exact
sync,
where
you
have
to
basically
fake
being
synchronous
and
that
just
like
adds
another
layer
of
being
a
headache
and
so
I
feel
like
rim
Raph.
B
A
C
B
C
A
C
D
C
A
C
So
we
have
well
at
least
a
bill.
Working
group
I
think
some
code
I'm
not
sure,
but
they
think
some
code
in
Libya
V
there.
This
disgusting
trick,
where
we
first
try
to
move
the
directory
somewhere
else
and
then
delete
it.
So
at
least
we
can
keep
something
good,
but
that
can
be.
We
can
discuss
that
further
like
further
down
the
road
I.
B
Mean
our
MRF
I
mean
that's,
not
an
atomic
operation
anyway,
yeah
right
so
I
mean
what
can
you
really
expect
out
of
it?
You
know
if
you're
gonna
use
our
MRF
and
it
breaks
halfway
through
well
I
mean
you
should
probably
know
what
you're
getting
into
so
there's
no
way.
We
can
guarantee
that
to
be,
like
you
know,
a
single
atomic
operation,
but.
C
I
think
we
need
to
be
very
clear
on
that,
because
you
know
no
tries
to
give
some
guarantees
on
most
of
its
api's,
and
this
is
like
this
is
a
compound
operation
which
is
kind
of
unique.
So
you
know
at
least
the
standard
gives
the
the
output
of
removal
gives
kind
of
an
indication
how
far
along
did
it
God
did
it
get?
It
gives
like
a
number
of
handles
I
think
it
was
able
to
delete.
So
like
that's
like
a
kind
of
a
design
perspective.
We
need
to
keep
in
mind.
A
C
A
B
Yeah,
do
you
have
a
like
an
issue
for
that.
C
B
C
So
which
so
a
a
one
question
to
the
group
is
that
and
I'm
referencing
ethics
watch
in
the
sense
that
is
it.
B
C
B
A
B
Is
this
a
good
cadence
or
a
good
sagen
to
the
next
userland
shims
topic?
Yes,.
A
Definitely
so
I
reached
out
to
James
Halliday
about
with
Nick
mcdr,
and
it
was
really
not
to
just
switch
to
a
native
implementation
of
it,
and
it
made
me
think
we,
you
know
it's
gonna
be
a
mixed
bag.
I
know
Isaac
would
love
to
retire
in
Wrath,
but
probably
other
people
who
have
James
holidays
point
of
view
and
I
mean
it's
really
up
to
them
like
I,
know,
Sandra's
or
who
switched
to
the
native
implementation,
and
his
is
Viktor
competitor
is
an
example.
Other
competitors
very
worried,
but
alternative,
which.
A
A
Yeah
and
I
saw
someone
updating
that
to
use
the
art,
no
Jess
native
implementation
else,
I
work
with
I,
don't
know
if
it's
landed
yet,
but
I
think
it
is
making
the
search
over.
Oh,
no,
it
has
landed,
that's
cool
yeah.
So
all
this
to
say
I
when
I
was
can
advocate
as
I
love
for
us
to
eventually
start
using
I
like
nodejs,
sanctioned
libraries
to
read
the
shims,
maybe
like
they're
publishing
to
at
nodejs
on
NPM
or
something
with
Jim
the
work
on
old
platform.
How
people
feel
like
that
I
think.
C
A
C
A
I
guess
we
can't
try
to
call
using
that
namespace.
Yet
last
I
saw
that
thread.
It
was
like.
People
were
moving
towards
:.
Instead
of
a
forward,
slash,
I,
thought
and
like
it
was
just
some
completely
different
syntax
than
mcat
modules,
which
would
means
our
naming
collision
concerned
with.
If
we
were
publishing
some
stuff
and
the
toiling
working
group.
So
it.
B
A
Yeah-
and
this
is
where
people
kind
of
collided,
because
I
think
it's
one
option-
is
we're
actually
back
porting,
all
this
stuff
and
and
I
feel
like
it,
just
pretty
terrifying
to
backport
some
of
the
bigger
changes
like
I'm
gonna,
back
forward
a
version
of
libuv
into
v8
that
has
a
completely
different
RM
dash,
RF
syntax.
You
know
like
that
actually
and
that
actually
be
back
ported
all
the
way
back
to
node
6
right,
I,
don't
know
if
it
can
at
what
point?
A
B
We
can
check
that
issue
again,
but
it
didn't
sound
to
me
like
there
was
much
clarity
on
what
we
should
do
and
I
think
you
know.
If
we're
gonna
publish
it
are
our
shims
and
and
we
can
certainly
keep
them
in
the
org
I.
Imagine
or
maybe
a
or
maybe
it's,
maybe
that's,
not
even
the
node
GS
or
gone
on
github.
Maybe
it's
a
different
org,
but
that's
nothing
is
gonna.
Stop
us
from
doing
that.
A
B
B
B
A
A
A
C
Said
so
on
that
note
we
had
I'd
not
sure
it's
on
the
agenda.
No,
but
we
had
that
conversation
in
Twitter
a
month
ago
about
chalky
Darin
death
with
swatch
and
that
is
advanced,
etc
about
cannibalizing
parts
of
that
of
that,
like
ecosystem
into
poor
and
poorly
feeling,
FS
watch
to
be
better
than
it
is
right.
Now,
that's
like
open
a
new
issue
in
the
repo,
so
we
can
focus
transmission,
but
the
segue
is
directly
I.
A
Mean
that
brings
up
an
interesting
point,
we've
kind
of
so
far
like
we've
only
done
a
few
things
so
far
as
the
tooling
group,
but
we've
so
far,
shied
away
from
injuries
in
significant
chunks
of
JavaScript
logic
to
shim,
behavior
and
I.
Think
we're
eventually
gonna
want
to
write
like
like.
Should
we
be
shying
away
from
pulling
in
something
like
like
choke
it
or
like
you
say
you.
C
Know
not
not
it's.
We
need
to
find
out
I
think
we
need
to
find
like
a
well
a
balance
of
what
you'd
be
in
core
I.
Think
the
main
targets
for
as
I
see
it
for
for
liberty
and
the
no
does
to
give
a
similar
feature
set
across
platforms.
So.
E
A
It
like
why
even
have
to
watch
API
at
that
point,
it's
kind
of
like
I'd
like
to
and
it's
a
I
feel
it's
a
foot
gun
for
the
community
right,
because,
if
I
don't
know
the
shortcomings,
I'm
gonna
go
see,
ok,
watch,
that's
cool,
let's
use
this
API
method
and
then
one
of
the
first
core
requests.
That's
gonna
coming
into
my
library,
is
switching
it
for
a
username
module.
C
It's
a
it's
a
strange
situation:
I'm
not
well
versed
in
what's
happening
because
I
don't
work
a
Mac
and
and
it's
a
fairly
client
oriented,
Somnath
I,
think
it's
an
excellent
case
for
for
tools
because,
like
a
lot
of
tools,
watch
file
systems
but
like
that
there's
also,
like
you
said,
I
think
this
whole
issue
brings
up
like
fad,
because
people,
because
also
we
don't-
we
haven't
mapped
like
the
gaps.
There
isn't
like
a
an
exact
like.
C
A
A
E
C
E
Soothing
experience
from
that
as
well
just
coming
from
the
perspective
of
rural
up
I
know:
we've
been
speaking
about
it
in
the
role
of
project
quite
a
bit,
and
it's
you
know
something
that
rich
Harris
does
go
on
about
as
well,
that
this
watch
API
is
very
frustrating
to
work
with
and
in
rural
up
by
default.
We
use
the
the
standard
node
watch
API,
but
the
problem
that
happens
with
that
is
I.
E
Think
if
I
remember
correctly
is
that
we're
creating
a
handle
or
a
watcher
for
each
Shepard
file
because
we're
watching
a
lot
of
files,
whereas
other
watches
consider
batch
that
load.
So
as
the
you're
watching
everything
in
node
modules,
for
example,
then
it
suddenly
just
slows
down
ridiculous
and
we
get
these
terrible
times
and
then
you
have
to
switch
to
Chucky.
Does
there's
kind
of
this
experience
where
it
works?
Initially,
okay
and
then
it
just
breaks
down
completely
and
and
slows
down
your
build.
E
If
I'm,
remembering
correctly
I
mean
I,
haven't
really
researched
this
one
I
didn't
know
it
was
gonna
come
up
today,
but
it
is
it's
a
big
one.
From
a
tooling
perspective,
I
mean
in
all
these
tools.
We
complain
about
watches
and
the
saddest
thing
about
it
is
like
the
people
who
worked
on
tools
like
char
guitar
have
traced
those
bugs,
but
those
bugs
haven't
necessarily
been
all
followed
up.
E
So
there's
kind
of
in
the
space
in
the
middle,
where
these
things
have
been
dropped
and
we
don't
necessarily
know
exactly
what
those
those
issues
are
to
follow.
But
you
know
if
there
was
a
conceded
efforts
towards
patching
that
gap,
that
that
would
be
huge
and
I
know
that
a
lot
of
tooling
authors
would
really
really
really
value
that
you
know
solving
the
problems.
E
A
Think
that's
really
excited
about
features
like
rim
wrath,
but
it
almost
feels
like
Cho
Couture
is
almost
a
clearer,
immediate
win
for
the
type
of
thing
we
should
be
doing
as
an
initiative,
which
is
help.
This
even
help
people
in
the
community
land
their
the
work,
they've
done
in
user
Lane
modules
upstream
into
node,
because
sometimes
it's
just
that
the
barrier
event.
No,
we
made
them
I
not
be
able
to
patch
these
things.
Like
you
say,
okay,
so
we
can
help
facilitate
that
I.
E
Even
even
just
from
a
signalling
perspective,
because
I
think
a
lot
of
people
have
a
lot
of
apathy
around
node
watches
and
to
just
start
to
correct
that
promise.
I
can
respect
Wednesday.
Well,
let's
take
a
bug
in
and
fix
one
small
bug
to
do
with
it
or
something
like
that,
and
just
show
that
there's
some
someone
picking
those
up
in
the
BB
or
wherever
they
live.
B
Somebody
read
my
mind:
okay,
there's
a
Twitter
link
yeah.
If
we're
talking
to
things
that
are
that
are
like
that
are
more,
maybe
pressing
or
more
worthwhile
than
rim
Raph
I.
You
know
if,
if
FS
watches
is
one
of
those
things,
what
about
and
I
would
say,
this
is
probably
even
more
of
a
big
deal.
This
is
something
like
cross
bond
like
looking
at
that
and
saying:
okay,
why
do
we
need
cross
spawn?
Why
doesn't
spawn
just
work
on
Windows
like
like
it
should?
And
you
know
what
would
it
take
to
pull
that
into
core.
F
It
would
be
great
to
get
someone
from
Microsoft
involved.
I
know
what
our
first
meeting
when
we
chatted
at
Note
interactive.
There
was
a
guy
from
Microsoft
there
and
I
think
a
lot
of
these.
These
compatibility
issues
are
on
Windows,
so
we,
it
would
be
great
if
we
could
get
him
back
or
someone
because
it
seemed
like
they
were
interested
in
in
solving
some
of
these
issues.
C
C
A
Maybe
the
medic
question
is
like
sounds
of
we
have
like.
We
have
a
few
things
that
are
pet
things
we
continue
to,
but
I
mean
like
a
monthly
meeting,
we're
not
gonna
get
code
down
into
monthly
meeting
I
wonder
what
are
some
good
actually
is.
We
could
take
away
to
have
some
initial
wins
on
some
of
these
username
modules,
we'd
like
to
start
to
retire
here
and.
C
B
A
C
C
D
A
Was
going
to
say
maybe
a
good
starting
point
is
like
we
have
the
node,
tooling
repo,
that's
just
for
running
meetings
and
notes.
Maybe
we
could
open
issues
on
there
that
are
like
here's,
an
idea.
We
think
that
would
be
really
good
to
move
choking
or
into
Nova
Corps.
Here's
some
resupply,
here's
the
Twitter
conversation
series.
A
What
we
think
it
would
look
like
if
we
have
any
other
comments,
but
then
it's
up
to
if
anyone
in
the
community
wants
to
pick
it
up,
we
can
help
like
you
say,
champion
it
and
we
can
provide
that
just
a
joke
and
then
it
provides
a
nice
place
for
someone
who
wants
to
contribute
to
the
node
project
to
go
well,
there
are
some
actual
meaty
things.
I
could
be
doing
that
I
know.
I'll,
have
the
support
of
a
few
contributors
to
help.
I
am
great.
How.
C
Do
we
get
somebody
it's
somebody
I'm,
maybe
I'll
do
something
like
if
somebody
wants
to
do
it,
there's
an
individual
and
get
the
team's
support.
I
think
that
we'll
both
come
across
great
and
the
higher
chances
of
success.
Then,
if
we
do
something
you
know
who
decided
as
a
group
to
do
it,
and
then
it
falls
between
chairs
how.
F
C
A
Think
there
are
ways
so
like
I
mean
a
bunch
of
us
are
Twitter
like
at
least
kind
of
like
evangelize
it
as
things
people
could
be
working
on
and
there's
the
mentorship
working
group
honestly
and
having
a
set
of
like
pretty
meaty
things
for
a
mentee
to
work
on.
It's
actually
great,
because
because
you're
kind
of
reaching
like
what
am
I
gonna
work
with
this
person
on
for
the
next
three
months,
so
I
mean
we
could
I.
A
F
F
B
F
B
You
know
if
we
can
I
don't
know.
If,
if
we
can
find
somebody
to
do
this
stuff,
then
then
great
you
know,
but
I
don't
feel
like
we
should
I,
don't
quite
understand
what
you
were
saying
about.
We
shouldn't
be
coding
or
something
or
maybe
you
you
said
something
else.
It
was
like.
We
shouldn't
be
coding
outside
of
core
yeah.
B
B
Requests
on
node
core
without
an
Associated
has
not
been
a
positive
experience
for
me
in
the
past,
so
you
know
we
could
create
issues
and
and
try
to
drum
that
up,
but
ultimately
either
somebody
from
this
group
or
somebody
else,
who's
interested
needs
to
do
it.
We
can
certainly
get
try
to
get
the
word
out
to
pay.
This
is
what
working
on,
and
this
is
what
we'd
like
to
be
doing.
I
guess
I
would
not
jump
to
creating
an
issue
or
whatever
right
away.
Yes,.
A
I
do
think
if
we
have
something
pretty
clearly
defined
like
like
choking
her
again
I
think
it
could
be
good
to
rate
it
up
and
like
I
was
saying
just
because
you
know,
maybe
maybe
what
we
do
is
we
help
bring
them
something
who's
just
getting
involved
in
no
decor.
We
help
them
build
the
issue
by
going
and
like
soon
as
they
get
the
polar
puck
to
open
encore.
We
can
come
in
and
say
we're
really
excited
about
this.
This
meets
our
tooling
group
initiative.
A
A
B
So
I
think
originally
we
wanted
to
do
every
other
week
and
at
this
time,
and
it
turns
out
that
we
had
to
move
it
because
we
conflicted
with
benchmarking
working
group
and
so
I
moved
it
forward
a
week.
But
then
we
conflicted
with
the
benchmarking
working
group
again
and
I'm
like
what
the
hell's
going
on
well
what's
going
on
is
the
benchmarking
working
at
Group
meets
every
three
weeks,
and
so
we
can't
be
in
every
other
week
at
this
time,
and
you
know
Jordan
raised
an
issue
or
made
a
comment.
He
was
like
well.
B
Why
can't
we
just
let
why?
What?
Why
can't?
We
only
you
know
stream
one
thing
at
a
time
like
why
can't
we
pay
YouTube
to
stream
multiple
things
like
how
does
that
work
what's
going
on
there,
and
so
somebody
should
follow
up
on
that.
Maybe
I'll
follow
up
on
that
with
Michael
Dawson
and
ask
him
who
to
ask
or
whatever,
but
I,
would
rather
not
meet
every
three
weeks
I
like
the
idea
of
two
weeks,
but
unfortunately
that
will
cause
a
problem.
A
B
B
Can
live
with
that
for
right
now,
but
I
would
like
to
see
if
we
can
solve
that
problem.
Otherwise,
and
you
know
creating
a
a
doodle
pool
pole
and
having
everybody
try
to
vote
on
a
workable
time.
I
feel
is
like
the
ultimate
pain
in
the
neck
and
so
I'd
rather
not
do
that,
since
it
seems
quite
a
few
people
can
make
this
time.
A
A
There's
something
like
is
this
kind
of
interesting
like
Duke?
Does
code
transformation
potentially
have
you
know,
would
this
be
the
purview
of
the
tooling
committee?
Yeah
would
be
worth
I
think
just
we
should
try
to
know
real,
actually
I,
don't
let's
just
try
to
actually
have
a
conversation
with
Dan,
something.
C
Think
it
comes
from
the
like,
I
think
it's
looking
at
it
from
at
the
actual
applications
that
grow
up
or
NC
or
stuff
like
that
that
have
that
that
cause.
You
know,
upstream
pressure
into
the
standard,
think
likes
modules
and
and
that's
that's,
how
I
see
it,
which
is
interesting,
which
is
like
stuff
that
I've
been
thinking
about
like
can
changes
in
the
language
allow
for
better
tooling.
Thank
you
like,
for
instance,
modules
and
tree
shaking
and
and
things
like
that.
That's
like
an.
A
F
C
It's
it's
something
that
I
just
don't
believe
in
the
whole
next
J
SNCC
concept,
server
less,
you
know
lamb,
dicing,
everything
and
and
a
little
bit
in
a
similar
vein.
I
had
some
discussions
about
like
up
streaming
things
like
acorn
or
or
spray
our
babble
into
node
and
making
it
like
finding
the
way
to
make
it
more
language
forward,
because
at
the
moment
it's
it's
even
if
it
even
lags
behind
v8
in
the
sense
of
what
node
can
what
you
language
features,
no
can
implement
and
I.
C
A
Know
because
I
mean
like
Babel,
has
a
really
close
relationship
with
tc39,
because
Babel
is
used
to
test
how
the
language
would
feel
with
new
proposals.
So
it
kind
of
feels
like
a
natural
extension
to
know.
We
have
a
close
relationship
with
Babel
to
like
okay.
If
it's
actually
an
adopted
standard,
it's
just
not
in
v8.
Yet
Dewey
is
a
jimmdon.
Nobody,
but
maybe
that's
a
terrible
idea
of
it.
I.
F
C
B
B
C
C
The
rift
or
on
does
it
won't
say
where,
but
like
a
big
gap
between
work,
that's
done
a
note
core
and
work.
That's
done
and
all
those
tools
and-
and
there
was
in
I
think
too
little
intersection
between
these
two
domains
and
I.
Think
it's
an
interesting
place
to
let's
say
think
about,
like
you
said,
I'm,
not
sure
exactly
how
or.
A
One
thing
that
comes
to
mind
for
me
is
like
we
have
this
whole
MJS
thing
like
no
one
wants,
like
some
people
want
MDS
some
people
don't
want.
Em,
Jess
and
MPM
floated
a
patch
that
added
ESM
support
a
couple
years
ago,
using
a
thorn,
and
the
idea
was
that
you'd
have
like
an
acorn
compiler
sitting
in
the
node
core
code
base
that
could
handle
this
new
language
construct.
A
A
C
A
D
A
A
So
you
so
right
now.
Test
coverage
uses
a
build
step
and
note
that
transcloud
all
of
the
source
code
and
it
takes
20
minutes
for
the
test
suite
to
run,
and
it
has
to
replace
all
the
JavaScript
with
different
JavaScript
and
now
that's
not
needed,
really
excited
about.
That
is
that
no
tooling
I
think
a.
A
A
B
B
Wants
to
talk
about
something
at
the
next
meeting.
All
you
need
to
do
is
put
the
the
tooling
agenda
label
on
that
issue,
and
it
can
be
anywhere
it
doesn't
have
to
be
in
in
the
tooling
repo
you
can
put
it
in
any
repo
in
the
nodejs
already,
and
it
will
end
up
in
the
meeting
notes
and
the
meeting
announcement
and
all
that
crap.
So
please
do
that.
If
there's
something
that
you'd
like
to
talk
about.