►
From YouTube: 2021-01-06-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
january
6
2021.
We
will
follow
the
agenda
that
we
have
tagged
in
our
the
repo.
That
is
issue
number
38.,
and
we
have
the
first
thing
on
our.
I
guess
before
we
get
started,
does
anybody
have
any
announcements
that
they'd
like
to
share.
A
A
Okay,
so
the
first
thing
on
our
agenda
was
the
needs
and
wants
of
constituencies-
that's
number
20.
before
the
the
holiday
season.
We
had
a
couple
of
brainstorming
sessions
where
we
worked
on
that
and
I'll
paste
it
in
the
chat.
But
we
put
together
this
pr,
which
includes
the
the
the
outcome
of
that,
and
I
thought
we'd
just
spend
a
few
minutes
talking
about
that.
A
Yep,
okay,
that's
good!
So
if
we
look
at
what's
in
there,
I
can
bring
it
up
and
share
it.
A
A
A
A
Understanding
the
work
happening
in
the
node.js
project
features.
Do
I
have
to
look
forward
to
roadmap
changes,
confidence
to
help
the
project
upkeep
leadership.
Confidence
in
the
project
does
well
run
and
will
continue
to
be
maintained.
Successful.
B
A
A
A
So
how
does
that
look?
How
did
I
not
change
that.
A
B
So
we
we
did
have
a
request
to
start
an
rfc
process
land
on
node's
core
as
an
issue
which
kind
of
covers
a
similar
thing
to
this.
So
maybe
we
could
work
on
this
a
little
more.
B
So
one
of
the
big
things
that's
being
discussed
is
being
at
the
table
when
big
decisions
are
being
made.
B
A
semi-consistent
comment
I
see,
is
people
just
want
to
create
pr's
kind
of
because
they
have
lower
visibility,
and
so
it's
not
just
a
seat
at
the
table
when
decisions
are
being
made,
but
we
need
to
actually
help
people
find
what
decisions
are
being
made,
because
some
people
are
actively
myself
included
in
the
past,
have
tried
to
make
prs
because
they
were
lower
noise
than
starting
long
discussion
and
reaching
consensus.
That
way.
B
So
this
is
under
ability
to
affect
the
decision,
so
yeah
I'll
see
to
the
table
when
big
decisions
are
being
made
and
knowing
what
decisions
are
being
made
is
what
I
want
to
add.
Somehow.
A
C
I
think
it's
more
about
the
process
overall
right,
a
process
to
to
surface
big
decisions
and
allow
you
know
access
to
those
decisions
of
sorts.
A
D
A
D
I
think
we
have
a
lot
more
level
levers
now
to
be
able
to
do
that,
and
my
hope
is
that
we'll
be
able
to
do
that
much
more
easily.
Now,
with
how
the
foundation
and
our
control
over
our
own
stuff
is
designed.
B
A
B
B
C
One
comment
I
have
about
the
wording
here
is
that
it's
making
it
so
that
that
the
the
the
onus
is
on
the
person,
as
opposed
to
the
project
like
I
wonder
if
this
could
be
worded
in
a
way.
C
More
responsible
to
make
these
decisions
public
or
you
know
I
don't
know
how
to
phrase
it
exactly,
but
I
feel
like
it
should
be
flipped
a
little
bit.
B
Do
does
that
mean
we
need
to
include
notification
in
this
of
some
kind,
because
if
we
have
like
blog
posts
or
something
about
upcoming
things
in
the
next,
I
don't
know,
however
many
months
that
goes
a
little
bit
different
from
how
we've
done
with
prs,
but
it
seems
reasonable
for
important
decisions,
since
they
are
generally
only
released
on
the
lts
schedule.
D
So
I
I
think
part
of
that
part
of
putting
in
the
work
though,
or
like
for
the
for
at
least
folks
in
this
position
is
like
lowering
the
barrier
to
getting
them
to
put
in
the
work
is
having
having
them
know
and
having
them
have
access
to
it
and
like
for,
for
you
know
us,
that's
probably
less
of
a
problem,
because
we
spend
a
lot
of
time
in
node
and
are
invested
in
specific
things,
but
other
people
might
not
be,
and
so
this
is
a
way
to
get
them
to
either
to
the
point
where
we
are
or
to
like,
be
able
to
strategically
invest
their
time
in
the
things
that
they
care
about.
D
A
I'm
just
trying
to
find
the
right
balance
like.
I
totally
agree
that
we
we
can
do
more
and
improve
improve
on
that.
I
just
think
that,
like
there's,
a
difference
between
saying
hey,
like
the
suggestion
already
was
like
hey
we're
just
going
to
tag
the
issue
that
still
requires
somebody
to
go
and
query
those
tags
and
find
them
versus
hey.
I
just
want
to
add
myself
to
a
mailing
list
and
be
told
right.
C
You
might
be
able
to
do
it
in
your
own,
like
mailbox
rules
or
something
I'm
kind
of
thinking
about
this.
Coming
from
the
idea
of
a
potential
for
an
rfc
process-
and
you
know
maybe
that's
beyond
the
scope
here
but
like
if
there
were
something
that
were
more
of
a
big
decision.
Could
it
be
put
on
the
blog.
You
know
not
like
it
needs
to
be
elaborated
on
in
the
space.
E
A
A
B
A
D
D
A
B
B
E
Should
we
also
add
to
have
some-
let's
say
working
example,
and
not
just
and
not
just
one
function,
but
I
think
tierney,
I'm
sorry
for
the
pronunciation.
No,
you
gotta.
E
Okay,
great
you,
you
were
doing
some
stuff
on
the
example
repo.
B
B
E
Let's
say
an
easy
step
in
for
people
to
use
node
in
different
use
cases
and
not
just
doing
or
just
actually
asking
them
to
go
to
to
read
the
pure
documentation.
Even
if
it's
great
sometime,
it
could
be
great
to
to
show
how
to
implement
node.js
with
a
lambda
or
I
don't
know
which
services,
but
something
like
that.
A
E
E
Maybe
not
sure
the
api
but
concrete
concrete
use
case
so
use
cases
for
the
apis
yeah.
A
I
guess
that's
like
that
sounds
a
bit
different
to
me
than
like
code
samples
or
I'm
just
trying
to
think
like
what
would
it
look
like
not
that
we
should
specify
the
the
solution,
but
I
kind
of
understand
the
hey.
I
want
to
use
this
api
some
code.
That
shows
me
how
use
cases
makes
me
think
like
well.
Why
would
I
want
to
use
this,
and
where
would
I
want
to
use
it's
like?
Well,
if
I
don't
know
that
I
need
to
use
it
maybe
like.
Is
that
really
a
need.
B
B
B
A
D
D
All
right
that
gets
into
a
value
judgment,
that's
rough
like
if
you
choose
most
important
like
I
don't
know
for
like
streams
or
something
it's
gonna,
be
like
there's
a
lot
of
reasons
you
do
streams
and
which
one
is
the
most
important
ends
up
being
a
value
judgment,
that's
hard
to
like
choose.
A
C
All
right
no
go
ahead.
Tony
really
quickly,
though,
actually
roy
is
waiting.
A
C
D
I
I
end
up
in
the
no
doc
slot
when
I'm
doing
like
weird
things
that
I
don't
do
often
and
there's
usually
like
a
sync
method
and
async
method,
and
then,
like
often
for
that
weird
stuff,
there's
like
two
different
things
that
are
close
enough
together
that
are
like,
I
don't
know
which
one
of
these
I
need
to
choose,
and
it
turns
out
only
one
of
them
is
correct
and
so
like.
D
That
is
a
thing
that
maybe
you
know
this
would
solve
is
like
having
the
co
having
code
is
good,
but
also
having
some
pros
around
that
code
of
like
explaining
what
the
code
is
doing
or
why
it's
doing
it
or
like
having
like
language
around
that,
just
like
a
paragraph
or
something
for
that
code,
sample
would
potentially
help.
You
know
address
that
if
that
makes
sense.
D
Oh
yeah
right
and
I
guess
my
the
reason
I'm
saying
it
is
because
you
were
asking
like
because
of
the
question
you're
asking
around
like
what
is
the
like.
Is
this
a
needed
thing
like?
I
think
the
implementation
does
end
up
mattering
in
in
that
of
like
what
problem
does
this
solve?
Well,
the
implementation
kind
of
helps
answer
that
a
little
bit.
A
E
B
A
A
A
B
A
A
Okay,
next
one
innovation
is
at
as,
as
at
a
consumable.
A
A
A
B
A
A
A
A
A
A
B
B
A
I
think
that
could
kind
of
come
under
the
easy
installation
as
like
in
terms
of
consuming
in
the
different
environments.
If
you
want
to
consume
multiple,
I
could
see
that
being
a
subset
of
that
so
easy
issue,
reporting
resolution
and
collaboration,
a
good
path
to
report
issues
to
the
project.
The
ability
to
collaborate
contribute
to
the
project
to
get
them
addressed
a
clear
understanding
of
how
to
interact
with
the
node.js
project.
A
A
Yeah,
that's
probably
a
good
idea:
okay,
I'll
just
gonna,
add
that
comment
and
we
can
move
on
many
other
comments
on
that
one.
E
D
Hold
on
sorry,
I
was
muted,
my
bad.
The
the
bullet
under
desktop
platform
support.
This
is
absolutely
init,
but
it
should
have
a
space
after
os
and
windows,
windows
and
linux
should
be
capitalized,
and
then
it
should
be
mac
os,
since
os
x
is
not
the
branding
anymore.
A
D
A
B
A
D
E
A
A
B
Because
are
we
talking
about
more
diagnostic
signals
coming
from
core
or
the
ability
to
have
users
add
diagnostic
signals
that
could
be.
A
A
A
A
Relevant
api
is
in
core,
so
I
think
we
should
take
it
one.
Two
three.
A
B
B
I
think
you
need
to
clarify
what
part
of
intermediary
dependencies
you're
trying
to
solve
for
is
it
usability
security,
etc?.
B
Well,
it's
about
the
apis
being
some
form
of
usability,
I'm
not
sure
what.
A
A
A
B
A
Any
other
comments:
no
the
next
one
is
ways
to
fund
their
work.
B
Funding
providing
a
payment
method
or
it
could
be
explaining
ways
that
you
can
get
funding
other
things.
A
A
B
B
B
A
A
A
B
B
A
A
D
I
also
think
the
word
throughput
is
limiting
to
a
specific
set
of
use
case.
I
could
be
wrong
in
this,
but
it's
potentially
limited
to
a
specific
set
of
use
cases
of
node
that
are
not
all-encompassing.
D
Well,
but
like
I,
I
think
performance
would
be
like
there
there
is.
It
will
be
performance
for
that
target
right,
like
if
you're
running
something
on
a
raspberry
pi.
You
want
that
it
to
be
like
you
know,
you're
running
on
our
raspberry
pi,
and
you
want
it
to
be
performed
there
not
like
on
optimize.
I'm
not
arguing
for
I
don't
know
why
I'm
defending
it,
but
like
the
other.
A
Thing
is,
this
is
not
like
these
are
not
necessary
for
everybody
right,
I
think
like.
If
we
went
back
to,
let
me
cancel
out
of
that
for
a
second.
A
A
B
A
A
A
B
The
one
thing
we
don't
have
is
a
scope
or
model
for
what
security
means
for
node.
I
think
that's
separate.
B
B
A
B
Collaborators,
I
think
supportive
collaborators
might
be
a
difficult
topic,
because
that
implies
in
general,
you
always
support
and
there's
necessary
tension
where
people
will
have
conflicting
ideas.
D
A
Okay,
so
I
I
yeah,
I
do
have
a
hard
stop,
so
I'm
gonna
have
to
drop
off,
but
if
people
could,
maybe
you
know,
look
at
the
last
two
comment
on
comment
on
those
there's
a
few
other
things
that
I
know
people
are
going
to
go
and
comment
on.
A
A
So
thanks
for
everybody's
time
and
we'll
talk
to
you
through
github,
hopefully
to
sort
of
close
on
this
and
in
a
couple
weeks
thanks.
Bye
thanks,
bye.