►
Description
A
Technical
committee
meeting
for
September
14
2016,
if
I'm
not
mistaken,
this
is
the
one
year
anniversary
of
the
merger
of
I,
ojs
and
nodejs.
So
if
you
see
someone
who
worked
on
works
or
worked
on
either
or
both
of
those
projects
give
them
a
high
five
today,
let's
start
with
stand
up
and
first
would
be
Bradley.
B
Not
too
much
going
on
synced
up
with
various
people
about
trying
to
understand
what
the
difference
is
between
the
two
module
systems
for
ES
modules
are
got.
A
couple
of
proposals
to
review
from
Chris
Dickinson
and
Jeremiah
has
one
out
on
the
EP
other
than
that
not
too
much
going
on
yep.
C
A
C
F
I've
been
working
on
the
v6
point,
6.0
release
and
that
should
be
of
today,
but
I'm
having
some
running
into
some
stuff
on
sit.
Jum
and
I.
Wasn't
a
hundred
percent
sure
that
everything
it
went
into
it
would
necessarily
pass
it
or
I
saw
some
stuff
that
looked
like
it?
Maybe
I,
don't
know,
looked
a
little
bit
suspicious
as
to
to
like
could
maybe
cause
issues.
F
G
So
a
little
bit
with
the
Diagnostics
working
group
trying
to
get
together
a
meeting
for
next
week,
but
with
the
interactive
this
week
haven't
gotten
much
reply
there,
so
I
might
have
to
bump
it,
and
then
this
general
issues
and
PRS
and
a
couple
places
and
was
on
discussing
modules
a
little
bit
with
with
Bradley
and
couple
other
people.
Next
is.
H
Julian
I've
been
reviewing
a
couple
of
timers
PR
from
Jeremiah
and
investigating
and
fixing
a
few
leap
UV
bugs
on
our
OS
and
I
also
write
the
async
hooks
EP
from
Trevor.
Next
is
Brian.
I
Okay,
so
I
mostly
been
taking
another
stab
at
the
JavaScript
DNS
a
client
and
trying
to
get
see
if
I
can
take
different
avenues
for
trying
to
get
performance
to
be
close
to
see
Aires
in
the
system,
resolver
and
I
think
I'm
getting
pretty
close
now
with
a
few
optimizations,
but
still
not
quite
there
other
than
that.
Just
the
normal
reviewing
PRS
and
issues
next
is
rod.
D
J
Hey
guys
just
working
on
finishing
up
the
v8
inspector
migration,
it's
now
in
the
v8
tree
and
it
builds
and
so
we're
almost
ready
to
declare
that
migration
done
and
there's
some
continued
discussion
on
the
micro
task
queue
introspection
api's
on
the
v8
side,
on
on
the
on
the
tracker,
I've
listed
the
issue
in
the
dock
and
so
I
think
things
are
you
gonna
want?
Well
there
that's
off
me.
Next
up
is
Trevor
NARS.
G
G
J
K
Right
finish,
the
finish:
the
east:
well,
wasn't
one
percent
complete,
but
it
was
really
close
to
one
hundred
percent
completion
to
follow
the
EP
as
it
was,
and
X
marking
showed
that
it
was
slaughtering
performance
even
if
they
weren't
being
used
and
so
I
cut
scope
and
about
daily
p.
I'd
been
all
this
history.
I
cuts
go
up
a
DP
and
then
also
updated
the
pr
I--
left
victim.
It
separates
sake
and
see
what
it
was
and
what
it
is
and
what
it
is
now
so
that
it
won't
hinder
performance.
K
K
Next
tick
we
use
it
all
over
the
place,
I
mean
if
you
look
at
the
PR,
show
an
icing
stack
just
receiving
and
responding
to
a
single
HTTP
requests
as
another
eight
or
ten
next
hit
calls
and
each
of
those,
even
if
they're
not
being
tracked,
Bay
still
going
to
receive
new
IDs,
just
those
minor
little
calls
or
add
up
really
fast,
especially
when
you're
trying
to
do
a
35,000,
or
course
per
second
but
yeah.
It's
outfits
/
view
it
can
be
used
and
tested.
A
A
D
K
Were
to
enable
a
hook
and
then
run
a
new
synchronous
operation
and
then
disable
the
hook.
The
hooks
any
synchronous
operations
that
occurred
within
the
time
it
was
enabled
and
disabled
are
are
the
hooks
are
propagated
along
those
a
synchronous
calls,
and
so,
even
after
the
hook
has
been
disabled,
two
callbacks
will
continue
to
be
called
this
way.
You
could
be
selective
about
what
was
being
listened
to,
and
that
feature
it
just
it
was
okay,
I
feel
like
I
could
have
managed
it,
but
honestly
the
biggest
hindrance
is
next
type.
I
feel
like
that.
K
K
A
Commits
but
what
was
I
oh
yeah,
I
I
mean
yeah
I
started
to
leave
like
you
know,
punctuation,
nits
and
stuff,
and
then
I
stopped
myself,
realizing
that
we,
you
know,
we
really
just
need
to
vote
on
the
content
and
not
anyway,.
F
A
F
K
By
cutting,
but
by
cutting
the
features,
and
by
doing
some
code
make
link,
I
was
able
to
it
still
has
about
a
two
percent
overhead,
even
if
the
hooks
are
not
being
used,
but
that's
a
lot
better
than
the
fourteen
percent
was
back
when
it
still
had
to
do
like
state
probation.
So
it's
still
not
where
I
want
it
to
be,
but
it's
it's
close
enough
where
99%
of
users
wouldn't
notice
a
difference.
A
A
Ray
hooray:
okay,
so
if
I'm
doing
the
math
correctly,
we
have
seven
votes
in
favor
and
one
abstention
which
again,
if
I'm
doing
the
math
correctly,
we
need
two
more
two
more
votes
in
favor.
If
this
is
to
pass
or
a
whole
bunch
of
abstentions,
so
I
guess
the
only
resolution
is
to
put
this
information
in
the
EP
poll
request
and
at
mention
nodejs
CTC,
to
try
to
solicit
more
votes
from
people,
both
yes,
votes,
no
votes
or
abstentions.
So.
A
D
Note
as
well
that
in
the
in
the
side,
panel
I
dropped
a
link
to
the
pull
request,
which
is
pull
request,
5853
one
which
goes
along
with
this,
the
EP.
It's
not
we're
not
voting
on
that
bill
request,
but
the
if
you
want
to
start
looking
at
the
code
for
the
implementation
been,
and
we
should
look
that
at
least
number
eight
531
awesome.
Thank.
A
You
right
for
taking
the
action
item
of
putting
the
information
in
the
pull
request.
So
unless
somebody
has
an
absolute
last
minute,
addition
to
the
public
agenda,
I
think
we're
time
to
move
on
to
QA
from
anybody
watching
the
stream.
C
C
A
Opening
an
issue
for
that
would
be
a
great
idea,
I
think
the
the
ability
to
approve
pull
requests
in
the
interface
might
enable
us
to
make
and
automating
the
generation
of
reviewed
by
metadata,
for
example,
very
reliable.
That's
it's
very
exciting.
A
F
Someone
else
I
feel,
like
we've
seen
this
person
before,
but
I
can't
read
them
their
youtube
name
says:
what's
the
status
via
six
modules,
what's
the
team's
personal
opinions
on
that
I
guess
that
should
be
probably
to
me
these
days.
V6
modules
is
mostly
kept
up
in
the
related
eps,
which
numbers
I
don't
have,
but
it
should
be
EP
number
two
and
the
related
pull
requests.
F
Now
to
that
the
rewrite
and
or
my
other
proposal,
I
believe
there
will
be
some
of
us
and
Bradley
are
going
to
be
going
down
to
a
tc39
meeting
in
that's
at
this
month.
Yeah
and
we
have
some
materials
prepared
for
to
talk
more
to
them
about
some
challenges
were
facing
there,
which
are
mostly
summarized
in
related
pull
requests
on
to
that
EP.
F
A
Since
that's
specifically
for
personal
opinions
and
I
love
personal
opinions,
giving
my
own
because,
like
hear
myself
talk,
I
guess
I
certainly
hope
that
you
know
we
can
avoid
the
goddamn.
You
know
purse
personally,
I
hope
that
we
can
work.
You
know
we
can
work
with
tc39
and
get
alterations
such
that
we
can
avoid
the
dot
MJS
extension.
But
if
that
doesn't
happen,
you
know
the
the
dot.
Mjs
extension
is
not
ideal,
but
it's
it's
it's.
You
know
I
I.
Do
I
do
believe
that
you
know
better
than
than
other
options.
D
My
personal
opinion
is
that
we
are
unfortunately
trapped
in
a
tough
corner
where
tc39
has
created
a
spec
that
has
some
technical
problems
for
node.
We
are
having
difficulty
getting
them
to
hear
our
concerns
and
and
make
changes,
and
they
would
rather
they
think
that
the
path
forward
is
for
us
to
make
changes
and
that
that's
enough,
but
I.
Looking
at
the
details,
it
seems
to
me
that
that's
you
know.
If
we
do
that,
then
we
have
to
make
some
really
tough
breaking
changes
for
users,
so
we're
in
a
tough
place.
D
We
have
a
lot
of
users
out
there
that
love
the
idea
of
modules.
Unfortunately,
that's
based
on
existing
transpired
versions,
which
are
not
actually
expect
compatible.
So
the
thing
that
people
love
is
not
actually
the
thing
that
is
spect
and
that
we
are
being
forced
to
implement
so
it'll
be
interesting
to
see
how
this
plays
out,
but
it,
but
either
way
we're
in
a
really
tough
corner.
I.
F
One
other
thing
to
note
is
that
no
one's
no
browsers
are
shipping.
This,
yet
I,
don't
think
it's
ready
to
ship
spec-wise
are
saying
yet
so
and
regardless
v8
doesn't
have
it
fully
implemented.
So
there's
no
way
we
could
ship
it
today
or
probably
even
in
like
the
next
month
or
before
v7
or
whatever
anyways
it'll
take
longer
than
that.
No
matter
what.
B
Yep
chacras
implementation
is
actually
pretty
close
to
done
for
the
type
equals
module
speck
in
the
browser,
but
I
mean
that
would
drastically
change
if
we
go
to
tc39
and
that
changes
the
specification
because
then
they
will
have
to
re-implement.
D
So,
to
connect
the
two
questions
that
we've
had,
there
is
actually
going
to
be
a
talk
at
node,
interactive
Austin
by
Bradley
on
Wednesday,
this
nebula
30th.
So
if
you're
very
interested
in
modules,
you
really
should
turn
up
and
have
listened
to
that
and
even
chapter
Bradley
while
you're
there,
and
that
happens
to
be
at
the
same
time
as
our
ctc
call
so
I'm,
suspecting
that
a
lot
of
ctc
members
probably
won't
make
the
call,
but
maybe
even
be
in
that
talk
so
yeah.
A
F
D
I'll
just
make
one
a
minute
announcement
for
people
listening
and
for
the
record
that
the
foundation
has
been
conducting
it's
what
he
called
not
voting
for
chair
and
vice-chair,
and
the
votes
have
come
in,
for
there
is
a
Denise
Cooper
from
paypal
renewed
as
scare
and
Scott
Hammond
of
giant
renewed
as
vice
chair,
and
that
will
be
formalized
at
the
board.
Reading
this
week,
secretary
is
still
on
unfilled.
Yet.
A
Okay,
cool
thanks
for
listening
everybody
thanks
for
coming
ctc
folks,
and
let's
do
it
again
next
week.