►
Description
A
C
D
E
I
J
Hey
I
just
got
back
from
vision,
so
I'm
working
on
writing
up
some
of
that
stuff,
trying
to
figure
out
how
we
can
connect
with
the
community
there
a
little
bit
better
and
I
generally
just
kind
of
worked
on
the
board
meeting
and
stuff
yesterday
about
it.
I
don't
have
the
thing
in
firmly
sewn
up
next.
L
M
I
learnt
working
on
a
PR
to
make
a
module
cash
look
up,
case-insensitive
in
Windows.
It's
a
long-standing
issue
that
I'm
hoping
component
resolve
and
still
working
with
you
on
porting
benchmarks
to
windows,
especially
HTTP.
One
next
would
be
further,
but
it's
not
here
set
function
doesn't
seem
to
media.
She
get
he
not
here.
Stephen
Loomis.
N
I
A
F
So,
where
we're
at
right
now,
the
thing
I've
been
focusing
on
most
is
the
most
the
place
where
it
breaks
the
most
easy.
Not
so
it's
X.
So
my
pro
requests
for
using
blocking
mode
on
OS
x,
+,
4
td,
wise,
should
be
finished.
I
haven't
merged
that
yet
I'm
probably
going
to
unless
anyone
objects
out
for
the
meeting
and
then
do
a
release
with
it.
F
A
F
Well,
that's
not
entirely
true,
so
there's
been
long-standing
reports
since
one
point
no
point
to
when
we
had
the
lib
EV
one
point:
2.1
upgrade
about
stuff
getting
sometimes
dropped
from
pipes,
one
right,
outputs
too
large,
but
that
happens
sort
of
across
all
platforms.
Well,
it
happens
on
OS
X
2
because
it
has
to
deal
with
pipes
and
doesn't
have
TDY
hawks
like
OSX
did
40
wise.
F
F
A
F
A
F
Have
not
looked
at
that
right
now
that
kind
of
requires
the
van
awkward
touch
to
Libby
v
or
a
lot
of
work
on
our
end.
I
think
Ben
is
looking
into
rewriting
lots
of
that
stuff.
So
we
don't
don't
need
that
pack,
which
is
probably
about
as
much
work
as
actually
doing
the
stuff
on
our
own
might
be
to
begin
with.
So.
A
F
This
patch
is
pretty
much
good
to
go.
Investigate
on
Lennox
is
probably
going
to
be
a
little
bit
of
pain
now,
so
that
that
might
need
more
eyes
and
I
can't
really
like
I.
Don't
really
have
the
expertise
to
do
much
in
lib
EV
or
fix
some
of
those
problems,
necessarily
so
probably
get
back
to
everyone
next
week
about
that
or
try
to
ping
people
if
people
are
interested
in
potentially
helping
out
with
the
problem
like,
if
you
can
message
me,
that
would
be
great.
E
A
I
E
I
integrated
every,
like,
oh
sorry,
I'd
originally
the
you
know
not
necessarily
objected
to,
but
that
was
more
so
we
weren't
getting
like
what
do
we
do?
In
the
development
environment,
we
were
working
on
dogs
to
knotts
q
that
data.
That
was
the
only
like
concern
that
I
but
I'm,
not
of
those
by
any
means
I.
A
I
Yeah,
I
think
that's
fair.
I
think
also
that
I
mean
we
can
just
you
know,
kick
us
back
to
the
issue:
/
pull
retract,
pull
pull
request
system
and,
if
something
you
know,
if
someone
opens
a
pull
request
to
insert
google
analytics,
that
looks
like
it's
going
to
track.
You
know
stuff
that
other
than
what's
on
the
website,
then
it
just
takes
one
person
from
the
CTC
or
any
other
collaborators
say
don't
do
this
and
you
know
that
it
won't
happen
or
it's
not
supposed
to
anyway.
I.
C
H
C
J
A
J
C
A
A
A
A
C
I'm
not
talking
about
the
local
docs
now
and
about
the
Doudna
track.
Header
I
think
that
it's
a
perfectly
valid
option
to
just
ignore
the
junior
track
header
on
browsers
that
are
known
to
all
set
it
by
default.
Actually,
that's
watch,
Peavy
does
and
that's.
What
are
the
tracking
system
do
that
for
the
genital
area
today
they
just
acknowledge
if
it
comes
from
browser
dash
is
known
to
enable
it
by
default.
So
when
it's,
not
the
user,
that
should
did
enable
that.
I
J
I
can
make
a
suggestion
to
move
forward
like
if
we
have
a
patch
that
doesn't
include
them
in
in
the
local,
build
and
does
on
the
website.
Can
we
just
merge
that
patch
and
then,
if
somebody
wants
to
disable
it
with
do
not
track,
they
can
just
send
another
PR
on
top
of
it.
That
adds
that,
if
statement
to
remove
it-
and
we
should
probably
get
that
on
the
website
too,
if
they
want
to
send
that
PR
but
I,
don't
prefer
not
to
like
until
you,
you
know
blocking
this
indefinitely.
That.
A
B
So,
let's
see
over
the
weekend,
we
got
another
big
spike
people
with
interest
in
what
node
is
going
to
do
with
es
modules
and
we're
seeing
the
same
kind
of
varied
approaches
for
different
people
on
what
they
would
like
to
see
done.
We're
seeing
the
parsing
option,
the
package.json
option,
the
file,
extensions
being
talked
about
and
even
I
think
Chris
Dickinson
is
taking
an
approach
of
going
through
and
seeing
if
the
spec
can
be
changed.
B
B
There
was
a
vote
a
while
ago
saying
that
the
CDC
favors
the
file
extension,
but
that
is
by
no
means
the
absolute
be
all
end.
All
of
this,
because
we're
still
talking
with
tc39
about
things
that
can
be
done
to
rectify
the
situation.
I,
don't
know
how
much
we
can
change
the
spec.
It
looks
like
it
will
be
very
difficult
to,
and
it
would
have
other
repercussions
like
breaking
code.
B
That
people
expect
will
work,
especially
since
browsers,
are
starting
to
ship
BS
modules,
so
I'm,
just
taking
this
as
a
moment
to
inform
everyone
that
things
are
still
being
discussed.
I
don't
have
time
to
really
discuss
the
nitty-gritty
of
every
single
proposal,
but
I
will
do
my
best
to
keep
with
it
on
social
media.
That's
about
it,
quick.
J
Quick
question
about
the
things
that
break
like
if
we,
if
we
added
some
kind
of
pragma
at
the
top
or
something
like
that,
like
you,
can
see
an
additive
changed
of
the
spec
that
actually
wouldn't
break
anything,
that's
already
been
written.
It
would
just
be
a
requirement
for
that
to
work
in
node
right.
B
Yes,
so
there
have
been
a
couple
of
approaches
to
this,
so
like
use
module
is
one
that's
actually
really
hairy
implement
because
it's
really
hard
to
actually
determine
just
how
you
strict
works,
there's
actually
automatic
simian
semi-colon
insertion
rules
that
can
affect
it
and
it
deals
with
comments
and
things.
That's
a
kind
of
hairy
approach.
Krista
Canson
looked
at
having
magic
bites
and
that's
basically
a
label
statement
that
is
the
beginning
of
every
file.
That's
a
little
easier
for
tools
to
deal
with.
B
F
B
I
B
We
can
look
at
that.
The
status
report
is
going
to
be
massive,
probably
because
there
are
so
many
options
that
were
explored
well,
be
because
you
can
put
a
bunch
of
links.
Sorry
go
ahead.
No,
no,
no
I've
tried
the
whole
send
links
thing
of
it's
very
difficult
for
people
to
follow
if
I
send
a
ton
of
links.
So
the
other
thing
to
keep
in
mind
is
v8
doesn't
have
this
implemented,
yet
we
are
still
talking
to
them,
so
we
don't
even
have
a
parser
to
work
with.
B
This
is
not
going
to
land
in
node
7.
That
I
can
tell
it'll,
maybe
land
a
note
8,
depending
on
when
v8
finishes
their
parser,
but
even
beyond
the
parser,
we're
having
to
change
up
some
expectations
of
the
spec
in
order
just
to
get
it
to
work
at
all.
So
it's
not
like
this
is
a
quick
thing,
we're
probably
looking
at
next
year's
LTS
for
this
to
actually
be
in
core.
B
I
Mean
all
these
stuff
is
so
far
in
the
future,
that
and
subject
to
such
massive
change
between
now
and
when
it
actually
lands.
That
doesn't
seem
to
really
make
too
much
sense
to
try
to
get
the.
How
do
you
modules
work
in
know?
Jess
you're
widely
disseminated
to
the
average
user,
that
is,
that
correct,
Bradley.
B
Yes,
because
if
we
change
the
spec,
then
that
changes
how
things
are
learned,
it
could
also
change
how
we're
going
to
implement
things.
It's
more
in
flux
than
people
think
it
is.
People
expect
things
often
to
work,
how
Babel
works,
but
the
es
spec
does
not
work.
Helped
Babel
works
a
lot
of
what
people
expect
we'll
have
minor
breakage
when
they
move
to
Real
spec
based
modules,
rather
than
Babel
based
compilation.
B
This
actually
causes
a
problem,
because
the
way
most
a
PMS
work
today
is
that
they
take
a
module,
that's
already
been
evaluated
and
has
generated
its
exports
and
they
wrap
the
exports,
so
they'll
wrap
functions
and
things
in
order
to
tool
them.
So,
instead
of
exporting
the
real
FS
read,
file
an
APM
like
New,
Relic
or
app
native,
will
go
and
replace
what
read
file
would
have
been
with
something
else.
B
This
is
a
similar
pattern
to
what
happens
when
people
use
Bluebird
promise,
if
I
all,
but
the
import
view
we
are
given
on
either
by
importing
a
namespace
or
a
binding
directly
is
read-only.
You
can't
do
that
anymore,
and
so
we
have
to
kind
of
tool
out
the
loaders
using
vm
guidance.
So
we
have
to
talk
to
v8
on
how
exactly
we're
going
to
do
this
so
that
this
functionality
is
preserved.
F
B
We're
trying
to
get
them
to
both
work
under
the
same
spec,
so
we're
actually
talking
with
the
what
WG
loaders
back
about
if
they
can
modify
a
spec
that
they
have
called
the
reflective
module
record
to
meet
the
needs
of
apm's.
If
that
is
done,
and
if
all
the
VMS
agree
that
it's
an
okay
change,
then
it
will
be
in
the
what
WG,
loader
specting.
B
F
There's
some
other
comments,
so
it's
also
noted
that
those
threads
like
the
module
set
or
super
intimidating
and
can
be
very
difficult
for
new
people
and
also
the
same
person
who
this
is.
The
original
comment
also
comments.
It's
not
about
what
actually
happens.
It's
about
what
people
are
afraid
will
happen
in
controlling
that
conversation
yeah,
so
that
stuff
we
need
to
work
on.
They
say
they
might
be
willing
to
help
so
we'll
I'll
contact
them
and
get
them
a
little
more
I'm
standard
questions.
There
I
have.
B
B
So
that's
things
like
transforming
source
code
into
other
kinds
of
source
code
or
using
this
thing
called
the
reflective
module
record.
These
man-in-the-middle
modules
for
tooling,
like
a
PMS
and
finally,
there's
a
third
major
component
called
the
pipeline.
Oh,
we
can
pretty
much
reuse
everything.
It
really
closely
resembles
how
things
are
implemented
in
node
today,
except
for
the
pipeline.
So
the
pipeline
uses
a
lot
of
promises
and
forces
all
these
things
to
become
a
sink,
and
we
just
can't
do
that
without
causing
major
breakage
of
expectations
on
the
timing
of
when
modules
are
evaluated.