►
From YouTube: 2020-01-21-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,
looking
at,
what's
going
to
make
help,
keep
note
say
successful
for
the
next
10
years.
We
forgot
to
start
the
streaming.
My
fault,
sorry
about
that.
What
we've
been
started
off
with
is
discussing
the
next
step
in
terms
of
the
constituencies
and
the
needs
that
we've
worked
on.
A
We
worked
on
that
last
week
in
between
then
and
now
we
landed
the
document
which
captures
that,
but
the
sort
of
closing
step
is
we
want
to
make
sure
that
we
validate
that
against
the
greater
community,
and
we've
been
talking
about
a
few
ways
that
we
can
do
that.
So
I'm
just
going
to
share
my
screen
here
and
we
were
looking
at
some
different
ideas.
A
B
A
C
A
Okay,
so
I
you
know
if
we
think
that's
good,
I
can
volunteer
to
reach
out
to
the
foundation
to
ask
for
that
kind
of
survey.
A
C
B
I
mean
another,
I
I
I
slightly
lost
the
threat
there
because
I
was
saying
we're
live
in.
B
We
could
even
have
a
separate
survey
for
like
the
mailing
list
and
for
you
know
putting
it
out
from
from
the
node
twitter
account
and
have
it
be
the
same
questions
but
just
gathered
the
different
responses
distinctly
to
make
sure
like
to
see
kind
of
where
the
differences
are
and
what
the
potential
biases.
B
Like
that,
okay.
C
A
A
Foundation,
member
responses
look
like
versus
overall
community
yeah,
that's
a
good
idea,
so
basically
that
email
might
just
be
here's
the
survey,
here's
a
survey,
but
it's
a
different
survey
link
and
you
know
so.
We
can
compare
that
those
responses
to
what
we
get
back
from
just
the
more
general
one.
A
B
The
deliverable
thing
there's
the
survey
I
mean
we
might
also
want.
I
I
don't
know
if
tweeting
like
hey
we're
like,
maybe
if
we
do
some
kind
of
intake
form
for
random
folks
that,
like
we
also
might
want
to
put
that
out,
but
also
that'll
get
a
lot
of
like
just
knowing
that
account.
Now
that'll
get
a
lot
of
a
lot
of
replies
and
it
might
be
too
much
for
us
to
manage
right.
B
Right
in
in
interaction
there
will
be
high
and
so
yeah
you
know
that's
fine.
We
can
do
like.
We
don't
have
to
look
through
all
of
them,
but
it
you
know,
I
I
think
that's
that's
a
good
problem
to
have
it's
just
maybe
challenging,
and
I
want
to
make
sure
we're
not
like
overselling
the
work
we
can
do.
A
C
A
Individual
interviews,
but
if
there
was
like
you
know
a
bunch
of
people
who
were
interested
in
coming
and
talking
through
that
for
an
hour,
I
think
that
would
actually
be
quite
interesting
right.
B
The
the
challenge
with
that
is
just
that
the
quality,
the
fidelity
of
the
feedback
you
end
up
getting
is
gonna,
be
a
lot
lower
and
then
it
also
does
introduce
like,
if
someone's
a
more
quiet
person-
and
you
know
another
person
that
is
a
loud
person
that
quiet
person
is
probably
not
going
to
talk
as
much
and
so.
B
Going
to
hear
from
them
as
much
so
I
mean
like,
I
would
also
be
willing
to
help
run
like
I'd.
Be
I'm
happy
to
sign
up
and
like
run
a
bunch
of
these
for
like
if
we
can
set
them
to
like
30
minutes
or
something
yeah.
A
A
B
B
It'd
probably
be
one-on-one
okay,
it
would
probably
wouldn't
be
like
a
bunch
of
people
and
it'd
be
just
like.
Basically,
we
have
a
set
of
questions
and
we
we
go
and
go
kind
of
in
depth
on
those
rather
than
right
breath.
So
and
again
that
would
be
up
to
whatever.
Whatever
questions
we
want
to
set
is
what
I'd
ask
right.
A
And
then
the
question
would-
and
I
think
you
know
it's
possibly
the
survey
questions
but
more.
You
know
it's,
because
it's
free
form
will
it's
much
easier
to
go
into.
You
know
to
start
with
those,
and
then
you
can
go
into
different
areas
right
to
so
sort
of
like
in
terms
of
scoping
like
how
many
do
you
think
you
can
do
and
how
would
we,
if
you
know
we
tweeted
that
out?
A
How
would
we
get
the
narrow
it
down,
or
is
it
that
you
know
you
have
several
people
in
mind
that
you
think
we
could
reach
out
to
or.
B
I
mean
yeah,
I
think
it
may
be
just
there's
a
few
ways.
You
could
do
it.
We
could
just
randomly
select
people
from
that
pool.
We
could
intentionally
select,
making
sure
we're
getting
as
wide
a
range
of
backgrounds
as
possible
and,
like
part
of
that,
intake
form
could
be
like
you
know,
give
a
like
give
us
context
on
your
background
and
stuff
so
yeah.
I
think
that
that
you
know
we
might
want
to
try
to
get
as
many
backgrounds
as
possible,
but
yeah.
A
A
Everybody
who's
interested
to
come
and
actually
talk
to
us
about
it
has
has
an
opportunity
and
then
follow
that
up
with
some
individual
sessions.
You
know
where
you
select
the
people
based
on
you
know
trying
to
get
the
good
coverage
of
of
the
different
areas
and
where
people
come
from
and
all
that
kind
of
stuff
without
having
them
have
them,
be
the
people
who
need
to
speak
up
in
the
larger
group,
mm-hmm
yeah,
that
makes
sense
yeah.
I
think
that's
fair,
okay,
so
in
terms
of
that
yeah,
so
you
know
intake
form.
A
A
A
A
A
B
Do
is
a
group
okay
like
lessons
ready
and
then
hand
them
over
to
rachel
to
right.
She
can
help
help
us
put
them
in
a
survey.
Monkey
thing
and.
A
B
At
least
for
I
would
say,
we
probably
don't
want
to
ask
the
individual
in
group
session
for
demographics
that
that's
like
a
relatively
well-defined
set,
that
we
can
probably
just
do
async,
and
then
I
I
guess
like.
Are
there
any
other
qualifying
questions
you'd
want
to
have
for
this,
or
are
you?
B
Are
we
just
interested
in
like
full
full
self
selection
like
if
someone
like
the
implication
that
if
someone
is
filling
up,
the
survey
they're
probably
going
to
be
interested
in
giving
feedback
anyway,
like
it's,
people,
aren't
just
randomly
filling
out
surveys
for
no
reason
about
topics,
so
perhaps
just
like
getting
demographic
information
and
then
moving
on
is
fine,
but
I
don't
know
if
we
have
any
other
qualifying
stuff
that
we
want
to
have
in
that.
A
B
Yeah,
well
I
mean
I,
I
guess
it
also.
I
don't
think
it's
bad
to
have
that
in
the
main
main
form
and
then
like
have
an
additional
option
of.
Would
you
like
us
to
reach
out
to
you
for
to
do
like
a
one-on-one
session,
or
would
you
be
interested
in
us
potentially
reaching
out
to
you
for
a
one-on-one
and
then
from
there
if
they
answer
yes,
cool,
we'll
we'll
we'll
add
that
we'll
we'll
filter
that
out
or
filter
out
everyone
who
says
no
and
then
select.
B
A
B
Socioeconomic
race,
geographic,
geographic,
that
kind
of
stuff
yeah,
so
I
I
can-
I
can
go,
find
like
an
official
list.
It's
not
just
me,
making
stuff
up.
Okay
sure
is
like
good
and
respected.
B
A
So
I
think,
using
reverse,
intercept
and
run
several
sessions
based
on
answers
to
right.
A
C
A
A
Okay,
so
I
think
that's
good
for
that
agenda
item
the
next
one,
there's
there's
a
number
which
is
the
key
technical
areas
next
10
for
years
and
revisit
time
slots.
So
I
guess
actually
the
revisit
time
slots
is
one
I
know
darcy.
I
think
you
put
out
a.
I
think.
C
A
A
The
same
thing
I
think
for
the
next
10
for
collaboration,
I
think
mary
was
was
going
to
hopefully
lead
that
one.
So
I'd
suggest
we
spend
the
rest
of
the
time
working
on
the
sort
of
starting-
and
I
know
this
will
be
a
longer
time,
but
like
the
process
of
generating
the
technical
areas
and
trends
that
we
think
are
important
to
the
constituencies
that
we've
identified.
A
C
Just
the
point
of
order,
it
looks
like
gene
is
looking
to
join
yup.
Sorry
yeah
thanks
for
the
heads.
A
A
C
A
C
Just
copy
paste,
what
were
the
we
can
change
the
columns.
I
guess,
but
I
create
a
board
again.
C
C
A
Yeah,
I'm
not
you
know
it's
technological,
it's
kind
of
technology
trends,
maybe
node.js
features.
A
C
Do
you
want
to
take
time
to
fill
this
out?
I
think
that
by
because
I've
cloned
it
by
default,
your
if
you
add
tickets
into
it,
they
won't
be
visible
by
default,
but
I
know
in
other
exercises
we
usually
give
folks
some
time.
A
C
C
B
B
B
B
B
A
A
I
guess
there's
two
other
columns
that
come
to
mind
that
might
have
been
useful,
which
is
like
ecosystem
and
the
node.js
project
like
in
terms
of
like.
If
we're
talking,
I
don't
know
how
they,
if
they're,
strictly
technology
things,
but
it's
kind
of
like
they
relate
to
things
that
are
strategic
in
terms
of
meeting
the
needs
of
the
constituencies,
because
those
are
just
some
categories.
I
have
had
a
few
ideas.
I
don't
know
how
to
fit
into
these
two
columns.
C
A
A
C
B
A
John,
you
done
two
john
sorry.
B
It
you
meet
a
darcy.
C
Great,
so,
if
we're
done,
I
can
show
the
cards
if
we're
all.
Okay
with
that.
What
I
think
we've
done
in
the
past
is
try
to
do
a
quick
pass
and
see
if
there's
any
overlapping
tickets
and
then
combine
them
and
then
go
through.
I
guess,
sort
of
a
voting
system.
I
think
everybody
has
like
six
votes
is
and
then
I
guess.
C
Yeah,
I
think
you
can
imagine
if
you
want
to
go
through
them.
If
we
see
anything
that
should
be
obviously
collapsed
into
one
card,
yeah.
B
C
B
Dynamically
typed
they're
also
having
typing,
so
that's
more
of
a
thing
that
I
think
is
just
becoming
an
industry
standard
or
norm
rather
than
specifically
typescript
yeah,
but
I
think
our
domain,
it
typescript
is
the
one
that
matters.
A
B
C
A
little
bit
interesting,
I
was
almost
like.
I
almost
put
jam
stack
and
or
like
I
imagine,
like
pre-compilation,
being
some
sort
of
maybe
automation
as
well.
But
do
you
mean
pre-compilation
in
a
different
way.
B
So
pre-compilation
I
mean
just
like
everything
from
like
web
back
type
script.
You
know
everything
that
it
requires
is
a
build
step
to
get
to
your
final
app
at
this
point
is
like
a
pre-compilation
thing
to
me,
and
that's
like
I,
I
think
you
know,
as
we
see
more
javascript
people
picking
up
like
rust
and
go.
That
is
like
a
normal
standard
as
well
or
normal
expectation.
B
So,
like
I
guess
that
that
was
more
of
what
I
was
getting
at
is
just
like
there
is.
There
is
the
trend
of
you
know.
People
are
trying
to
reduce
it,
but
we
are
inherently
living
in
a
world
where
we
transpile
everything
or
pre-compile
everything.
B
A
B
Yeah,
so
node
node
is
the
tool
that
they're
often
writing
that
that
stuff
in
so
right,
interesting,
yeah,
yeah.
A
Fit
together,
no
that
they
don't
actually
they're
different.
B
Is
is
boring,
ssl
or
alternative
ssl,
something
like
not
not
alternative,
as
it's
always
a
thing,
but
like
alternative
ssl,
tooling,
something
that
should
go
in
node.js
features
or
is
this
things
that
already
exist.
A
These
are
like
what
do
we
think
is
strategic
for
the
success
in
the
next
10
years
yeah.
So,
if
you
think
that
like
having
alternatives
is
strategic,
you
know
throw
it
in
there,
I'm
not
yeah.
I
know
I
don't
know
I
I
wouldn't.
I
wouldn't
necessarily
immediately
agree,
but
I
don't
necessarily
disagree
so
like
yeah,
it's
basically,
if
you
think
it
is
throw
it
in
there,
and
it's
worth
this
it's
worth
discussing
so.
C
So
I
know
we
had
like
the
binary
summit
yep
and
that
was
essentially
yeah
like
okay.
We
were
talking
a
lot
about
like
yeah,
yeah
installation.
I.
A
I
don't
know
if
we
want
to
like
go
through
the
like.
You
know,
people
could
could
mark
their
like
what
they
think
is
most
important
sure,
and
then
maybe
we
just
leave
it
at
that
and
next
time
we
pick
it
up,
and
we
might
you
know,
do
another
pass
of
this
just
to
see
if
we've
come
up
with
new
ideas
or
other
people
have
other
ideas
and
sure.
C
C
Yeah,
I
think
we
each
get
six
votes,
yeah.
A
C
C
Today,
you
can
also,
if
you
really
feel
strongly
about
something
that
you
think
is,
is
really
important.
You
can,
I
think,
double
up
and
yeah.
You.
A
B
C
B
Invested
somewhere
michael.
C
C
B
Three
four,
so
it
does
not
do
an
x
per
thing
it
does
like.
If
you
remove
one,
it
will
there's
two
votes
from
you
in
it.
There
will
still
be
an
x
there.
B
C
Definitely
have
more
than
six
because
the
little
prompt
at
the
top
tells
you
notification
tells
you
how
many
you
have
left
each
time.
So
if
you
click
to
vote
on
something
it'll
tell
you
how
many
you've
left.
B
What
up
today
es
version
javascript
support
and
yes,
I'm
at
the
same.
B
B
A
We
we
had
like,
basically,
we
had
it
built
in
a
way
that
supported
people
using
it
in
fips
environments
like
we
actually
had
to.
We
had
an
option
where
you
could
build
it
in
a
specific
way,
and
it
then
met
the
requirements,
because
you
couldn't.
A
Yeah,
so
it
may
actually
be
different.
Openssl
3
allows
sort
of
a
plug-in
approach,
so
it
may
be
that
you
know
we
don't
need
to
do
as
much
special,
but
it's
it's
basically
doing
what
we
we
can
in
within
node
to
enable
node
to
be
used
with
fips.
Basically,.
C
I
think
it
was
already
sorted,
so
that's,
unfortunately,
why
I
think,
if
you
I
maybe
it's
personally,
so
you
can,
if
you
click
on
it,
it
might
maybe.
C
A
B
A
A
B
B
B
I
think
that
would
be
really
interesting
to
maybe
like
clean
this
up
a
bit
like
you
know,
de-dupe
a
little
bit
and
publish
it
and
just
say
like
hey
we're
interested
in
this.
Maybe
I
have
an
issue
for
it
and
just
say
like
ask
the
whole
group:
does
anyone
want
to
add
anything
or
modify
this,
but
that
would
be
really
a
really
interesting
way
to
collect
feedback.
I
think.
A
C
Yeah
we
did
this.
We
did
that
for
npm
at
a
former
one
of
the
previous
interactive
collaboration,
subnets,
interesting,
yeah
and
yeah,
you
get
some
interesting
feedback.
Sometimes
you
get
some
not
not
being
as
serious
about
it.
A
I
think
we
should
make
a
separate
board,
like
I'd,
almost
be
tempted
to
say,
like
here's,
a
blank
word
and
you
know
have
this
is
like
anybody,
because
you
don't
necessarily
know
who
voted,
but
that
one
could
be
like
here's.
Just
the
the
anybody
came
and
gave
us
some
suggestions
and
then
that
could
be
used
as
input
to
the
group.
You
know
sort
of
refining
what
we've
got
here.
B
I
think
I
definitely
think
seeding
it.
A
bit
with
a
few
things
will
help
get
other
people
engaging
in
it
just
like,
even
if
it's
like
you
know,
basic
things
like
documentation,
esm
worker
threads,
you
know
and
then
like
similar
on
the
other
side
like
graphql.
A
B
A
C
Yeah,
do
you
want
to
create
maybe
an
issue
just
so
we
can
coordinate
async
and
I
can
definitely
set
up
another
board
or.
B
A
B
A
B
A
Head
out
but
yeah:
let's
do
that
async
I
can
I'll
when
I
read
it,
the
minutes
I'll
create
an
issue
and
I'm
gonna
add
a
link
to
this
fun
retro
and
then
that
that
will
do
that.
We
can
do
that
async
because
that's
yeah,
that's
a
good
idea.