►
From YouTube: Node.js Tooling Group Meeting
Description
A
B
Given
some
of
the
issues
around
trying
to
implement
that
at
the
C
c,
plus
plus
level,
we
think
it's
probably
best
to
just
do
it
in
JavaScript
and
so
from
there.
We
could
essentially
copy
and
paste
some
portion
of
rim
wrath
into
into
the
FS
library,
and
we
would
need
to.
We
would
probably
want
to
leave
some
of
it
out,
and
so
the
stuff
we
want
to
leave
out
includes
glob
the
glob
behavior,
because
with
the
user
Landreth
module,
what
you
can
do
is
you?
B
B
Where
I
feel
just
commented
a
minute
ago
about
hey,
but
but
what
about?
What's?
I
want
to
port
the
full
Shu
till
module
so,
and
so
Shu
till
is
Python
it's
in
Python
standard
library.
It
provides
some
more
higher
level
file
operations.
Like
a
rim,
RAF
it'll,
you
copy
an
entire
tree,
a
directory
tree.
D
If
we
do
it,
you
know,
let's
claim
the
space
and
call
our
implementation
our
entry,
because
concrete
now,
because
it
doesn't
glob
try
to
make
like.
So
what's
that
so
there
was
a
debate
started
on
Twitter
about
spoke
behind
versus
more
standardized
things
and
I.
Think
that's
like
great
idea.
Although
rim
raft,
the
npm
module
is
great,
but
you
know
sorry
to
collect
all
those
modules
and
like
making
a
hodgepodge
of
modules
in
core.
That's
gonna
bring
us
the
wrath.
D
C
C
D
D
I'm
saying
like
let's
say,
let's,
let's
say
we're
like
the
long-term
plan
is
to
have
CLI
tooling,
maybe
even
call
later
on,
and
things
like
copy
tree
move
copy
files.
Things
like
I
think
deal
goes
so
like
that's.
A
plan.
First
item
on
the
menu
is
our
tree,
which
is
a
Rimmer
under
under
the
hood,
and
it
has
nice
like
API
signature
and
to
this
tree.
This
is
this:
is
our
plan
and
then
we
can
copy
and
what
I
think
pythons.
You
know.
C
C
B
B
D
B
B
D
A
B
D
D
E
C
B
B
Okay,
I
would
volunteer
to
to
look
into
getting
that
or
talking
to
the
author,
so.
D
D
B
C
B
F
F
Basically,
what
is
happening
is
that
we
are
working
to
move
away
from
write
file
from
the
currency,
prosperous
usage
that
is
made
today
to
go
into
something
which
is
a
create
by
mapping
and
getting
the
performance
equally
available,
regardless.
If
different
era
is
running
or
not
on
Windows,
so
today
it
should
have
no
impact
to
the
tools
or
whatsoever,
but
we
are
making
good
progress
and
making
a
big
push
in
that
direction.
B
F
We
are
far
from
being
done
and
from
tooling
on
an
existing
project
prospective.
What
we
are
going
to
propose
is
to
have
a
hidden
switch
from
a
past
vibe
a
system
variable
or
something
that
would
disengage
the
new
way
of
dealing
with
five,
so
that
the
current
way
would
be
there
still
for
a
few
iteration
into
the
libuv
platform,
so
that,
if
somebody
is
kind
of
heat
where
you
are
with
the
difference
in
performance
with
style
management
in
an
existing
product,
it
would
still
be
possible
to
run
old
as
it
is
today.
F
So,
basically,
we
want
to
implement
that
in
a
way
where
it
would
be
by
default.
The
way
node
would
see
any
fives
on
deal
with
any
file
on
the
Windows
platform,
but
you
will
have
a
documented,
even
switch
or
argument,
which
is
part
of
another
discussion.
We
were
discussing
so
that,
basically,
if
your
project
will
be
broken
by
that
new
increase
in
speed,
that's
not
common
to
say
that
it
would
still
be
possible
to
fall
back
and.
F
That
one
reason
where,
as
a
river
fan
also
of
discussion
I'm
following
it
to
bury
those
very
carefully,
because
that
has
to
be
part
of
the
thinking
of
the
scenario
we
wants
to
validate
everything
before
we
move
on
in
a
direction
and
if
there
is
any
question
or
comment,
I
never
refer.
I
was
looking
into
that
performance
direction.
In
many
case,
please
do
not
hesitate
to
reach
to
us.
F
D
F
D
C
B
All
right
so
alright,
so
anybody
have
anything
else
on
that
front
or
rear
up
front.
So
the
next
thing,
then,
is
I'm.
Gonna
talk
about
this
now
is
argument
parsing,
if
you'll
find
that,
if
you
think
it
is
a
good
idea
and
that
we
should
add
or
work
to
add
something
around
it,
then
it
would
be
good
to
have
have
have
comments.
If
it's
probably
better
to
just
drop
it,
then
we
can
just
drop
it,
but
I
I
feel
like
I've,
invoked
the
wrath
of
the
small
core
crowd
a
little
bit
there.
So
what.
D
G
The
patient,
with
the
rating
form
a
standard
input,
but
just
this
just
the
minimalistic
approach,
at
least
that
should
be
covered
in
a
better
API
and
because,
at
the
end
of
the
day,
I
get
I
get
it
that
it's
against
the
whole
philosophy
of
node,
of
having
a
broad
at
the
standard
library,
but
at
least
a
very
minimal
like
that's
what
I
will
argue
for
and
the
whole
debate
about
argument,
parsing
and
also
standard
input.
Reading
did.
B
B
It's
this
big
wallet
text.
This
is
21
days
ago.
You
know
find
that
comment,
I'll
paste
it
so
where's
the
chat
here
this.
This
is
the
comment
and
then
down
here
at
the
bottom.
There
is
a
list
of
four
things,
and
this
is
like
I
was
trying
to
identify
what
essentially
all
argument.
Parsing
implementations
end
up
doing
no
matter,
you
know
how
fancy
they
get
or
what
language
they're,
written
and
I
mean.
Maybe
I
don't
want
to
say
that
maybe
I
just
say
you
know.
B
This
is
what
it
looks
like
when
you,
when
you
are
writing
an
argument.
Parser
enjoy
to
use
this
note,
and
this
is
kind
of
like
in
my
head.
This
was
the
minimal
functionality
that
you
would
need
for
this
to
be
useful,
and
so
does
that
sound
reasonable
is?
Is
there
there
more?
That
could
be
trimmed
off
of
that?
Is
there
anything
else
that
I'm
missing
that.
G
B
So
basically
it's
just
giving
you
a
nicer
data
structure
to
work
and
I.
Think
that's!
That's
all
that
a
lot
of
people
need
just
for
accepting,
like
the
bare
minimum
of
I
need
to
just
send
this
one
flag
to
my
program.
For
example.
Maybe
you
weren't
writing
a
CLI
program.
Maybe
maybe
you
have
like
a
server
you're
running
and
you
didn't
think
oh
I'm
gonna
need
to
send
options
to
this
thing.
B
Well
now
you
need
to,
and
so
something
like
this
would
make
it
easier
to
just
kind
of
bang
that
out
with
that
having
to
go
and
pull
down
a
larger
module
to
deal
with
it.
So
I
don't
know
that's
this
kind
of
where
everything
you
know,
even
even
the
people
that
that
don't
need
heavy
option,
parsing
or
a
very
robust
solution
can
use
something
like
this
to
just
get
their
arguments
in
a
nice
data
structure.
A
Having
a
slice
to
the
second
parameter,
like
you
said,
is
really
valuable.
This
came
up
at
work
last
week,
actually
cuz
all
our
code
samples
have
this
like
now.
Just
are
these
slice
tube
and
you're
good
to
go,
and
it
just
makes
for
hard
to
read
code
I,
think
onion
ated
as
possible,
like
get
rid
of
that.
It
would
be
nice
right.
So.
B
A
Is
like
the
meaning
of
like
single
versus
double
and
like
single
with
multiple
characters?
Is
that,
like
multiple
options,
we
said
at
once,
they're
just
like
people,
have
a
million
opinions
about
this
kind
of
thing.
So,
as
long
as
you
say
like,
we
have
no
opinions
about
what
you
do
with
the
argue
like
I,
don't
know
even
putting
them
in
an
object's
a
little
controversial,
because
you
do
have
the
like
be
setting
multiple
options
at
once.
A
The
problem
is
where
you're
gonna
run
into
a
slippery
slope.
Even
if
you
say
oh
we're,
just
gonna
populate
the
keys
of
an
object,
then
you're
gonna
run
into
well.
How
does
a
single
dash
differ
from
a
double
dash
like
if
it's
a
single?
Is
it
actually
multiple
keys
and
an
object?
And
then
now,
where
now
you'll
have
10
more
people
come
in
with
10
more.
D
D
A
As
a
default,
okay,
here's
an
idea
out
of
left
field
well,
I,
don't
hate
so
much
slice
as
a
default.
It
might
be
nice
and
maybe
you're,
just
coffee.
There's
now
two
things
populated
on
an
RD
object
or
something
another
option
like
I've,
been
talking
more
to
Daniel
Ehrenburg
about
what
might
be
in
the
standard
modules
in
in
v8,
and
you
know
just
in
the
standard
modules
namespace
like.
Maybe
it
doesn't
make
sense
in
node,
but
maybe
it
makes
sense
that
there's
a
minima
stand
standard
modules,
I,
don't
know
we're
thinking
about.
A
B
A
D
A
That's
like
like
yards
is
like
yards,
is
no
minused
and
yards
like
I've
just
spent
years
trying
to
come
to
the
best
compromise
on
a
bunch
of
these
things.
But
it's
just
like
the
number
of
issue.
The
number
of
interesting
arguments
around
like
trivial
things,
like
the
count,
that's
like
fairly
large
space,
with
a
lot
of
opinions
and
and
and
things
like
bzzz.
D
Less
skeptical
I,
don't
think
it's
I
am
Amit
as
again
from
my
experience,
people
are
not
against
opinions.
They're
against
reasoning
like
you
have
to
give
a
very
good
argument.
Why
did
this
entire
concept
should
be
in
core,
which
is
either?
It
covers
a
huge
use
case
or
having
it
in
core
gives
you
some
sort
of
benefit?
D
D
I
think
that's
a
very
good
argument
because
we're
not
no
we're
not
excluding
anyone.
Everyone
could
pick
their
own
other
implementation,
we're
just
helping.
You
know
the
poor
defenseless
rely
developer,
just
wants
to
read
a
couple
of
arguments
and
then
in
and
then
what
happens.
I'm
imagining
the
situation
like
the
project
manager
comes
in,
he
says
yeah,
you
have
2x
argument
and
then
he
comes
in
and
says:
well
you
have
to
negate
the
document
and
then
it
comes
no.
A
May
be
an
action
item
that
is,
someone
should
compare
yards
and
yards
and
commander
and
see
if
there
are
like
it
like
what
are
the
semantic
differences
between
the
two,
because
if
you
didn't
support
both
of
those
parsing
engines,
that's
the
vast
majority
of
the
sea
lies
on
the
registry.
Anything
else
a
look
at
boost.
E
A
C
A
G
Thing
that
bothers
me
about
having
more
complete,
like
implementation,
like
darts
commander
we're
discussing
here,
is
that
the
core
is
more
than
just
see
lies
right
and
that
that
might
be
like
a
big
argument
for
a
pushback
against
having
this
on
in
court
yeah.
If
it
was
just
for
catering,
see
alized
and
yes
definitely
bet,
but
it's
it's
not
so
much
more.
Today,.
D
Big
think
around
this
whole
group
I
know
this
is
very,
very
opinionated
towards
web
service
thing.
Why
should
you
PhDs
OpenSSH?
Broadly,
live
everything,
that's
geared
towards?
No
that's
first-class
citizen
use
case
and
what
does
group
is
I?
Think
one
of
our
mandates
is
to
remind
everybody
that
CLI
is
also,
and
and
if
we
have
you
know,
sleep
and
broadly
and
then
HTTP
HTTP
to.
D
B
D
A
There's
probably
more
consensus,
then
than
the
argument
on
github
would
think
because
I
don't
think
they're
like
I
mean
the
reality
is.
If
you
go
to
your
command
line,
you
want
most
of
the
programs
to
behave
the
same.
Like
you
kind
of
know.
What
you're,
like
you,
know,
you're
what
you're
gonna
get
when
you
type
double
to
a
sure,
yeah.
A
Don't
live
I.
Think
I
was
looking
at
the
seat
like
what
is
it?
Is
it
art
parse?
That
is
the
specification
and
it
does
seem
like
a
little
lacking
compared
to
what
I
know
people
like
in
yards
so
like
maybe
it's
an
argument
for
making
it
improves
it.
Maybe
it's
argument
for
a
new
specification.
Isn't
my
argument
is.
I
There,
a
least
common
denominator
that
can
be
identified
between
the
major
parsers
I
guess.
One
of
my
concerns
with
the
idea
of
bringing
argument
parsing
into
the
node
core
is
well.
For
example,
yargh
has
had
quite
a
few
December
majors
lately.
So
how
do
you
deal
with
that?
If
argument
parsing
is
in
the
core,
you
know:
does
my
program
only
work
with
no
12,
and
you
know
it
might
not
work
with
node
14.
D
A
D
A
A
C
A
Had
this
come
up
one,
because
my
new
job
at
Google
is
basically
helping
to
maintain
the
public
know
facing
node
libraries,
which
are
all
typescript
for
the
most
part.
So
we've
actually
been
having
a
bunch
of
conversations
this
week
on
around
those
libraries
having
porous
stack
traces
which
overlaps
with
the
test
coverage,
DUP
and
whining
to
do
and
I
found
a
month
ago.
It
turns
out
there's
a
source
map,
implicit
implementation,
MIT
license
in
the
v8
code
base.
A
A
A
The
stack
trace
you'd
want
to
be
applying
the
source
map
and
then
nodejs
actually
adds
its
own
content
on
to
the
exception,
which
is
where
you,
your
exception,
has
the
little
snippet
of
code,
which
shows
you
what,
where
the
exception
occurred
in
the
code
base,
that
is
added
by
node.
But
the
actual
line
position
of
the
exception
is
added
by
v8.
So
you'd
kind
of
kind
of
need,
source
map
support
in
both
places
to
get
a
clean
stack,
trace
and
then
there's
a
question.
A
Do
you
show
both
line
numbers
like
do
you
want
to
know
the
original
source
position
and
the
source
position
that
happened
in
the
transpiled
code?
Do
you
actually
maybe
have
a
link
to
where
you
would
find
the
non
transpiled
code
if
you
haven't
shipped
the
original
source
in
your
module,
like
there's
a
bunch
of
interesting
design
problems,
the.
C
A
D
B
A
That's
fair
and
I
think
that
brings
up
two
points
or
like
one
like.
We
should
try
to
get
Rebekah
on
this
call,
so
we
do
have
a
representative
from
NPM
and
to
why
I'm,
just
gonna
say
like
even
even
if
it
may
be.
That's
surveys
skewed
like
it's.
You
can't
argue
at
the
fact
that
there
is
a
lot
of
transpiled
code
on
a
registry.
A
A
C
D
Time,
that's
like
it
comes,
and
it
goes
super
political
yeah,
but
regardless.
If
and
if
I
wanted,
to
think
that
I
love
to
know
that
at
least
in
Windows
it's
it's
a
single
file
and
it
just
works
and
it
can
do
anything
except
NPM
is
except
fetching
packages
which
is
but
the
first
thing
that
you
do
this.