►
From YouTube: 13 September Meeting
Description
The Rust WebAssembly Working Group meeting from 13 September 2018.
B
B
C
A
B
As
far
as
like
the
last
bunch,
N
and
websites
area
like
I,
was
very
sceptical
at
the
start
that
we
were
going
to
be
able
to
do
all
the
things
that
we
set
out
and
basically
everything's
done,
like
we
haven't
actually
published.
What's
this
yet,
which
is
like
the
last
big
remaining
thing
but
like
I,
think
we're
at
a
point
right
now,
where
we
could
publish
it
and
like
we
just
want
to
double
check.
A
Also
think
that
over
the
last
six
weeks,
there's
been
a
lot
of
really
good
documentation,
work,
that's
happened
and
I
mostly
just
want
to
say
good
job.
It's
Jen
on
that,
because
it's
pretty
much
a
heroic
effort
by
basically
just
you
so
seriously.
Thank
you.
Let's
focus
on
trying
to
grow
that
team,
so
you
can.
Oh.
B
D
E
A
B
E
Beta
that's
being
produced
not
today,
but
soon
is
the
is
the
addition,
and
that
will
be
in
beta
for
two
cycles
until
mid
to
early
December,
and
so
the
next
cycle
technically
ends
in
late
October.
But
so
we
have
two
more
slight
two
more
six
week
cycles
of
Polish
for
before
the
edition
actually
hits
table.
B
And
like
again,
we've
since
had
all
of
our
stuff
pretty
much
in
you
know
shipping
and
writing
the
rest
release
trains,
but
what
so
we're
not
as
affected
by
like
deadlines.
But
what
will
happen
is
there's
gonna,
be
a
lot
of
marketing
and
attention
and,
like
we
have
a
very
big
prominent
place
on
the
new
website.
It's
going
to
roll
out
with
the
addition
and
everything.
So
as
far
as
like
users,
I
think
we're
gonna
see
a
huge
uptick
when
that
happens.
E
A
B
Yeah,
so
that's
exactly
like
what
I
was
trying
to
get
at
and
and
again,
I
think
this
is
the
case
with
like
a
lot
of
ways.
Impact
stuff
is
like,
like
implementations,
are
not
usually
like
that
hard,
but,
like
figuring
out
the
right
place
in
the
design
space
is
like
there's
a
lot
of
trade-offs
to
be
made
there
and
it
really
benefits
from
like
forethought
and
an
upfront
design
work
totally.
A
Can
I
share
my
screen
to
just
show
one
thing:
that's
kind
of
off
topic,
but
should
talk
about
it
all
the
amazing
work
we
did
in
the
last
six
weeks,
all
right
so
I
was
talking
with
my
manager
on
the
web
assembly
site
at
Mozilla
today
named
till,
and
we
were
talking
about
how
to
gauge
whether
or
not
we're
successful-
and
you
were
just
talking
about
getting
more
users
with
the
addition.
Push
and
I
just
wanted
to
share
that
I.
A
A
E
D
E
E
I've
kind
of
assumed
that
we
at
the
bare
minimum
will
start
an
issue
for
breaking
changes
who
want
to
make
and
I'm
sure
we'll
start
populating
it
pretty
soon
and
then
we'll
try
and
batch
those
up
so
not
have
them
all
go
out
all
at
once.
But
if
we
have
something,
that's
like
a
minor
breaking
change,
it
doesn't
really
break
anyone
practice.
We
can
probably
yeah.
B
Like
I
think,
there's
also
a
couple
like
Moe's
prefix
things
that,
like
shouldn't,
be
exposed
that
we've
kind
of
entrenched
in
the
way
by
DL
and
like
that,
would
technically
be
a
breaking
change
to
remove
it,
but
like
it,
wouldn't
actually
work.
If
anyone
was
trying
to
use
it
anyway,
and
so
like
that's
the
kind
of
thing
where,
like
I,
think
we
could
make
something.
That's
technically
breaking
change
as
a
not
freakin
version
books
that.
A
Being
said,
I
think
with
Alex
talking
about
doing
polish,
like
maybe
we
should
start
auditing
and
finding
those
things
and
just
removing
their
exposure.
Cuz
people
will
find
a
way
to
successfully
use,
but
you
thought
was
a
broken
just
like
nothing
thing:
they'll
figure
it
out,
and
then
you
really
will
break
them.
C
E
B
Great,
if
we
make
types
more
specific
or
we
add
a
new
wrapper
for
promise
that
keeps
track
of
the
generic
type,
that
it's
gonna
result
in.
That's
breaking
change,
yeah
I
think
those
so
certainly
the
way
that
we
translate
types,
I,
think
I
on
for
breaking
changes
and
and
those
specific
things
where
we
are
introducing
like
generics
or
something
like
that.
I
think
we
just
need
to
have
more
usage
experience
before
we
decide
if
that's
even
something
we
want
to.
B
First,
do
because,
on
one
hand
like
that
does
seem
like
it
would
be
a
nicer
interface
on
the
other.
Our
primary
goal
is
to
enable
usage
of
the
api's
and
kind
of
be
like
a
Lib
C,
like
system
library,
to
enable
other
people
to
build
higher
higher
level
api's
and,
and
so
there's
like
a
balance
there
and
I
think
we
just
don't
have
like
the
usage
to
inform
that
decision.
Yet
yeah.
A
And
I
would
say,
at
least
with
this,
like
timeline
I,
think
we're
aiming
for
was
impact
to
1.0
by
the
addition,
but
I
don't
think
that
we
want
resin
by
gen
to
1.0
ever
or
at
least
anytime
soon,
because
the
goal
is
to
get
people
to
like
get
a
large
number
of
people
using
the
tool
chain.
So
we
feel
like
we
have
enough
feedback
to
be
able
to
make
these
decisions,
which
I'm
not
sure
that
we
have
at
the
moment,
yeah.
B
So
certain
things
are
unsupported
like
which
API
is
is
that
affecting
because
it
might
end
up
being
like
a
very
small
count
of
api's
that
are
affected
by
a
particular
unsupported
feature
that
ends
up
being
a
really
important
API
like,
for
example,
just
setting
the
body
of
a
fetch
request
thing
that
seems
pretty
important.
That's
pretty
fundamental
API
on
the
web,
and
even
though
it's
like
by
the
numbers,
it
doesn't
show
up
a
lot
in
our
vast
web
idea.
It
still
seems
pretty
important,
so
I'm
gonna
actually
add
that
as
well.
B
E
B
I
think
moving
forward.
Probably
jeaious
value
is
the
best
thing
to
do
to
here,
because
it's
kind
of
implicitly
nullable
in
that
it
can
be
null
or
undefined
and
like
once
once
the
types
start
getting
like
a
little
bit
too
complicated,
like
I,
think
there's
diminishing
returns
in
trying
to
explicitly
type
it
in
rest.
B
A
One
thing
that
might
be
nice,
especially
if
the
ideas
for
like
polish
and
just
kind
of
like
slowing
down
I,
haven't
looked
at
the
codebase
in
a
second.
But
maybe
we
want
to
encourage,
like
some
refactorings
to
like
clean
up
some
stuff.
Just
like
I,
don't
know
if
we're
still
doing
like
typescript
generation
right
next
to
the
Jas
or
like
I,
don't
know
it
might
be
a
nice
opportunity
to
do
to
make
some
calls
for
like
cleaning
up
the
codebase
and
adding
tests
and
stuff
I.
A
Thinking
a
little
bit
about
and
I
would
have
to
go,
check
and
see
if
this
is
still.
The
case
feel
like
when
we
generate,
like
the
bodies
of
functions,
tend
to
have
like
make
the
J
s
and
make
the
typescript
like
right
next
to
each
other,
and
it
just
makes
the
function.
Bodies
really
long
and
I
feel
like.
A
A
It's
something
that
rust
is
tried
to
do
a
lot
of,
and,
like
seems
to
not
be
very
good
at,
but
one
thing
I
think
we
have
caught
on
to
is
that
if
you
don't
want
people
to
do
feature
work,
you
have
to
give
them
something
else
to
do,
or
they
will
add
features
so
like
coming
up
with,
like
just
saying
like.
Let's
do
cleanup
work
like
similar
with
feature
stuff,
it
can
help
to
like
file
issues
with
like
specific
types
of
polish
work.
C
C
C
B
C
E
B
A
A
So
there's
a
couple
of
things
that
I
definitely
want
to
see
happen.
The
first
one
is:
we
have
the
RC
RFC
for
expressing
NPM
dependencies,
and
so
this
actually
is
going
to
be
some
work
and
wasn't
binding
to,
though
not
not
to
much
at
least
as
far
as
I
can
tell
I
think
a
lot
of
it
is
already
there
but
yeah
so
finish
the
NPM,
depp's,
RFC
and
then
implement.
A
It
would
be
the
number
one
priority
thing
I
think
we
want,
but
additionally
I
think
and
we've
been
kicking
this
down
the
line
for
so
long,
but
really
spearhead
some
work
and
what
a
config
file
looks
like
for
wise
and
pack
so
that
we
can
find
they
get
it
in
there.
There's
like
a
lot
of
work
that
has
been
done,
but
I
think
there's
like
some
product
work.
A
That
just
needs
to
be
done
on
that
config
file,
and
so
I
would
really
like
to
see
that
land
and
so
assuming
that
we
can
get
the
config
file
was
an
optimism,
snip
support
and
then
the
NPM
dependencies.
That's
that's
a
whole
bunch
of
stuff
right
there,
and
so
maybe
that's
what
we
aim
for
for
what
a
wonderful
I'm
trying
to
think
of
what
does
a
1.0
and
wasn't
pack
require
it's,
not
those
things.
What
are
the
things
I'm
leaving
out.
A
B
The
other
thing
that
I
think
maybe
is
worth
like
having
conversation
around
and
like
you,
don't
necessarily
need
to
change
anything
here.
But
like
eggs,
worth
like
asking
the
question
and
and
exploring
the
designs
a
little
bit
is
what
to
do
with
like
local
installs
binaries
the
right.
Now
we
throw
them
like,
essentially
just
by
happenstance
the
way
that
er
was
implemented
and
without
like
thinking
about
it
too
hard.
B
And
so
you
know
it's
the
exact
right
version,
etc,
which
is
like
definitely
want
to
be
invariants
that
we
want
to
maintain
but
like
if
a
bunch
of
library
or
a
bunch
of
projects
are
all
using
one
behind
gen
OH
dot
2.15,
for
example,
they'll
each
have
their
own
copy
of
the
binary
and
like
does
it
make
sense
to
have
like
home
door.
/Da
plasm
pack,
slash
rake,
you
know
a
deduplicated
set
of
binaries.
B
A
B
A
E
A
A
One
thing
that
I
do
like
that,
like
doesn't
excuse
that
maybe
like
like
I'm,
not
trying
to
say
we
shouldn't
change
it,
but
if
people
do
want
to
share
one,
they
can
run
in
no
installs
mode
and
just
install
it
on
their
own
in
a
shared
place
like
installing
it
on
your
own
makes
it
a
shared
place.
So
then
you
can
just
do
it
and
you
just
have
to
run
the
install
on
your
own,
so
yeah
like
there.
E
B
A
A
B
E
One
thing
that
I
want
to
mention
is
the
installation
experience.
I
have
been
an
issue
for
this
pretty
recently,
but
I
I've
been
as
we
become
more
it's
just
with
awesome
pack,
I
think
it
makes
sense
for
us
to
pick
up
dependencies,
like
probably
literally
bundling
binary
on
inside
of
wasn't
pack,
so
you
don't
have
to
install
anything
when
also
do
things
like
that,
but
or.
E
Like
basically
as
we
get
more
ambitious
with
Wiseman
pack
and
which
I
think
we
should
it
becomes
harder
to
build,
wasn't
packed,
especially
for
newbies.
It's
like
the
canonical
example
that
I've
always
thought
of
this
is
like
I
am
in
Windows
user
who's,
just
trying
out
rust
for
the
first
time
and
like
what
stuff
is
gonna
be
great
there.
But
if
wasn't
packed,
stops
me
because
I
have
my
C
compiler
not
fully
configured
or
like
I
forgot
to
install
something
like
pretty
crappy
experience.
Yeah.
E
E
A
A
That's
awesome,
I
would
love
to
like
follow
along
on
what
you
do
so
I
can
also
help
out
with
it,
but
that
sounds
really
great
yeah
using
I.
It
would
also
be
nice
with
this
installer
thing.
The
update
story
for
cargo
installed,
anything
is
kind
of
garbage,
and
so,
if
we
had
an
installer
that
like,
if
you
want
to
install
the
latest
version,
just
does
the
uninstall
and
reinstall
thing
for
you.
That
would
be
nice
because
something
people
like
how
do
I
update
I'm
like.
B
This
reminds
me
also
of
two
related
issues,
which
are
the
output
of
lesson
pack.
So
I
don't
know.
If
folks
saw
the
little
mini,
RFC
I
wrote
about
how
to
do
progressive
enhancement
of
the
output.
I
think
that's
something
you
should
land
for
this
cycle
and
then
relatedly
I,
don't
know.
If
you
found
an
issue
about
this
Alex
or
it
was
just
like
chat
in
an
IRC
or
something
but
like
the.
A
A
I'm
down
with
that
of
all
the
things
that
we've
just
listed
and
just
noting
that
we've
listed
a
lot
of
things
and
six
weeks
is
long,
but
only
six
weeks
deciding
what
to
print
and
what
not
to
print
doesn't
seem
as
important
to
me
as
the
other
things
like
I.
Don't
think
the
fact
that
we
say
like
created
a
package.json,
even
though
it
took
less
than
a
second,
is
like
really
improving
anyone's
day
and
like
it
does
have
a
nice
element
of
self
documenting
what
the
tool
actually
does.
A
So
it
has
like
a
small
benefit
and
doesn't
seem
to
have
huge
negatives
I.
Think
in
the
long
run,
it's
a
really
nice
improvement
and,
like
I,
think
that's
positive
by
prioritisation.
Much
like
if
we
wanted
to
focus
on
the
output
of
Westpac
I'd,
be
much
more
interested
in
dealing
with
the
progressive
enhancement
and
also
a
couple
of
the
other
issues
that
Alex
filed
about
getting
the
cargo
build
output.
D
E
A
This
is
not
really
our
problem
and
just
have
a
the
working
group
build
tools
that
do
these
things
for
us,
because
it
seems
quite
squarely
like
in
their
wheelhouse
and
something
that
they
care
about.
And
what
to
do
like
I
know.
That's
true
like
what
I
told
to
killer
cover
about
the
emesis
bug
he
was
like.
A
You
need
to
fix
this
right
away
because
it's
literally
in
the
book
and
I
so
like
there
is
like
a
whole
set
of
folks
that
really
want
to
make
that
stuff
happen,
and
so
we
can
do
the
work
and
wise
impact,
but
I
also
think
a
lot
of
work
can
be
done
on
indicative
and,
and
it
turns
out.
Almost
all
of
this
work
actually
happens
in
the
underlying
crate
console
and
the
more
work
that
console
can
do
like
I
think
the
better
it
is
for
both
us
and
just
all.
Cli
applications
addressed
everywhere.
B
B
F
It
might
be
not
so
much
related
to
this,
but
it
combines
both
passing
back
and
matthan
behind
you.
So
initially
we
had
some
plans
like
because
some
JavaScript
libraries
and
reach
out
to
others
and
then
surgically
insert
vasin
into
it
and
increase
the
performance
and
showcase
this
kind
of
stuff.
Do
we
have
to
keep
that
kickstart
this
in
the
current
sprint?
Or
what
do
you
guys
think
like?
B
A
Could
be
wrong
about
this,
but
I
think
some
deal
is
is
referring
to
something
that
I
talked
about,
maybe
like
five
thousand
meetings
ago
or
something
where
it's
not
that
we're
necessary
blessing.
But
sometimes,
if
you
want
examples,
you
have
to
like
go,
seek
them
out
and
so,
like
I,
think,
for,
for
example,
one
of
the
things
might
be
I
know
at
some
point.
A
There
was
like
a
conversation
of
having
some
webpack
processes
and
wisdom,
I'm
thinking
of
a
conversation
I
have
it
like
Shawn
a
long
time
ago
for
like
finding
people
who
have
packages
that,
like
we,
both
think
would
benefit
from,
like
you
know,
replacing
some
of
the
code
and
lessons
and
that
the
maintainer
czar
like
excited
and
interested
in
doing
it
like
it's
mostly
like.
Let's
maybe
try
and
find
some
partnerships
and
just
like
seek
out
like.
A
F
Yeah,
it's
it's
somewhat
similar
to
that,
like
it
matches
whether
I
wanted
to
do
it.
Okay,
it
gives
an
advertising
ground
for
us
also
and
on
the
other
hand,
it
also
helps
us
in
order
to
showcase
the
capabilities
and
things
like
that,
which
is
probably
the
same,
because
I
have
gone
through
a
library
called
react
in,
go
like
they
have
trying
to
nature
converting
the
entire
rack
in
Co
and
they're.
Trying
to
do
Co
based
react
or
something
so
they're
people
who
are
trying.
Actually,
this
kind
of
stuff
and
I
think
like.
F
We
also
should
start
doing
that,
and
we
did
that
in
the
back.
So
the
fact
ji-suk
student
was
doing
and
doing
implementing
interest,
and
he
has
some
issues
and
I
think
we
will
have
to
reach
out
to
them
and
then
ask
like
what
is
that
problem,
and
probably
we
can
if
we
can't
help
we'll
help
them
all,
we
can
add
them
more,
and
we
also
have
to
clearly
tell
people
if
you
guys
want
to
do
this.
If
you
guys
want
to
try
this,
we
are
there
to
help
you
guys
and
we
can
make
this
happen.
A
Yeah
I
mean
in
the
end.
Maybe
this
is
just
something
like
a
set
of
tweets
that
we
all
promote.
That's
like
do
you
have
like.
Do
you
think
your
library,
your
JavaScript
library,
would
benefit
from
webassembly?
If
so,
like
know
that
we're
here
to
like
help,
you
do
that,
like
if
you're
feeling
lost
or
something
like
please
reach
out
like
we
want
to
help
yeah.
A
One
thing
for
the
book
I'd
like
to
see
fixed-
maybe
I,
don't
I,
don't
know
if
there
are
currently
plans
for
adult,
be
honest.
I
have
not
looked
at
the
issues
on
the
book,
but
in
recommending
the
book
of
some
of
the
Boz
Deborah
folks,
the
last
chapter
of
the
game
of
life
tutorial
I
felt
like
getting
it
running
or
I.
Think
it's
like
some
Python
like
engine
X
stuff
I,
would
really
love
to
replace
that
with
anything
else.
B
A
A
The
way
you
would
deploy
any
other
type
of
web
app
like
one
of
the
things
you
might
want
to
do
is
start
a
local
server
or
run
a
local
like
run
a
server
on
or
like
a
remote
computer
and
like
link
out
to
how
to
do
that,
because
the
the
solution
is
a
specific
solution
to
a
more
general
problem.
That
also
has
nothing
to
do
with
what
we
build
and
so
would
I
think
of
like
tech
debt
in
Docs,
like
we
should
not
maintain
documentation
for
something
that
we
don't
maintain.
A
So
I
would
love
to
just
like
find
some
good
tutorials
like
if
you
don't
know
how
to
deploy
a
web
application,
that's
chilled,
but
there's
of
books
out
there
and
how
to
deploy
web
application.
I
think
we
should
just
shell
out
too
instead
of
having
the
text
in
there
I
think
it
makes
people
like
my
initial
reaction
on
seeing
that
in
the
book
was.
Do
I
have
to
do
something
special,
and
the
answer
is
no.
A
You
don't
have
to
do
anything
special
to
deploy
an
application
that
has
some
webassembly
in
it
and
so
I
think
we
might
be
hurting
ourselves
there,
because
it
being
a
special
chapter
that
doesn't
say
like
it's
fine
I,
think
makes
people
think
that
they
have
to
do
something
unique
or
special,
and
that's
just
really
not
the
case.
Yeah.
B
A
It's
really
interesting
because
I
do
think
we
spent
a
lot
of
time
in
our
documentation
addressing
JavaScript,
audiences
and
I
do
think.
The
chapter
still
should
exist,
because
I
really
think
that
that
chapter
exists
for
people
who
are
not
coming
from
JavaScript
from
the
rust
people
moving
to
the
web
stuff
or
even
C++
folks,
and
so
I
do
think
it's
like
a
gap
in
knowledge
for
people
who
aren't
classic
web
developers
like
how
to
do
that.
A
B
E
B
Like
that's
all
embedded
in
the
tutorial
right
now,
but
there's
no
reason
it
needs
to
be,
and
so
we
should
split
that
out
and
then
this
tutorial
should
just
like
you
know,
have
only
these
specifics
of
profiling,
the
game
of
life
tutorial
and
then
just
reference.
The
reference,
material
or
I
can't
do
that
and.
A
That
sounds
great
I.
Think
it's
also
good,
because
that
will
give
the
book
like
a
little
more
like
return.
Value
like
I
know
that
I
always
like
tutorials
are
great,
but
using
a
tutorial
as
a
reference
can
be
a
huge
pain
in
the
butt,
because
there's
like
all
this
text,
you
don't
need
anymore.
So
I
like
that.
E
B
A
B
A
The
current
state
of
the
tool
change
just
like
a
like
a
link
aggregator
with
like
a
little
bit
of
context
around
each
I,
really
do
think
I'd
like
to
see
that
happen.
I
think
that
would
be
really
nice
and
people
seem
to
find
that
email
very
useful.
So
I
can
only
assume
that
other
people
and
everybody
who
wants
to
evangelize
this
workflow
is
not
going
to
always
email
us
about
it.
B
B
F
And
they
currently
only
have
the
back
support
I
think
they
have
to
move
to
data
bundles
and
probably
I
spend
some
time
on
this.
We
already
have
something
from
parcel
team,
I
guess
and
but
their
pull
request,
which
then
has
opened
for
integrating
webassembly
support,
is
still
open
there.
So
basically
I
think
most
of
the
things
we
cannot
do
unless
otherwise
the
bunglers
are
integrating
that
stuff,
but
probably
with
whatever
we
have
currently
like
parcel,
has
some
supportive
assam
currently,
so
we
try
to
add
those
things
inside
like
they're,
a
great
starting
off
point.
A
For
that
would
be
an
issue
that
itched
and
opened
on,
whereas
in
pack
and
assigned
himself
so
I'm
sure
that
he
would
be
happy
if
you
took
it
over
a
son
deal
which
is
so
I
spoke
with
the
parcel
folks
and
partial.
That
is
that,
like
out
of
the
box
like
the
Wes
impact,
workflow
should
work
with
parcel,
and
so
what
we
really
just
need
is
a
tutorial
that
explains
how
to
do
it.
They
just
like
an
example
to
either
one
show
that,
yes,
it
works
and
documents
it
or
like
to.
A
F
Of
course
it-
and
there
will
also
like
other
bundler
Zelda-
we
try
to
integrate
them
and
then
give
them
like
give
it
to
them
and
ask
suggestions
from
them.
Probably,
but
that's
that's
what
I
had
in
my
mind
and
the
template
section.
We
also
have
to
revamp
that
stuff,
because
we,
the
see,
is
not
perfectly
integrated,
I'm
just
hitting
for
the
sandbox
nest
release
once
that
is
there,
then
we
can
add
in
the
CI
to
see
thing
and
all
those
stuffs
can
be
done.
So
that's
pretty
much
of
it.
A
One
thing
I
do
know
that
I
want
to
do,
for
the
create
awesome.
App
template
is
right
now
create,
has
an
app
defaults
to
using
webpack
and
generates
a
bunch
of
web
pack
stuff.
For
you,
however,
once
we
demonstrate
that
the
parcel
stuff
works
or
if
we
had
any
other
bundler
support,
I'd
really
like
create
was
a
map
to
take
an
argument
of
which
bundler
you
want
to
use.
I
have
it
baffled
the
right
thing
for
you.
D
F
Generator
application
and
we
can
ask
set
of
questions
to
the
users
like
what
they
want
to
use
webpack,
whether
you
want
to
use
side
scripts
and
things
like
that,
then
we
can
use
that
information
and
create
application.
Probably
I
can
try
to
make
a
demo
project
or
something
like
that,
and
then
we
will
integrate
all
those
templates
into
a
single
location
and
make
sure
that
we
are
all
doing
that.
F
A
A
F
B
As
far
as
the
testing
story
goes,
I
think
we're
like
with
with
the
wave
impact
test
PR.
It
should
hopefully
land
today,
I
think
we're
in
our
super
super
good
place.
The
one
thing
that
I'd
like
to
add
is
right:
now
the
command
in
the
command.
You
specify,
if
you
want
to
use
fire
box
or
like
Chrome
or
some
headless
browser,
or
if
you
want
to
use
a
node
and.
B
B
If
you
try
to
run,
you
know
browser
tests
with
a
test
that
only
works
to
know
that
we
detect
that
and
like
say
like
nothing
to
do
or
whatever
right,
because
I
expect
a
lot
of
people
will
do
like
test
no
test
browsers.
Just
like
you
know,
especially
if
there's
like
one,
you
know:
sweet,
that's
per
node
and
one
sweet,
that's
for
browsers
or
whatever
just
having
that
work
correctly.
Yeah.
A
F
A
How
to
build
stuff
for
node
in
browsers
at
the
same
time,
happily,
together
that
story
like
I,
feel
like
that
story,
yeah
I,
guess
we
need
to
decide
if
we
want
to
get
that
done
before
the
edition
or
if
that's
the
first
thing
we
do
after
I.
Can
I,
as
I
said
in
the
last
meeting,
I
can
definitely
do
the
naive.
B
B
B
A
Thing
we
might
do
for
debugging,
which
maybe
it
fits
under
the
book.
I,
don't
know,
but
I
know
that
wasn't
debuggers
in
browsers,
nicer
and
so
maybe,
instead
of
like
oh
yeah,
I,
know
I
know
I'm
trying
to
be
positive
anyways
it
might.
We
might
just
like
try
and
like
talk
about
or
like
link
to
that
progress
in
the
book
to
be
like
this
is
what
these
browsers
are
doing
for
debugging
might
be
useful.
I,
don't
know.
B
A
I
guess
what
I
was
thinking
of
was
like
reaching
out
the
browser,
dev
tools,
teams
of
the
major
three
browsers
like
I,
know
the
person
working
on
this
type
of
stuff
at
Mozilla
and
like
if
a
place
doesn't
exist.
It
might
be
like
a
great
way
to
be
like
hey
by
six
weeks
from
now.
Can
you
please
have
a
blog
post.
A
A
B
B
B
B
A
B
So
getting
back
to
the
list,
I
think
this
list
is
looking
pretty
complete.
I
guess!
The
last
item
is
like
more
website
stuff.
We
just
did
a
bunch
of
like
content
overhaul
and
basically
matched
what
the
working
group
the
embedded
working
group
page,
looks
like,
which
has
been
kind
of
the
one.
That's
pioneering
the
domain
working
group
pages.
B
A
So
one
thing
I
guess
it's
my
guess.
We
could
do
that
or
I
realized
that
today
the
embedded
working
group-
somebody
I,
guess
started.
You
know
those
like
awesome
lists
that
people
make
about
programming
need
somebody
had
made
like
an
awesome,
rust
and
bedded
list,
and
so
that
was
absorbed
by
the
working
group
and
so
potentially,
if
we
wanted
to
like
take
that
weekly
list
that
we
have
and
like
turn
it
into
something
like
an
awesome
list.
A
A
B
See
some
of
that
is
like
in
the
book
with
like
crates,
you
should
know
and
like
tools
know
where,
like
I've,
been
trying
to
keep
that
very
curated
to
just
like
the
things
that,
like
you,
really
should
know
if
you're
gonna
be
doing
this
but
like
it
might
make
sense
to
take
this
list
and
make
it
like
a
chapter
of
the
book
or
something
if
that's
the
right
place,
or
maybe
this
like
landing
page,
that
we're
gonna
make,
is
the
right
place.
Yeah
I
agree.
That's.
A
Fancy
besides,
like
you,
can
make
a
PR
and
add
your
thing
to
the
right
category
and
the
readme
on
the
list,
and
we
could
like
repurpose
it
and
dump
it
out
on
a
website
or
link
to
it
or
something
I.
Don't
know.
People
do
really
like
I
know:
I
used
to
I
used
to
create
a
list
and
read
me
of
just
every
conference
stock,
I
watched
in
the
morning
and
friggin
love
that
stuff
they
loved
it
I,
don't
know
why
I
would
never
use
it,
but
lots
of
people
do
so.
Maybe
we
consider
it.