►
From YouTube: Node.js Technical Steering Committee meeting
Description
A
B
A
A
So
Nikita
put
this
on
the
agenda.
I
took
a
look
at
it.
It
looks
like
we
just
need
somebody
to
edit
what's
written
and
maybe
think
about
it
from
in
terms
of
if
it's
complete
or
not
and
figure
out
where
to
post
it,
and
unless
somebody
has
already
volunteered
to
do
that
in
the
issue,
I'll
volunteer
to
try
to
get
that
done
this
week.
I.
A
C
B
Okay
and
everybody
else,
of
course,
is
welcome
to
help
out
with
poor
requests
and
revenues
on
that
issue,
then
the
next
one
is
also
about
the
buffer,
constructor
runtime
deprecation.
It's
the
tracking
issue,
number
one:
nine
zero,
seven,
nine
from
what
I've
seen
there
were
no
updates
or
changes
since
the
last
week.
A
Yeah
I'm
sorry,
I
I,
don't
see
where
the
raising
hand
thing
is
in
the
interface.
Maybe
it's
because
I'm
an
owner
and
sure
anyway,
yeah
there's
I,
don't
think
there's
anything
to
do
on
that.
One
on
the
one
to
put
that
on
the
agenda
and
I
think
this
document
that
from
the
previous
issue,
is
really
the
next
most
important
thing
to
do
there
so
I
think
we
can,
unless
anybody
has
strong
opinions
about
it.
We
can
move
on
to
the
next
item.
D
D
Though,
if
there's
anything
that
we
may
have
those
of
us
who
don't
follow
the
usual
trackers
close,
be
those
may
have
missed
with
regard
to
fallout
from
version
10
more
and
the
buffered
application
other
than
be,
and
there's
the
typescript
TS
no
problem,
then
I
think
was
fixed
really
quickly.
Is
there
anything
else
that
came
up
through
the
issue
tracker
that.
B
Yeah
no
major
problems,
yet
if
you're
listening
and
you
have
major
problems-
please
let
us
know
so
we
can
try
to
fix
it.
Okay,
then,
the
next
issue:
let's
move
on
to
the
TSC
issues,
there's
a
tracking
issue
for
the
board.
Four
seven
six
I
believe
there
are
no
updates,
because
mine
is
not
here
and
then
the
other
tracking
issue
is
for
our
strategic
initiatives.
B
B
D
Other
than
I
just
have
at
the
time
to
update
that
doc,
but
open
SSL
one
one
one
is
up
to
pre-six
and
it's
still
on
track
to
be
formally
released,
mid-may
sort
of
things,
the
fifteenth
and
so
that
we
have
some
time
in
to
think
about
the
implications
of
integration.
What
we
might
expose
with
the
new
API
stuff,
TLS,
1.3
and
because
there's
some
build
concerns
some
compiler
concerns
with
it.
We
may
not
be
jumping
on
that
super
quick.
We
have
to
be
careful,
so
that's
all,
then.
D
B
E
So,
for
instance,
in
the
diagnostic
working
group,
we've
been
trying
to
figure
out
what
would
be
what
would
be
needed
to
move
a
thing
cooks
out
of
experimental
and
one
of
the
main
things
we're
focusing
on
right
now
is
performance,
so
there's
a
new
proposal
by
the
by
the
VA
team
on
improving
from
whis
hooks
performance.
That's
Diagnostics
issue,
one
eighty,
eight
one,
eight
eight
that
would
introduce
some
potentially
breaking
changes
in
the
promise,
succeed,
yeah,
so
that's
currently
under
discussion
and
as
a
way
to
include
performance
of
ASA
codes.
B
C
A
B
E
Bridges,
so
at
this
point,
I
think
what's
needed.
Is
somebody
actually
doing
the
work
to
introduce
the
namespace
in
in
our
module,
loader
and
I?
Think
Deb
snake
was
we're
trying
to
work
on
it,
but
it
is
a
fairly
here,
a
fairly
hairy
amount
of
work,
so
I'm,
hoping
that's
the
main
blocker
here
I
think
generally,
people
seems
like
core
in
favor.
C
C
A
Makes
me
wonder
if
people
are
gonna
start
using
it,
even
though
it
emits
an
a
warning
when
they
use
it
and
how
much
stuff
are
we
gonna
break?
Thank
you.
Whoever
is
taking
notes
as
I
speak
and
so
how
much
stuff
are
we
gonna
break?
You
know
in
the
ecosystem.
If
we
change
it
and
you
know
like
I,
don't
know
where
I
guess,
I
guess
I
guess
we
should.
You
know,
call
me
kita
so.
C
A
A
D
B
C
Can
we,
if
we
keep
like,
we
don't
have
a
policy
around
this,
then
we
should
probably
make
the
decision
that
experimental
modules
could
have
their
majorities
changed
so
that,
like
maybe
in
the
future,
we
can
make
them
more
consistent,
even
though
right
now,
because
there
are
a
lot
there's
a
tons
of
work
to
do
to
actually
make
dining
space
happens,
so
that
could
take
a
while.
But
before
that
like,
we
should
make
clear
that
they
could
change
so
that
we
could
change
them
in
the
future.