►
From YouTube: 2921-10-27-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
So
welcome
to
the
node.js
next
10
meeting
for
october
27th
2021
before
we
get
started,
I
guess:
does
anybody
have
any
announcements
they'd
like
to
share.
A
I'll
just
say:
for
any
collaborators:
there
is
a
pr
open
in
the
repo
just
documenting
and
capturing
our
the
technical
priorities
that
this
work
this
group
has
worked
on.
So,
if
you
can
go,
you
know
check
that
out,
comment
get
in
the
discussion
or
approve.
That
would
be
fantastic.
A
B
C
Yeah
I
looked
at
it.
I
have
been
poking
at
this
for
several
weeks.
Basically
anytime,
I'm
not
working
on
something
else.
This
is
what
I'm
working
on.
C
I
I
you
know
have
a
good
image.
I
have
a
good
docker
image
that
is
a
dev
container
that
works
as
a
dev
container.
The
challenge
right
now
is
getting
it
small
enough,
so
code
spaces
will
launch.
C
I
I
prefer
not
to
have
to
tell
people
use
the
bigger
code,
spaces
vm,
so
there's
like
four
tiers
of
vms
standard
is
standard
and
that
has
32
gigabytes
of
storage.
The
docker
image
with
a
warm
cache
is
pretty
chunky.
It's
like
20,
I
I
it
started
at
28
or
29.
I've
gotten
it
down
to
24
gigabytes,
I'm
basically
just
poking
through
and
and
tearing
out
what
I
can
as
I
go.
If
anyone
has
advice
on
like
hey,
you
can
delete
this
three
gigabyte
directory
that'd
be
great.
C
I
and
progressively
you
know.
As
I
tear
out
more
and
more
the
code,
spaces
environment
set
up,
gets
further
and
further
along.
So
I
I've
gotten
it
significantly
further
at
this
point,
and
I've
learned
some
interesting
things
but
yeah,
that's
I
I'm
I'm
poking
at
it.
A
C
Mean
if
you're
a
node
collaborator
you
have
that
comp
to
some
extent,
I'm
sure
there
will
be
a
cap
and
we'd
have
to
share
that
out
later
yeah,
but,
like
I
don't
want
people
to
have
to
do
the
premium
one
that
has
like
you
know
it
costs
a
little
bit
more,
but
it's
it's
more
steps.
It's
not
just
click
like
it's
like
more
steps
in
that
it's
two
extra
clicks.
It's
also.
C
Space
32
gigs
of
disk
space
yep,
and
it
there's
I'm
I'm
not
fully
sure
on
like
how
the
infrastructure
works
and
why
the
24
gigs
is
too
big
but
yeah
it
it
dies.
A
Like,
like,
I
think,
there's
some
tools
like.
I
know
the
rail
that
I
run
pops
up
like
a
graphic
that
says:
here's
your
where
the
disc
where
all
the
stuff
is
used.
Have
you
looked
at
that?
I'm
just
curious.
C
Where,
where
hold
on,
where
are
all
that?
That
was
the
point
I
got,
I
mean
it's,
it's
you
know,
I
I'm
putting
it,
I'm
basically
trying
to
make
a
warm
cache,
docker
image
of
building
nodes,
so
I'm
I'm
building
node
and
then
consuming
that
node
for
development.
Theoretically,
so
that
the
cash
is
there
and
we
don't
have
to
rebuild
too
much
every
time.
C
If
that's
a
bad
idea,
if
that's
not
smart,
your
y'all
would
be
the
one,
the
best
ones,
to
tell
me
that
but
yeah
like
I
don't.
Basically,
I
want
someone
to
be
able
to
hit
build
as
soon
as
they
get
into
the
docker
image
and
have
it
be
fast
rather
than
slow,
yeah.
B
No,
it's
not
tiny,
but
there
are
a
few
things
that
might
be
going
on.
Generally.
F.
Dupes
might
help
you
that's
finding
duplicate
files,
also
docker
images
depending
upon
how
they're
layered
can
explode
in
size,
so
deleting
operations
still
use
up
that
full
amount
of
disk
space.
Yeah.
C
I
don't
know
I
have
everything
is
running
on
one,
a
single
run.
All
of
the
all
of
the
commands
are
compressed
into
that
now
and.
C
Yeah,
I
that
was,
I
cut
out
three
gigs
by
switching
to
debbie
and
slim
yeah
like
I,
and
if,
if
people
want
to
tell
me
use
arch
or
something
or
alpine
or
whatever
the
small
one
is
please,
I.
C
A
The
reason
I'm
confused
is
like
I
did
some
tests
to
say
like
were
there
people
saying
like
on
fedora?
We
were
running
out
of
memory,
so
I
spun
up
a
virtual
machine
and
I'm
just
looking
at
it
and
the
virtual
machine.
I
only
gave
the
machine
30
gig,
of
memory
total,
and
it
tells
me
that
the
like
that's
how
big
the
file
system
can
grow
to,
but
it
tells
me.
A
C
Yeah
I
mean
I
I'm
and
also
I'm
using
ninja,
which
I
don't
know
if
that
makes
it
bigger.
Maybe
that's
a
mistake.
This
would.
C
Yeah
yeah,
I
I
configured
it
with
ninja,
which
I
assumed
would
be
better.
Perhaps
that
is
significantly
bigger.
A
C
Yeah,
no,
I
appreciate
that.
I
also,
I
don't
think
I'm
I'm
doing
a
debug
build
as
well,
which
I
assume
is
what
I
should
do
for
dev.
Maybe
I'm
wrong.
C
A
C
I
think
I
think
that
makes
it
significantly
bigger
so
right
it.
B
Does
yeah.
C
A
C,
plus
plus,
that
is
right,
so
I
think
you
know
it'd
be
a
really
good
start
to
just
yeah
yeah.
If
we
turn
off
debug
and
now
match
it
now
fits
in
nicely.
That
would
still
be
a
really
good
starting
point
for
people
to
come
in,
and
you
know,
even
even
if
you're
doing
like
some,
you
know
some
small
change
to
add
code
coverage
or
whatever
yeah.
You
don't
need
that
and
it
would
be
helpful
to
just
say:
go.
C
Yeah,
so
I
mean
taking
off
debug,
I
think
should
actually
probably
make
it
work.
The
baby
should
have
thought
about
asking
someone
about
that,
but
yeah
I
I've
made
progress
like
it
works
like
it.
C
It
does
what
it
should
do
so,
if
that,
if
that
makes
it
starting
get
code
spaces
on
the
standard
image
which
the
other
thing
about
the
standard
image
is
that's
what's
available
publicly
right
now
there
are
like
they've
talked
about
other
sizes,
I've
used
other
sizes,
I
have
access
to
other
sizes,
but
like
it's
not
a
publicly
available
thing,
so
that's
coming,
but
like
it's,
not
something
and
I'd
prefer
to
just
like
go
with
whatever
is
available
publicly.
C
The
other
thing
is
this:
isn't
necessarily
just
for
code
spaces
like
you
you
can.
This
is
just
the
generic
dev
container
config
that
which
is
what
code
spaces
consumes
docker.
It
themselves
have
begun
adopting
it
as
well.
So
this
also
just
serves
as
a
dev
image
that
you
can
deploy
anywhere.
Basically,.
A
C
A
You
may
need
to
like,
because
of
what
I
guess,
yeah,
if
you
start
from
scratch
and
building
it,
then,
yes,
just
from
what
bradley
mentioned
is
that
deleting
things
doesn't
necessarily
help
but
yeah
if
you're
starting
from
a
fresh
docker
file,
that's
not
an
issue,
so
okay
yep,
that
is
good.
So
the
next
two
things
we
did
have
on
the
issue
was
a
technical,
deep
dive
on
documentation
and
then
the
growing
and
maintain
the
level
of
contribution
in
the
future
in
the
future.
A
We'd.
Also,
last
time
we
talked
about
the
different
technical
areas
like
how
we
should
move
forward.
We
agreed
on
so
maybe
I
was
just
hoping.
Actually,
we
could
spend
a
little
bit
of
time
on
the
summit
just
in
terms
of
thinking
of
planning
and
stuff.
So
let
me
find
out
find
the
minutes
from
last
time.
A
C
A
A
C
November
25th,
I
I
would
say
if
you
could
do
earlier
than
the
18th
I
would,
but
if
the
that
is
the
latest,
I
would
do
it.
Okay.
A
C
D
Up
yeah,
it
was
4
p.m,
the
french
time,
so
I
think
it
was
10
to
2
for
you,
yep.
C
A
Speak
out
of
google,
actually
here
I'm
going
to
add
the
same.
I
think
there's
any
reason
to
use
a
different
zoom.
Is
there
no
way.
C
A
A
Okay,
so
that's
good,
so
plant,
okay,
pipe,
sorry,
okay,
targets
november
18th,
10
2
est
eastern
time,
I
guess
in
terms
of
sort
of
fyi
to
people.
A
You
know
I
guess
we
will.
I
can
put
on
the
tse
agenda.
A
We
all
make
sure
we
tell
people
that
we
could
post
on
the
collaborators
discussion
just
to
bring
your
facebooks
in
right,
so
that,
like
create
a
new
discussion
that
says
hey
this
is
happening.
Is
that
right.
C
A
C
C
A
A
A
A
A
A
A
C
A
A
If
not,
okay,
so
the
other
two
things
we
did
have
on
the
agenda,
although
we
kind
of
agreed
we'd,
like
you
know,
mini
summits,
maybe
the
better
way
to
get
the
deep
dives,
we
did
start
to
talk
last
time
in
terms
of
documentation.
A
A
C
A
A
Not
okay,
I
think
the
next
one
is
maybe
we're
spending
a
little
bit
of
time.
Just
discussing
we've
got
the
we've
got
some
of
the
technical
things
covered
under
the
mini
summit
planning.
This
one
is
like
a
deep
dive
on
maintaining
growing
level
of
contribution.
I
don't
think
we
can
necessarily
cover
the
deep
dive,
but
it
might
be
worth
spending
a
little
bit
of
time
like
we
did
on
docs
in
terms
of.
Are
there
some
some
things
we
should
be
thinking
about?
In
terms
of
that
we've?
A
You
know,
the
pre-built
binaries
is
already
one
of
those
things.
A
C
C
C
Not
nothing
tell
me
otherwise
like
go
ahead,
no,
not
in
core,
like
in
other
places.
You
can
like
node
core
utils,
even
or
you
know,
website
or
whatever,
like
the
the
not-
and
this
is
this,
isn't
just
a
nope
thing
like
every
every
major
project
has
this
kubernetes?
Has
this
electron?
Has
this
core?
The
core
thing
is
your
core
person
or
like
there's,
nothing
easy
left
to
do
and
that's
just
how
it
ends
up
working.
A
Right,
so
actually
we
think
this
this
there's
kind
of
like
two
two
types
of
contributions.
If
we
patients
here,
maybe
I
don't
know
if
it
makes
sense
for
me
to
share
the
everybody's,
probably
in
the
minute.
So
maybe
that's.
Okay,
like
I'm,
I
there's
kind
of
like
helping
to
keep
things
like.
There's
there's
the
fixing
scratching
say
scratching,
watching
an
itch
flash,
solving,
no
problem
and
then
there's
like
longer
term.
A
Moving
bringing
the
platform
forward
is
because
I'm
just
thinking
like
if
we
think
about
it
like
there's,
hey
I've
got
a
problem.
Can
I
fix
it
for
myself
right
and
that
helps
everybody
right?
Like
hey,
I'm
reading
the
docs,
oh,
the
docs
were
confusing.
I
can
fix
that
or
I
ran
into
this
technical
problem.
C
Sorry
go
ahead,
I
was
gonna
say
like
even
even
in
the
I
can
fix
that
in
docks,
docks
are
kind
of
impenetrable,
like
you
have
to
get
core
set
up
and,
like
that's,
that's
a
very
high
barrier
to
making
a
docks
change,
and
so
there's
even
there's.
Even
things
like
that
of
like
challenges
in
in
the
project
that
we
could
do
to
reduce
the
barrier
to
drive-by
contributions.
A
C
Kind
of
you
still
have
to
run
like
make
tests
and
stuff
which
isn't
really
like,
if
I'm
just
a
javascript
developer,
trying
to
do
a
javascript
thing,
and
I
find
a
javascript
bug
in
javascript,
docs,
spinning
up
a
container
and
spinning
up
a
container
and
like
having
to
run
make
tests
is,
is
still
a
higher
barrier
like
it
is
a
higher
barrier
than
is
necessary.
I
think
is
what
I'd
say.
A
A
C
A
I'm
just
thinking
like
the
different
kinds
of
problems,
because,
like
yeah
yeah,
it's
the
and
what
makes
sense
in
terms
of
like
bringing
you
know,
value
and
also
addressing
what
people
want
to
get
out
of
it
right
like
if,
if
it's
strictly
hey,
I
want
to
report
a
doc
issue
and
we
had
an
easy
way
to
report
those
and
then
somebody
else
could
actually
go
and
apply.
Those
and.
C
I
think
it's
one
of
the
things
in
that
is
that,
like
there
there's
some
like
business
stuff
around
this,
but
like
you're
kind
of
adding
a
lot
of
barriers
to
like
the
person,
probably
know
if
they're,
if
they
recognize
it's
a
problem,
they
probably
recognize
how
to
fix
it.
If
it's
a
javascript
problem
or
they
there's
like
a
decently
good
chance
and
getting
them
to
do
that,
and
lowering
every
single
barrier
possible
is
the
ideal
situation.
Because
then
you
get
them
to
kind
of
get
involved
and
do
the
work
sure.
A
A
B
C
I
don't
know
I
mean
it's
there,
like
the
the
the
with
with
anything
in
the
space.
You
can
always
make
it
easier,
and
it's
at
what
point?
Is
it
good
enough?
Like
you,
you
could
split
it.
You
could
split
out
docs
into
like
a
node.js,
slash,
docs
or
documentation
and
then
automatically
pull
that
into
core
and
just
have
them
like.
Have
work
on
docs
be
done
there
or
I
guess
split
it
between
the
two
depending
on.
If
we
don't
want
to
change
core
workflows.
C
Yeah
and
then,
like
you,
basically
make
it
so
you
can
just
like
run,
npm
run
test
or
whatever
yarn
test
in
that
docs,
repo
and
it'll.
Do
it
it'll,
take
care
of
everything
for
you
and
like
you,
could
even
go
to
the
path
of
like
installing
make
or
whatever,
like
I
don't
know,
getting
everything
set
up.
C
I
would
say
yes
because,
like
I'm
not
gonna
lie
the
average
javascript
developer
is
not
familiar
with
make,
and
it's
a
big
scary
thing
that
is
like
a
linux
linux
thing
that
I
I've
heard
that
often
so
yes,
but
I
mean
like
also
like,
I
don't
even
know
if
I
have
make
type
of
a
situation
like
when
I
was
when
I
used
to
be
contributing,
I
didn't
really
know
what
make
was
or
how
to
get
it
or
if
I
had
it,
which
I
think
you
have
it
by
default
in
any
linux,
almost
any
linux.
C
But
like
I
don't
know
what
dash
c
means
and
like
stuff
like
that,
so
there
it's
just
it's
it's
small
barriers
that
add
up
to
preventing
people
from
contributing,
which
is
that's
fine
like
if
it's
a
trade-off
right
and
there
will
always
be
some
trade-offs.
A
Yeah
yeah
and
then
I
so
just
thinking
like
it's,
you
got
the
two
types
you
got
the
scratching
the
itch
solving
the
personal
problem
and
then
moving
the
platform
forward
and
getting
contributors
on
that.
Second,
one
is
probably
even
like
one
is
about:
maybe
lowering
the
you
know,
making
it
easier
for
people
to
do
something
once
the
other
one
is
like.
How
do
we
attract
people
to
continually
and
contribute
over
time
right.
A
And
that's
one
where
we
should
probably
that's-
that's
probably
more
of
a
deep
dive
on
its
own
too,
but
are
people
other
people
have
thoughts
who
are
here
in
terms
of.
A
A
D
C
C
I
think
it
was
cnc
cpc
stuff
having
context
and
like
having
tsc
members
being
available
to
go
and
talk
to
people
or
talk
to
people
in
in
leadership
and
companies,
and
you
know
those
who
are
in
companies
already
who
are
enabling
them
having
you
know,
leveraging
those
relationships,
it's
it's
all
just
social
and
networking
stuff
that
has
to
be
done
to
at
this
point
how
node
works.
I
think
that's
how
you
have
to
do
it.
A
C
And
I
I
think
we
also
almost
all
have
avenues
to
that
to
some
extent
right
like
I
I
can.
I
can
reach
out
to
people
like
I
I
I
know
people
in
you
know
my
role
that
I
can
re
ask
to
connect
me
and
I'm
sure
someone
at
red
hat
in
in
y'all's
group
could
do
the
same
same
with
ibm
same
with.
You
know,
github
and
google
and
the
rest.
C
A
C
I
I've
seen
it
be
successful
with
a
number
of
companies
it
being
hands-on.
I
mean
the
the
other
thing
is
to
companies
seem
to
care
more
about
their
investment
in
electron
than
they
do
in
their
investment
in
node.
I
assume,
because
it's
a
fundamental
thing
and
they
need
apis
out
of
it
and
they
have
like
an
invested
interest
in
like
I.
I
need
this
from
you.
C
How
do
I
get
it
from
you
and
the
answer
is
make
it,
and
so
that's
that
that
makes
an
easy
discussion
that
includes
business
value
of
like
you
know,
we
want
dark
mode.
Okay,
go
make
dark
mode
in
electron.
C
C
Yeah,
but
it's
like
it
is
electron,
is
the
product
right,
like
you
know,
slack
is
electron
like
you
can't
have
the
desktop
app
without
electron,
and
so
you.
C
I
think
it's
less
the
functionality
that
we
need
and
more
the
ecosystem
is
papered
over
all
of
the
bad
parts
enough
that
they
don't
care
to
invest
in
making
the
bad
parts
good.
A
C
A
It
it's
related,
though,
right,
like
they're,
not
pain,
points
that
are
painful
enough
for
people
who
would
want
to
invest.
I
guess
is
that
yeah
right
there
that
yeah
they're
obviously
pain
points,
but
it's
like
it's
not
painful
enough
that,
like
so,
for
example,
in
the
other
case,
it's
like
it's
painful.
We
don't
have
dark
mode,
we
don't
look
good
compared
to
our
competitors
or
something
right
like
versus
like
yeah.
This
is
this
is
makes
me
grumpy,
but
you
know
I'm
not,
I'm
not
grumpy
enough
to
do
something
right.
A
I
think
it
would
be.
You
know
if
you
mentioned,
if
we
could
get
you
know
jacob
or
whoever
from
the
electron
team,
to
give
us
some
insight
into
what
that
team's
done
and
on
that
front,
and
what
was
successful,
I'd
be
interested
in
hearing
that
anyway.
A
See
joe
joe
nodding
at
least
paris
got
thumbs
up,
john
okay,
so
yeah,
if
you
could
set
that
up,
that
might
be
an
interesting
sort
of
next
step
because
it's
like
my
take
is
like
in
terms
of
getting
moving
the
getting
people
to
contribute
to
move
the
platform
forward.
I
guess
our
question
would
be
like.
Is
it
that
challenge
that's
bigger
or
the
technical
things
that
holds
people
back
like
the
getting
support
to
do?
A
A
Okay,
so
I
think
that's
a
good
next
step
anyway,
if
you
can
see
if
jacob
has
any
interest,
we
could
do
that.