►
From YouTube: 2021-06-07-Next 10 years of Node.js
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
June
7
2021:
we
will
follow
the
agenda
for
the
issue,
which
was
posted
in
the
repository,
which
was
issue
number
71.,
I'm
just
navigating
there.
If
people
can
add
themselves
to
the
attendees
here,
oops
hold.
A
There's
the
link,
and
so
before
we
get
started,
does
anybody
have
any
announcements
or
anything
that
they'd
like
to
share.
A
Nope,
okay:
well,
let's
move
on
to
the
issues.
We
have
tagged
so
the
two
first
ones,
I
think,
will
probably
keep
us
busy.
The
first
one
is
is
looking
at
the
survey
feedback
that
we
got
last
time
we
got
together.
We
looked
at
the
first
part,
but
we
can
go
through
the
second
part
and
then,
if
we
get
through
that
we
have
the
second
issue,
which
is
the
key
technical
areas.
We've
got
some
feedback
from
the
the
collaborator
base
in
terms
of
what
they
saw
was
important
and
so
forth.
A
Okay,
so
this
is
the
the
slide
deck
I
think.
Last
time
we
spent
a
good
amount
of
time
looking
at
the
constituencies,
so
basically,
where
people
identified
with
and
then
the
gaps
that
were
not
covered,
we
dove
into
the
the
comments
we
came
up
with
a
pr
which
I
can
go
back
to.
A
Which,
basically,
I
I
landed
recently,
which
was
to
update
the
constituencies
based
on
the
survey
that
we
got
so
we
basically
had
agreed
to
add
in
you
know:
education
and
security
practitioners,
so
that's
sort
of
catching
people
up
as
to
where
we
were
from
the
last
discussion.
A
At
this
point
we
should
we
can
move
on
to
the
next
set
of
questions
in
terms
of
the
you
know
what
people
thought
was
important
and
I'm
trying
to
see
bigger.
B
A
D
B
A
A
Okay,
great
idea
for
downloading
so
okay,
so
we
can
go
through
here
in
terms
of
maybe
take
a
quick,
we'll
take
a
look
at
like
through
the
ones
that
we
had
how
people
identified
or
didn't
identify,
and
then
we
can
look
at.
There
was
also
a
write-in
for
things
that
you
know,
potentially
we
didn't
think
about.
So
obviously,
this
good
understanding
of
a
direction
and
a
prod
of
the
project
seem
to
really
resonate.
B
B
A
E
Do
we
did
we
have
that
the
one
that
got
the
most
is
actually
rather
an
ambiguous
option
for
what
its
meaning
is
right?
I'm
trying
to
remember
when
we
did
the
planning
I
actually
may
have
missed
that
meeting
too.
But
what
did
we
intend
by
that.
A
Is
what
I
would
read
into
that,
but
again
you're,
probably
right
that
we
don't
have
a
we
don't
have
you
know
we
the
way
we
did
it
is
we,
you
know
through
the
fun
retro
we
put
down
things
and
then
discuss
them.
So
I
don't
think
we
have
anything
more
detailed.
A
E
Okay,
this
one
seems
to
me
like
what
I
would
call
like
table
stakes
like
it's.
Of
course
it's
important
to
everybody.
Otherwise
we
wouldn't
use
it
like
they
wouldn't
use
node
at
all.
If
it
didn't
have
that
right
so,
like
I
don't,
I
don't
necessarily
see
a
ton
of
value
in
seeing
that
that
one's
the
top,
like
it's
kind
of
like
well
yeah,
so.
A
B
E
A
E
Docs
either
so
that,
if
we,
if
we
called
this
one
docs
right
as
far
as
like
moving
forward
that
to
me
makes
sense
and
also
I
understand
why
it
would
end
up
being
the
top
rated
as
well.
In
that.
A
A
Okay,
so
predictable
and
stable
releases.
You
know
that's
a
good
good
to
see
that.
A
I
think
that
I
guess
the
follow-on
questions
would
be.
Do
we
think
like
for
that
one?
I
think
we
actually
have
a
pretty
good
story
right
like
in
terms
of
you
know,
we
have
a
well-defined
lts
process.
We've
been
executing
on
it
for
a
number
of
years,
so
I
would
say:
that's
that's
like
confirmation
that
what
we're
doing
there
is
important.
We
should
continue
to
do
it,
but
I
wouldn't
see
any
actions
action
items,
but
maybe
that's
what
we
have
to
figure
out.
So
you
know
on
these.
A
E
So
to
me
this
is,
like
you
know,
james
made
that
proposal
a
few
months
ago
about
like
changing
the
release
process,
or
you
know,
and
and
this
to
me
would
be
to
take
to
that
conversation
and
say
a
lot
of
people
say
that
the
predictability
and
the
stability
is
really
important.
Would
you
know,
would
that
affect
how
that
conversation
went.
A
Yeah
yeah,
it's
it's
definitely
good
data
and
then
but
the
second
thing
is
like
maybe
out
of
this,
we
want
to
come
up
with.
How
well
do
we
think
we're
doing
on
each
of
these,
as
you
know
that
that's
sort
of
a
thing
to
to
help
prioritize.
If
we're
looking
at
like
what's
important
to
to
work
on,
but
okay,
so
that
one
then
the
next
one
you
said
was.
A
So
again,
that's
sort
of
like
yeah.
We
need
to
be
up
to
dateish.
We
can't
just
let
things
go
stale
next
after
the
sir
go
ahead.
A
B
A
B
C
E
High,
so
now
that
we've
kind
of
gone
through
some
of
them,
my
thinking
here
is
like
the
most
value
here
would
be
to
maybe
take
out
the
top.
You
know
five
and
the
bottom
five
and
like
maybe
take
that
to
a
larger
audience,
saying
like
here's,
here's,
what
people
find
important
here's,
what
people
didn't
find
important
right
because
there's
a
lot
in
the
middle
you
know,
but,
like
I
don't
know,
if
we
can
gain
a
lot
of
valuable
information
from
those
ones,
I
think,
but
just
looking
at
you
know
easy
contour.
D
A
Like
what
our
first
thing
was
to
like
validate
that
we
had
a
decent
list-
and
I
I
so
it's
interesting
to
look
at
the
lower
ones,
but
I
also
agree
with
like
the
comment
you
just
made:
wes,
that
just
because
they're
low
doesn't
mean
they're
not
like
we
didn't
get
validation.
Is
that,
like?
I
would
have
actually
expected
some
of
these
to
be
lower,
because
it's
a
smaller
subset
of
this,
the
bigger
group
that
we
went
to.
E
A
cross
reference
of
those
and
find
like
which
constituencies
map
to
which
important
things,
because
that
would
then
validate
our
constituency
to
feature
matrix,
that
we
have
right
right.
Yeah,.
A
E
Well,
it
might
be,
it
might
just
be
end.
Users
who
are
more,
like
you
know,
in
tune
with
open
source
needs
right.
You
know,
but
still
even
even
so,
I
think
just
this
list
is
only
valuable.
If
we
sort
it
and
then
then
it
could
be
a
bit
misleading
because
things
will
fall
to
the
bottom
that
are
super
important
but
to
a
certain
constituency.
E
C
A
I
mean
for
me
the
main,
the
you
know
the
we
can
go,
look
at
the
ones
we
missed
the
the
the
one
of
the
key
things
was
like
we'd,
come
up
with
a
list
that
we
think
this
was
actually
a
good
list,
and
so
my
question
is
here
like
do
we
do
any
of
these
numbers?
Make
us
think
that
one
of
these
things
really
isn't
a
need
is
one
question
and
I'm
not
sure
that
I
see
anything
in
there.
A
That
says
like
we
didn't
get
zero
for
anything
and
the
ones
which
are
lower
you
know
are
are
potentially
understandable
because
of
that
reason
of
hey
it
was
a
subsection
right,
so
it
doesn't
mean
they're.
Not
it's
still
important,
not
still
something
that
we
need
has
a
need.
It's
just
that
yeah,
okay,
there
was
a
smaller
subset
and-
and
we
still
got
confirmation
that
the
people
in
that
group
likely
you
know,
saw
that
as
a
as
a
reasonable
thing.
A
So
so
before
we
look
at
the
ones
that
were
missed,
like
does
anything
here
stand
out,
I
guess
is
like.
Is
there
a
surprise
here
to
anybody.
B
True
and
I
think
with
the
result,
we
have
a
lot
of
people
who
really
see
node.js
as
a
mature
and
stable
language
and
from
other
languages.
I
think
it's
also
a
lot
of
feedback
from
people
using
it
in
production,
maybe
in
bigger
company
or
really
being
used
as
a
key
tool
for
for
users
and
for
just
for
company,
because
you
have
a
lot
of
stuff
linked.
A
E
We
we
technically
have
some
level
of
answer
to
that
question,
along
with
the
which
constituencies
do
you
identify
with.
I
don't
know
if
I
can't
remember
so,
I
think
it's
a
little
bit
right
yep
and
it
kind
of
lines
up.
I
think,
to
what
you
were
just
saying,
which
is
like
I
don't
know.
E
Yeah,
I
wonder
if
that's
I
mean
it's
got
to
be
seeing
as
the
numbers
are
there,
but
I
think
a
lot
of
that's
going
to
be
devops.
You
know
sort
of
set
up
right
where,
where
people
probably
checked
off,
I
have
a
direct
end
user,
I'm
an
application
operator
and
I'm
an
application
developer
right
right,
probably
even
library
and
package
authors.
I'm
actually
surprised
that
that
one
ranked
so
high,
I
would
have
thought
classes
yeah.
C
A
E
E
Google,
google,
okay,
I
was
gonna,
say
that's
something.
I've
seen
internally
at
netflix
is
a
lot
of
people
say
they
publish
packages
but
they're
packages
that
are
only
consumed
by
their
team,
whether
or
not
they
and
some
of
them
even
say
well
yeah,
I
write
libraries,
but
they
actually
are
part
of
the
monorepo
and
don't
even
publish
them.
So
I
think
there's
a
little
bit
of
ambiguity
there,
which
is
fine.
That's
it.
E
I
mean
one
of
the
benefits
of
this
module
ecosystem
we
have
is
that
they
don't
always
have
to
publish
them
and
that's
fine,
but
they
think
about
them
as
libraries,
you
know,
so
they
might
have
workflows
that
are
library
like,
but
yeah.
A
Okay-
and
I
think
just
before
we
move
on
like
the
last
thing,
which
was
kind
of
interesting,
is
just
this-
the
you
know
it
was
like
five
percent
said
they
had
needs
which
weren't
covered.
So
I
think
that
at
least
says
well,
like
95
of
the
people
felt
that
we'd
covered
off
what
they
were
looking
for.
So
maybe,
if
we
now
flip
over
to
look
at,
I
can
find
that
the
survey
results
where
we
can
look
at
what
we
might
have
missed
and
is
this
going
to?
Is
this
readable
yep
at
least
as
we
do.
A
Okay,
now
this
is
where
I
need
to
find
the.
I
think
it
was
this
one.
I
think
it
was
in
the
wrong
order
right
right.
What
needs
are
not
covered
in
the
list?
Yeah
and
that's
readable
for
people
yep
the
size
is
good.
Okay,
so,
basically
the
first
one-
I
guess
is
people
talking
about
you
know
just
the
stability
of
the
the
project
itself.
A
E
So
the
way
I
read
this
answer
is
somebody
who
is
assessing
a
stronger
commitment
to
supporting
node,
probably
at
a
company,
because
otherwise,
why
would
you
care
about
10
years
out
right?
And
if
that
is
the
case,
I
would
think
that
popularity
and
usage
statistics
would
be
the
thing
that
would
help
them
gain
that
understanding.
E
You
know
growth
of
the
ecosystem,
stuff,
like
that
which
you
know
I
don't
know
how.
Well
we
do
at
talking
about
that
stuff,
that
kind
of
stuff.
You
know
right,
I'm
exposed
to
it
because
I'm
here
but
like
you
know,
I
would
be
interested
to
see
if
there's
like
some
people
who
are
less
in
touch
with
the
ecosystem,
who
still
need
to
assess
for
their
company.
Whether
node
is
a
good,
you
know:
choice
like
where
do
they?
Where
would
they
go?
You
know
right.
A
A
A
B
B
E
Which
is
great,
I
I
think
we
should
to
me
this
answer,
though,
signifies
like
some
piece
is
missing
from
somebody
trying
to
figure
out
the
the
rest
of
the
ecosystem
and,
to
be
honest,
the
http
server
is
probably
not
the
right
thing
to
have
at
the
top
of
that
page
like
maybe
we
need
to
have
like
a
landing
page
that
gives
both
the
community
and
the
like
the
blurb
about.
You
know
what
it
is.
It's
fine,
a
code
block
of
the
server
is
probably
not
very
valuable.
There
now.
A
So
this
yeah,
I
think
I
think
I
take
wes
point
that,
like
we
don't,
none
of
these
are
actually
like.
Why?
No,
why?
Why
bet
on
node
right,
like
wherever
the
order
is
or
whatever
a
y
bet
on
node,
probably
makes
sense
in
terms
of
a
cell
and
and
so
yeah?
A
I
think
that's
that,
like
I'm,
just
taking
a
note
here
that
I
think
that's
one,
we
should
consider
as
a
missing
need
in
terms
of
the
like
assets
that
say
why
you
would
bet
on
node
and
so
organizations
that
are
coming,
and
you
know
we
can
prioritize
with
everything
else,
but
I
could
see
that
being
like.
If
you
want
us
to
be
successful,
we
want
people
to
have
those
assets
and
to
say,
okay
yeah.
I
am
going
to
bet
on
note
right.
E
Yeah
totally,
I
think
about,
like
you
know
when,
when
we
were
putting
together
the
thing
for
the
collab
space
and
darcy
brought
all
these
stats
from
the
github
and
npm
ecosystem
stuff
and,
like
that's
the
kind
of
stuff
where,
if
you're
a
director
and
you're
you
know,
company
and
you've
got
a
bunch
of
engineers.
Saying
hey
like
we
want
to
write
some
javascript
on
the
server.
Can
we
make
a
big
bet
on
this
and
like
hire
some
new
people?
If
I'm
the
director,
I'm
that's
the
thing
I
want
to
look
for.
E
I
I
don't
really
care
about
what
the
technology
platform
is.
I
want
to
know
that
there's
you
know.
10
billion
downloads
a
month
on
the
thing
and
big
companies
are
committed
to
it
and
we've
got
you
know
an
active
contributor
base
of
you
know
hundreds
of
people
like
that's
the
stuff,
and
I
actually
don't
see
that
on
the
even
in
the
like
working
groups
and
these
other
things
like
yeah,
it's
targeted
toward
the
contributors,
it's
targeted
toward
the
programmers,
the
ics.
E
A
I
think
there's
the
marketing
team,
which
is
now
like
under
the
opengs
foundation,
so
it
may
be
marketing
more
than
node,
but
you're
right
that
I
don't
think.
We've
got
that
connection
and
I'm
thinking
now
like
I've,
been
writing
internal
decks
to
say,
like
hey,
we've
got
a
bunch
of
products.
I
want
to
convince
those
products
that
we
should
be
putting
the
assets
in
place
for
node.js
developers
and
that's
exactly
the
kind
of
thing
I've
been
like
trying
to
say,
like
here's,
some
numbers,
why?
A
A
The
next
things
there
good
type
information.
That's
very
specific,
I'm
not
sure
we
would
add
that
in
as
one
of
the
specific
needs,
but
I
think
it's
good
feedback
in
terms
of
our
technical
priorities.
D
A
E
That's
hard
to
say
I
wonder
too,
because
I
don't
know
for
certain,
but
where
is
the
collaboration
happening
between
us
as
the
node
project
and
typescript
as
a
language
ecosystem
like?
Is
it
happening
just
one
off
in
the
repositories
like
the
types
that
most
people
use
are
not
coming
from
they're
coming
from
definitely
typed?
A
You
know
the
the
node
repo,
so
I
I
know
there's
some
effort
and
some
people
pushing
that
forward.
I
think
it
might
be
bradley,
but
I
I
yeah,
I
think
there
isn't
like
a
strong
like
there
isn't
a
types
team
or
a
working
group
or
something
like
that.
A
E
E
Have
been
the
thing
that
would
have
broken,
I
have
still
don't
know
why,
like
somebody
else
who
writes
typescript,
came
in
and
fixed
it
for
us
and
like
great,
but
like
not
great
from
a
user
experience,
especially
you
know.
If,
if
I
didn't
have
the
confidence
that
disabling
the
type
linting
was
going
to
still
be
fine,
you
know,
and-
and
that
definitely
is
a
story
where
you
know
I
all
the
battles
that
we
had
in
express
with
with
this
was
was
always
painful.
E
It
would
definitely
be
you
know
something
worth
at
least
having
like
a
really
clear
best
practice
around
from
the
platform,
so
that
we
don't,
you
know,
introduce
those
kind
of
right
user
experience,
problems.
A
Okay,
so
maybe
maybe
let's
move
on
to
some
of
the
others.
But
I
took
a
note
that
typescript
is
called
out
a
number
of
times
in
the
needs
and
we
can
kind
of
not
sure
whether
that's
actually
like
a
separate
need
or
fits
into
our
technical
priorities.
But
we'll
note
that
for
now
the
next
one
was
game
developers.
E
E
That's
not
to
say
you
can't
write
a
game,
the
server
side,
part
of
a
like
a
multiplayer
game,
or
something
like
that
in
node,
but
also
at
that
point,
isn't
it
just
like
an
application
like
a
like
fit
into
the
application
developer
constituency
like
maybe
they
have
different
needs,
but
it
really
they're
writing
an
application.
It's
just
that
application
has
specific
needs.
D
Yeah,
I
was,
I
was
a
game
developer
myself,
like
a
few
things,
I'm
looking
one
major
thing:
I'm
looking
forward
to
is
the
quick
implementation
that'll
be
like
excellent
for
just
game
server
stuff,
but
also
like.
I
would
really
like
to
see
like
webgl
support
like
at
some
point.
I
don't
know
that
that
would
ever
happen,
because
it's.
E
D
D
It's
just
a
like
a
platform
that
you
can
run
whatever.
There's
like
command
line
tools
and
all
sorts
of
stuff.
You
can
build
with
it,
but
ui
stuff
is
a
thing
you
can
do
with
it
and
there's
kind
of
other
diverging
projects
like
electron
that
do
that
it
would
be
cool
to
have
a
similar
sort
of
thing
like,
even
if
it
was
a
diverging
project
which
was
just
node,
plus
webgl
and
like
whatever
other
things,
you'd
need
the
like
audio
stuff
as
well.
A
E
You
know
what
what
what
gets
what
gets
included
and
what
doesn't
is
what
I
meant
by
finding
the
line.
Like
you
know.
Obviously,
shipping,
html
and
css
is
like
well.
We've
got
browsers
like
let
them
do
that.
The
node
platform
probably
doesn't
need
it,
but
it's
interesting
to
know
that,
like
you
could
use
webgl
in
node
to
make
a
game
for
the
switch
where
you
wouldn't
need
all
the
rest
of
the
stuff
for
the
browser
so
yeah.
E
I
think
that's
like
an
interesting
one
that
might
end
up
being
like
a
niche
where,
like,
if
somebody
got
really
into
it
and
wanted
to
you,
know
ship,
an
npm
package
that
compiled
that
against
you
know
that
was
usable
in
node.
You
know
so
I'm
thinking
like
johnny
5.
You
know
that
was
like
a
really
good
important
thing
to
be
able
to
start
talking
to
iot
devices
like
if
there
was
a
library
like
that
that
implemented
webgl
in
user
land
in
here
that
should
be
possible.
E
D
Well,
how
like
most
at
least
console
environments,
work
it's
not
really
reasonable
to
just
like
write
an
mdm
module
and
call
it
done.
D
It
would
kind
of
be
more
like
an
electron
situation
where,
like
you,
have
to
have
a
custom,
build
that
integrates
all
the
stuff.
It's
like
a
lot
of
these
environments,
won't
let
you
run
external
code
or
the
way
their
build
process
works.
There's
just
like
there's
no
file
system
on
a
lot
of
these
systems,
so
you
can't
load
stuff.
You
have
to
have
it
like
built
like
baked
into
the
binary
or
like
things
like
that,
so
having
an
electron
like
thing
or
something
to
do
that
would
be
cool.
D
E
Well,
so
that's
where
it
borderlines
on
some
of
the
other
ideas
about
like
building
a
node
that
doesn't
have
like
the
http
stack
or
like
all
these
other
things
that
you
could
exclude
say
you
were
writing,
then
this
is
not
just
a
game.
Development
say
you're,
writing
a
cli
and
you
want
it
to
be
super
slim
and
really
fast.
E
So
you
would
want
to
compile
out
all
and
like
cross-platform
like
say
you
wanted
to
build
like
a
go
binary
style
thing
that
you
distribute
to
your
customers
right,
yeah,
and
so
it
come
with
the
full
platform.
If
you
wanted
to
do
that
today,
you're
shipping,
a
huge
binary
like
we
I've
done
this
and
it's
a
gig
or
whatever
you
know.
If
you
could
compile
out
all
of
those
things
that
you
don't
need
and
end
with
just
some
basic
things.
E
You
could
do
the
same
kind
of
thing
for
a
game
and
that
would
have
that
sort
of
feature
set
would
have
applicability
more
than
just
in
the
gaming
scenario.
It
would
be
great
for
cli
it'd,
be
great,
for
you
know,
deploying
to
the
to
a
a
serverless
environment
where
you
wanted.
Really
fast
startup
times
right,
like
there's
all
these
little
things
where
that
feature
set
could
be
leveraged.
E
And
then,
if
we
had
things
like
a
quick
module
say
we
had
an
easy
way
to
bundle
library
code
into
a
node.js
build
right.
Then
you
could
have
it
live
as
an
npm
module.
E
A
We've
got
a
little
bit
into
the
technical
yeah,
we're
a
little
bit
in
the
weeds.
So
let's,
but
I
think,
we've
you
know
took
a
few
notes.
There.
D
D
Yeah,
I
don't
know
if
anyone's
used
m
ruby,
but
it's
a
great
example
of
like
it
has
a
module
system,
but
like
it's.
Its
entire,
like
core
api,
is
part
of
module
system
that
there's
just
like
a
default
set
that,
like
all
this
stuff
is
pulled
in
unless
you
tell
it
not
to,
but
you
can
like
trim
it
down
to
like
this
build,
has
literally
nothing
in
it
and
it
can't
do
anything
actually
useful,
but
I
can
build
it
this
way,
or
I
can
just
like
pick
and
choose
which
things
I.
A
Want
the
above
select
would
be
good
enough:
okay,
so
a
built-in
module
that
can
replace
https
for
back-end
frameworks.
E
That's
an
interesting
one
without
more
details,
though
I
don't
know
we
can
get
a
lot
into
it
like
so
we
were
we've
been,
you
know
we
were
talking
and
we
sort
of
tabled
a
bunch
of
it
about
the
the
new
http
apis
yep,
and
I
and
I
I
almost
think
the
plan
that
we
had
there
solves
for
this,
because
we
would
have
a
lower
level
api
and
then
a
higher
level
api,
and
that
might
be.
You
know
what
what
they're
asking
here
like
the
higher
level
api,
is
what
I
was
thinking
right.
A
A
E
We
have
the
apis
that
people
need
right
and
where
we
don't,
we
should
be
filling
in
those
gaps
you
know
and
if,
if
it
requires
you
to
learn
a
whole
new
module
ecosystem
of
things
to
go-
and
you
know
build
a
you
know
some
web
server,
like
maybe
there's
parts
of
that
web
server
stack,
that
could
be
in
core
instead,
that
would
make
it
easier
right.
That's
the
way
I
read
it.
I
don't
know.
A
E
Yeah,
like
I
think,
about
the
like
fs
module
things
that
have
been
added
over
the
past
few
years.
It
was
like
look,
no
one
was
using
it.
They
were
all
using
some
userland
thing
that
gave
recursive
file
deletes
because
that's
like
mostly
what
people
wanted
so
pulling
that
into
core
is
like
absolutely
the
best
decision,
and
I
see
a
bunch.
D
A
E
D
E
A
A
By
easy
right,
yeah
yeah,
exactly
it's
like
I
mean
kubernetes
will
let
you
scale
and
you
know,
have
multiple
instances,
but
whether
you'd
call
that
easy-
and
I
guess
a
number
of
the
others.
Let
you
scale
but
possibly
in
a
much
smaller
context.
Right
like
you,
could
have
multiple
copies
running,
but.
E
I
mean
I
can
say
for
certain
that
scaling
anything
is
hard.
That's
you
know
just
going
to
be
that
way.
I
think,
having
you
know
things
like
diagnostic
tools
to
help.
You
understand
why
the
scaling
is
not
working
like
you
thought
it
would
is
the
best.
Probably
a
platform
can
do
right
because
it's
all
it's
so
dependent.
So
I
don't
know
that
there's
a
lot
right,
like
the
the
diagnostics
work.
Obviously,
performance
work
you
know,
but
other
than
that
you're
gonna.
E
As
soon
as
you
get
on
multiple
machines,
it's
not
really
node's
problem
anymore.
It's
like
your
platform's
orchestration
for
how
you
scale
and
you
know,
do
you
scale
in
response
to
cpu
pressure
or
like
what?
Like
all
of
those
questions,
it
depends
on
your
application.
So
I'm
not
you're,
not
there's
a
lot
to.
B
Yeah,
I
I
see
a
point
just
below
remote
debugging
in
kubernetes,
so
I
think
it's
almost
linked
to
what
you
just
said
was
because
I
think
it's
debugging,
but
it's
also
a
performance,
analysis
and
stuff
like
that.
B
It's
so
I
think
five
or
six
upper
where
you
are.
B
A
A
I
think
it's
good
to
know
like
this
is
like
okay,
people
are
scaling
and,
of
course,
and
large
systems.
We
don't
need
like
at
this.
In
this
case,
we
don't
need
to
solve
all
these
just
sort
of
note
them
and
say:
okay.
How
does
that
affect
our
our
like?
I'm
not
sure.
I
would
call
that
out
as
a
separate
constituency
need.
A
I
think
we
have
performance
in
here
somewhere,
whereas
right,
reasonable
resource
usage
performance
which
is
kind
of
in
that
scale.
So
I
you
know
from
the
macro
level
need
I
think,
we've
got
an
area
where
we're
covering
those
kinds
of
things,
as
opposed
to
like
a
complete
gap,
keeping
pace
with
the
jcgs
ecosystem.
A
A
C
A
Covers
this
yep?
Okay,
so
I
think
that
covers
that
it's
yep
now
I'd
agree.
This
is
kind
of
filling
in
some
specifics:
innovation
as
fast
as
possible,.
A
A
A
E
E
D
E
Yeah,
like
it's
just
not
going
to
happen
so
so
in
that
regard,
I
think
the
package
maintenance
working
group
sort
of
solves
this
problem,
which
is
like
get
some
folks
from
npm
and
hopefully
yarn
in
the
room
and
talk
about
like
what
gaps.
Those
tools
are
missing.
You
know
like
what
aren't
they
covering
and
in
the
case
of
like
this
particular
call
out.
E
You
know
they
maybe
have
some
very
specific
use
cases,
they're,
they're,
considering
and
there's
already
avenues
for
them
to
bring
those
to
light
via
the
the
package,
maintenance
working
group
and
the
npm
rfc
process.
And
then
you
know
the
yarn
issue
tracker
so
like
I'm,
not
sure,
there's
a
lot
to
gain
there,
except
that
this
is
really
important
to
the
community
and
it
sounds
like
this
person
thinks
there's
a
gap.
A
E
Maybe,
but
I
mean
honestly
go
to
the
npm
rfc
calls
and
you'll
see
there
are
people
bringing
up
ideas
around
this
all
the
time
and
it
gets
handled,
I
think,
pretty
effectively.
You
know
right.
Okay,
I've
been
very
impressed
with
the
progress
that
is
made
and
those
things
have
landed
in
npm
like
in
a
very
reasonable
time
frame.
You
know,
I
think,
and
yarn
has
its
own
different
process
and
I
think
they
move
they
move
and
land
things
quite
regularly
as
well
pnpm.
E
Similarly
so,
but
I
think
okay,
so
you
know,
I'm
not
sure
the
node
project
can
do
much
unless
the
ecosystem
really
changes
from
what
it
is
today
on
on,
where
those.
A
How
those
tools
are
maintained?
Okay,
simplification
of
apis,
I
think
that's
kind
of
related
to
the
apis
that
are
there.
I
guess,
although
it
sort
of
pushes
in
a
different
direction,
to
say
we
should
cut
things
out
versus,
add.
E
I
am
also
disappointed
that
we
removed
the
bundled
cli
debugger,
but
you
know
that's
in
the
past.
You
know,
but
that's
kind
of
like
the
this
is
the
you
know.
What
they're
asking
for,
which
is
similar
to
like
the
remote
debugging
in
kubernetes,
is
like
the
fact
that
we
don't
bundle
that
anymore.
I
know
it
was
a
maintenance
problem
or
whatever,
but
like
I
used
to
use
it
all
the
time
and
now
you
have
to
like
ssh
tunnel
the
debugger
session
across
and
it
you
know
like
it
is
kind
of
annoying.
E
Do
you
mean
node
inspect?
E
A
E
D
E
Know
bt
first
get
my
current
back
trace
like
there's
like
a
bunch
of
things
you
can
do
without
having
to
have
a
gui
on
your
local
machine
connected
up
through
some
sort
of
you
know,
debugging
pro
the
chrome
debugger
protocol.
The
old
way
was
like
what
I
think
they're
asking
for
here,
which
was
I
see,
browser
agnostic,
which
is
like
literally
on
the
box.
A
Yeah,
I
think
I
think,
though
I'll
have
to
go
back
and
look.
I
thought
we
actually
have
that
and
that
it's
like
we
have
been
shipping
note
the
node
inspect
client.
I
could
be
wrong,
though,
like
that's
what
my
understanding
was.
We
shipped
the
node
inspect
client
as
as
part
of
node
and
we're
actually
now
integrating
the
code
base
into
node
core
as
well
yeah,
but
I
think
that's
the
new
thing.
Maybe
I'm
wrong.
I
don't
know
I.
This
is
the
part
I
haven't
read
it.
E
C
A
Thing,
but
I
think
it's
the
new
thing
that
was
the
cly
replacement,
but
yeah
it
sounds
like
we
should.
We
should
both
go,
look
back
and
we're
two
minutes
over,
so
I
I'd
say:
let's
loop
back
again
next
week,
this
has
been
our
next
time.
This
has
been
good.
A
You
know
lots
of
lots
of
interesting
things
to
think
about
here,
we'll
next
time
we'll
go
through
the
rest
of
the
list
and
we've
still
got
quite
a
bit
to
go
through
and
you
know
after
we
get
through
that
we
can
sort
of
say:
okay,
based
on
the
survey.
What's
you
know,
has
it
confirmed
what
we
had
do
we?
What
do
we
need
to
add
to
our
to
our
needs?
A
If
anything,
and
then
you
know
next
steps
based
on
that,
and
I
think
it's
interesting
to
go
through
this
first,
because
some
of
these
are
sort
of
bleeding
into
the
very
specific
technical
asks
which
I
think
which,
when
we
get
into
the
the
feedback
that
we
had
on
the
technical
things
we
can
see
where
there's
some
overlap
here
and
it'll
be
interesting
having
gone
through
this
first.
A
No
well
thanks
for
everybody's
time,
and
we
hope
to
see
you
next
time
to
sort
of
continue
this
discussion,
which
is
quite
interesting
thanks
thanks,
okay,
bye.