►
From YouTube: 5 July 2018 Meeting
Description
The Rust WebAssembly Working Group meeting from 5 July 2018.
B
C
B
There's
a
small
section
in
there
highlighting
the
differences,
but
the
big
thing
is
instead
of
ten
days
of
FCP.
It's
only
seven
because,
like
you
know,
our
goal
was
to
have
a
lighter-weight
RFC
process,
and
so
that
was
like
one
way
to
kind
of
make
it
a
little
faster
and
looser
and
I
am
actually
forgetting
what
else
was
in
there
like
it.
B
So
I
went
through
the
rest,
RFC
process
and
like
really
like,
dug
into
it
and
like
everything
that
was,
there
was
kind
of
there
for
a
reason
and
the
reason
that
it
was
there
like
also
applied
to
us
as
far
as
I
could
tell
so
like
the
whole
I
guess.
What
I'm
saying
is
the
rust
artsy
process
like
regardless
of
what
it
might
feel
like,
sometimes
is
pretty
lightweight
and
I.
Think
the
parts
that
like
feel
heavier
weight
are
the
parts
that
are
actually
really
meaningful
like
having
to.
A
My
one
thought
on
this
is
that
I
think
it's
good
for
us
to
have
this
now.
One
thing
that
I
would
potentially
add
and
I'll
comment.
This
is
just
that
because
we
are
a
very
small
community
at
the
moment,
however,
our
actions
have
larger
consequences
for
the
ecosystem.
As
we
move
forward
is,
perhaps
we
should
have
a
part
of
the
RFC
that
it's
not
really
something
you
fill
out
but,
like
specifically
encourages
the
need
to
socialize
the
RFC
and
maybe
say
like.
A
Maybe
you
need
to
add
to
my
deer
RFC
that
says
these
are
the
specific
types
of
groups
we
need
to
socialize
it
with,
like
I,
think
about
the
RFC
that
I
want
to
make
on
expressing
MPM
dependencies
and
being
like.
We
need
a
lot
of
feedback
from
j/s
tool,
writers
and
jeaious
developers
on
this,
because
I
think,
unlike
the
problems
that
rust
has
right
now,
which
are
almost
the
opposite
ones,
we
have
we're.
A
Gonna
have
to
do
a
lot
of
work,
to
get
people
to
say
stuff
to
us,
so
that
that
would
be
my
one
thing,
and
so,
additionally,
with
that,
if
we
don't
get
that
many
comments
on
this
right
now,
I
think
that's
okay!
As
long
as
we,
you
know
remind
people
that
there
is
a
specific
process
and
then
maybe
after
the
addition,
when
we
have
collected
more
folks,
do
like
a
revisiting
of
it
to
see
if
people
have
feelings
after
we've
kind
of
done
a
thing
do.
B
A
I
think
it's
really
great
idea.
What
are
the
things
that
I
I
tend
to
do
when
I
make
project
one-pagers,
which
is
like
the
project
management
version
of
an
RFC,
is
to
make
sure
to
list
out
like
who
the
stakeholders
are
and
who,
like
people,
responsible
and
just
kind
of
like
play
out
like
the
personnel
elements,
and
so
particularly
for,
like
our
current
situation,
I
think
specifically
reaching
out
are
specifying
like
who
this
affects,
which
is
almost
it's
almost
more
important
to
get
feedback
from
who
it
affects
than
actually
the
core
team.
A
D
Would
also
maybe
help
is
that,
if
that
is
the
case
within
the
RC,
like
comment
section
like
actually
listing
out
how
we
reached
out
to
those
groups
says
like,
if
I
have
a
stake
in
there
like
did
we
put
this
out
on
Twitter,
or
did
we
like
contact
specific
people
who
we
kind
of
trusted
with
those
opinions
like?
How
did
we
do
that?
Just
that?
There's
some
context
around
that,
because
they
might
not
directly
want
to
comment
on
the
RFC,
but
we
might
solicit
feedback
from
them
and
then,
like
post
arguments,
yeah.
A
I
think
it's
a
super
good
idea
and
I
think
I
mean
additionally
win.
Something
like
this.
We
should
probably
in
the
RFC
and
talking
about
this
kind
of
stakeholder
section
say
that
even
if
you
aren't
explicitly
listed
in
or
identify
with
the
groups
in
the
stakeholders
section,
you
can
obviously
comment
and
it
will
be
considered
important,
it's
more
of
a
like
bare
minimum.
These
people
need
to
be
involved,
not
alike.
Only
we
only
care
about
these
people,
so
I
can
see
some
people
maybe
take
getting
a
little
bit
flustered
about
not
being
listed
I.
B
A
A
B
So
just
this
was
this
idea
was
another
way
to
make
the
process
seem
more
lightweight
and
like
kind
of
move
forward,
a
little
faster,
which
was
that
we
have
the
signing
off
phase
and
FCP
happen
concurrently
and
then,
like
you
know,
obviously,
if
people
raise
new
concerns
that
can
cancel
I'm
kind
of
iffy
on
this,
it's
an
idea
and
the
other
thing
is
like
if
we
want
to
use
FCP,
but
it
might
be
easier
to
stick
closer
to
the
rust
RFC
process.
Yeah.
A
D
A
E
A
A
Also,
interestingly
enough,
this
there's
this
is
no
way
like
completely
done,
but
the
core
team
is
exploring
how
to
make
the
RFC
process
if
I
say
heavier
weight
that
will
be
a
soundbite
and
I'll
be
screwed
forever,
but
they're
looking
to
add
more
stuff
to
it.
So
once
that
happens,
this
will
already
appear
later.
Wait
so
I
don't
know
the
timeline
for
that.
B
A
Totally
cool
yeah,
so
I
was
traveling,
so
things
are
a
little
bit
slower,
but
there
are
several
pr's
in
flight
for
doing
that
kind
of
week.
I
definitely
could
use
some
better
words
for
this,
but
I'm
calling
them
like
build
profiles
at
the
moment,
which
is
like
not
great
but
fundamentally
the
configurations
that
they're
like
conventional
configuration
profiles
for
the
different
types
of
tooling
that
we
want
to
integrate
into
westpac.
So
that's
happening
right
now
and
then,
once
the
RFC's
repo
kicks
off
doing
the
dependency
expression
stuff
is
what
is
going
to
happen
next.
B
A
A
Don't
have
them
a
lot
of
background
and
hopefully
running
the
vision.
Close
will
help
lose
people
in
that
direction.
But
if
anybody
has
any
background
on
like
the
funders
wanting
to
own
the
compilation,
step,
I
just
think
long-term,
that's
gonna
be
really
confusing
for
them
and
they're
gonna
be
chasing
our
tools
and
I.
Don't
think
we
want
that
so.
A
D
E
C
E
D
So
this
is
gonna
kind
of
also
the
some
point
for
this
I'll
talk
about
that
afterwards,
that
I
put
in
but
documentation
wise
Sarah
here
actually
is
finishing
up
a
contribute
on
MD,
so
we're
going
to
get
that
in
and
we
merged
some
issue
templates
in
case
people
have
issues
with
the
books.
So
that
way,
it's
a
little
bit
more
categorized
based
off
what
type
of
issue
that
they
run
into
kind
of.
D
Like
Russell
Jess's
issue
tracker,
which
is
nice
that
way
we
can
kind
of
categorize
stuff
a
little
bit
better
as
they
come
in.
There's
still
a
couple
of
sntp
ours,
but
I
just
haven't
had
the
time
to
get
around
to
I
know
detail
you!
You
have
a
few
in
there,
which
is
just
my
bad,
so
those
need
to
get
looked
at
and
I
know
Alice.
D
My
other
grocery
twenty
is
finishing
up
getting
the
getting
the
game
of
life
repo
updated,
so
that
it
will
contain
all
the
of
the
template
code
that
we've
been
working
on
so
that
it
uses
that,
rather
than
just
download
this
repo
and
start
working
on
it,
but
instead
like
the
actual
tools
that
we're
trying
to
recommend
people
to
do,
especially
if
we're
saying
like
get
started
with
it
wasn't
kind
of
thing.
So
I
should
be
coming
in
soon.
But
I
have
to
be
gone
for
like
the
next
two
weeks
because
of
natural
dark
commitments.
D
So
I
might
have
my
phone
around
to
like
look
at
stuff,
but
to
be
honest,
I
probably
won't.
So
if
other
people
can
like
just
take
a
look
at
PRS
and
just
help
triage
and
move
them
along
without
me
around.
That
would
be
super
super
helpful,
just
to
kind
of
get
them
in
and
make
sure
people
aren't
like
kind
of
waiting
around.
For
that.
That
would
be
an
incredible
amount
of
help
so
like
I'll,
try
and
check
in
but,
like
you
probably
consider
me
dead
for
the
next
two
weeks.
In
many
cases
in
terms.
A
A
D
Yeah
I
can
I
can
triage
tonight
and
then,
like
mark
some
stuff
for
people
to
work
on
there's
some
outstanding
stuff
that
just
kind
of
sitting
around
I
know.
Some
of
them
are
maybe
a
little
bit
more
difficult,
but,
like
I
mean
I
loved
it
people
like
would
just
take
a
crack
at
it,
and
some
of
them
are
just
kind
of
more
of
like
issues
to
tell
people
to
file
issues
like
Oh,
like
kind
of
like
just
like
a
open
issue
that
says
like
hey.
If
you
see
something
wrong,
let
just
put
something
in
there.
D
A
D
Her
her
rewrite
is
affecting
the
code.
That's
used
for
the
tutorial
itself,
which
is
like
how
do
I
like
set
up
the
board?
How
do
I
get
the
stuff
flowing,
but
it's
not
actually
like
going
to
affect
the
publishing
actually
that
might
file
an
issue
for
that.
But
writing
doing
a
publishing
section
would
be
a
really
great
helping
write
up
because
it's
been
TBA
for
a
while.
So
someone
must
have
take
a
crack
at
it.
That'd
be
excellent.
Yeah.
A
B
A
One
of
the
neat
things
about
its
focus
is
that
it's
going
to
actually
be
more
marketing
focused,
as
in
the
audience,
is
going
to
be
primarily
for
CEOs,
CTOs
and
decision
makers
and
wanting
to
get
them
to
use
rust
and
to
that
end,
part
of
our
push
for
these
domain
working
groups
is
the
domain
working
groups
answer
the
question.
What
is
rust
good
for
which
is
incredibly
difficult
question
to
answer
right
now,
and
so
in
the
what
is
rust
good
for
section
there
will
be
a
page
on
web
assembly.
A
That's
gonna
show
off
all
of
the
awesome
stuff
we're
working
on
so
I
met
with
some
deals
in
deal,
there's
kind
of
like
a
three-stage
process
for
how
this
works.
The
first
two
stages.
We
don't
really
have
to
worry
about
because
it's
mostly
sin
deal
me
and
Erin
Turin
working
on
it,
but
one
of
the
important
things
is
collecting
great
content,
particularly
anybody.
That's
using
rust,
wasm
in
production
is
incredibly
useful
to
have
and
then
links
to
documentation
and
potentially
conference
talks
or
videos.
A
So
if
you
happen
to
have
that
stuff
drop
them
in
the
channel
or
send
them
over
to
Cindy
law,
Rai
is
a
great
idea.
The
third
stage,
which
I
don't
anticipate,
will
be
any
word
no
time
soon,
probably
in
late
August,
we'll
do
a
view
where
it
shows
all
the
stuff
that
likes
in
deal
has
done,
and
then
Aaron
and
I
have
refined
and
we'll
go
through
it.
A
That
way,
I
will
say
if
you
are
particularly
interested,
it's
always
great
to
have
one
person
but
I
always
think
it's
a
good
smell
if
one
person
owns
a
thing.
So
if
there's
anyone
else
who's
additionally
interested
in
the
website
and
like
wants
to
work
with
some
deal
on
it,
it's
definitely
there's
still
availability
for
that.
So
you
can
reach
out
to
me,
or
some
deal
to
talk
about
it,
but
we're
getting
going
and
we're.
Also.
This
team
is
kind
of
ahead
of
the
other
teams,
which
is
really
cool.
A
So
that
is
still
in
there
I
mean
I
had
my
meeting
with
some
deal
Tuesday
evening,
so
I've
kind
of
like
thrown
it
over
the
fence
to
him
and
he
has
not
like
sent
something
back,
which
is
very
reasonable.
It's
not
been
very
long,
but
I
do
think
at
some
point.
It's
really
good
to
bring
that
up
that
we
wanted
to
do
so
in
all
hands.
A
Upper
lid,
Nick
and
I
kind
of
was
brainstorming
part
of
this
page,
and
one
of
it
was
like
a
tabbed
code
snippet
or
it
showed
basically
like
a
hello
world
kind
of
thing.
The
goal
of
a
code
snippet
would
be
to
show
how
easy
it
is
and
inevitably
I
think
it
depends
on
where
we
end
up
landing
like
if
it
is
easy
enough
to
have
a
compelling
code.
Snippet
I
think
we
should
keep
it,
but
it
really
depends
on
how
compelling
we
can
make
it
so
yeah.
B
B
A
B
A
Well,
we
don't
directly
control
developer
tools
in
Firefox,
I,
think
being
able
to
show
off
that
we
have
support
from
that
team
is
really
awesome,
so
we
might
I
know
that
I
don't
currently
have
great
feedback
for
him.
Besides
that
it
would
be
a
great
way
to
help
market
this
stuff,
but
if
an
folks
want
to
get
into
that
further
I
know
that
he's
looking
for
people
and
I
can
share
his
email
address
with
them.
B
It
actually
reminds
me
of
another
thing,
which
is
that
the
the
webassembly
community
group
has
is
in
the
process
of
creating
a
sub
community
group
for
debugging
related
things,
and
this
is
where
kind
of
you
know,
dwarf
or
language
server
or
whatever.
That
would
allow
rust
to
actually
get
proper
source
level
debugging
on
the
web
in
developer
tools.
A
Thing
is
just
a
PSA
to
the
folks
in
this
group.
Anyone
can
join
the
wasm
community
group.
So
if
you
are
interested,
you
just
go
to
the
website
and
you
just
sign
up
and
they
send
you
an
email
that
says:
welcome
to
the
Wesen
community
group,
so
probably
worthwhile.
If
you're
like
interested
in
standards
or
even
just
to
kind
of
like
keep
an
eye
on.
A
A
There's
anybody
here
who
is
interested
in
doing
that.
The
like
really
short,
summary
of
what
cargo
generate
does
is
it's
exclusively
for
git,
repo
based
templates
and
what
it
does
is
it
clones
it,
and
then
it
does
substitution.
So
you
basically
create
a
repo,
that's
a
template,
and
then
you
plug
values
into
where
you
put
little
curly
brackets
your
template.
So
not
not
super
sophisticated,
but
it
should
be
useful
and
you
know
preventing
folks
from
having
to
write
out
a
whole
ton.
Importantly.
B
Alright,
next
agenda
item
is
so
I
found.
This
thing
called
depend
bot
and
it
will
send
pull
requests.
It
seems
like
it's
green,
it's
it's
like
green
keeper
for
NPM,
except
that
supports
rust,
and
so
it
will
send
pull
requests
to
update
sub
dependencies,
and
that
seems
like
something
that
would
be
useful
for
things
that
depend
on.
Madam
vine,
Jen
and
I
just
wanted
to
get
people's
thoughts
and.
D
A
A
A
A
B
C
This
assembly
support
right
now,
and
so
this
is
this
kind
of
probably
mostly
being
talking
with
fan
about,
but
so
there's
one
tool
wasn't
as
omim
the
binary
and
test
suite
or
like
the
battery
and
tool
kit,
which
has
been
had
some
work
done
and
like
is
somebody
it
doesn't
work,
but
it's
not
in
a
packaged
up
form
like
it's
a
very
manual
thing
and
everyone
has
to
reach
out
write
their
own
code
to
do
that.
So,
ideally
kind
of
like
the
high-level
idea
we
want
to
do
here
is
basically
solve.
C
And
then
internally
like
we
can
figure
out
whether
it's
but
because
there's
there's
two
strategies.
One
is
this?
Wasn't
as
impiety
symbaloo
to
javascript?
I
just
have
it
be
head
of
the
same
semantics
or
roughly
the
same
semantics.
The
other,
though,
is
I
know
spend
is
thinking
that
maybe
we
can
just
write
a
web
assembly
interpreter
and
javascript,
so
we
don't.
C
Actually
we
just
shift
the
same,
whether
some
blue
file,
but
we
have
an
entire
term
interpreter
baked
in
and
so
those
two
strategies
you
might
want
to
talk
about
at
some
point
figure
out,
but
that
probably
won't
send
here.
So
there
might
not
be
a
whole
lot
to
talk
about
here
other
than
if
anyone
has
any
thoughts
about
this
as
is
or.
D
C
Possible,
but
it's
subtly
different
enough
that
I'd
suspect
we
probably
aren't
going
to
use
that,
and
that's
also
so
for
us
code.
You
can
might
be
able
to
compile
your
code
once
and
you
can
compile
it
for
both
the
Asmodeus
target
and
the
target,
but
I
suspect
that
over
time
the
SMGs
target
is
probably
going
to
become
a
little
bit
rotted
and
or
not
do
so
hot
over
time
and
I.
C
C
What
you
can
do
is
that
this
is
not
necessarily
just
for
rust,
but
it's
also
kind
of
a
general
webassembly
goal,
which
is
to
have
some
sort
of
fall
back
and
so
C++
and
those
like
various
code
bases
may
not
always
have
the
option
of
using
inscription
or
like
instead,
and
so
the
idea
is
that,
ideally,
we
would
have
here
a
general-purpose
solution
for
just
web
assembly,
which
is
compiling
wasm.
Specifically,
it's
like
just
buys
into
Asmodeus,
but
that
is
probably.
C
C
A
So
like
for
me,
like
I'm,
like
sounds
good
but
like
I,
haven't
been
able
to
consume
all
the
information.
I
probably
would
need
to
make
an
informed
decision,
so,
like
I
also
want
to
tell
til
that
with
the
Mozilla
folks,
but
we
should.
We
should
try
and
have
some
sort
of
like
group
document.
That
says
that
this
is
what
we're
trying
to
do
and
why
I.
C
E
C
Where,
like
there's,
certainly
a
couple
of
options
like
we
could
do
any
any
of
the
above,
what
I
would
personally
probably
advocate
for
like
doing
mostly
and
wasnÃt
Azzam,
although
we're
thinking
of
renaming
that
tool
as
the
Jetsons
anyway,
so
basically
doing
most
of
that
right
there,
and
then
the
bundler
every
bundler
would
share
that.
So,
like
roll
up
parcel
web
pack,
everyone
would
do
the
same
thing
of
just
calling
this
this
one
tool
and
that
way
ever
no
one's
know
no
one
has
to
duplicate
to
too
much
functionality.
Okay,.
B
B
A
Also,
just
mostly
I
I
do
feel,
and
this
is
partially
an
in
like
kind
of
an
awesome
way
that
the
folks
on
the
bun,
their
team
have
a
lot
of
time,
but
I
feel
like
Butler's,
already
have
a
rather
large
and
important
role
in
our
stuff.
So
expanding
that
and
particularly
expanding
it
in
a
way
that
affects
a
specific
module
type,
might
just
be
expanding.
It
way
too
much,
especially
for
a
team
that
we
really
need
to
focus
on
a
really
specific
workflow
I
mean
they're.
A
Both
awesome,
don't
get
me
wrong
and
I'm
not
trying
to
say
I,
don't
want
them
working
on
it.
So
much
as
I'm,
just
like
I,
think
I
think
we
need
to
keep
it
focused.
Also.
The
use
case
it
seems
to
cover
is
es6
module,
support
and
node,
which
has
no
timeline
as
far
as
I
checked
last
and
so
I
guess,
additionally,
I
would
share
their
like
I.
Don't
think
this
is
urgent
in
any
way
one
person
that
I
think
that
we
might
want
to
loop
in
to
get
some
feedback
on
this
and
like
the
stakeholders.
A
Okay,
I'm
that
we
talked
about
with
RFC's,
is
Lynn
Clark,
who
is
championing
the
wasm
modules
proposal
in
tc39
right
now,
so
she's
gonna
have
the
most
information,
I
think
so
I
I
would
probably
say.
Let's
turn
this
into
an
RFC
and
or
maybe
just
have
a
conversation
about
further
details
and
loop
and
Lin
to
see
if
this
is
exactly
what
we
want
to
be
doing.
B
A
Only
thought
against
that
is
I.
Don't
think
this
is
gonna
be
important
before
the
addition,
and
we
already
have
more
things
and
more
things
we
want
to
do
than
teams
and
people
so
I
feel
like
it
might
be
more
of
a
distraction,
but
I
don't
know.
These
are
just
like
gut
level
feels
at
the
moment,
so
maybe
I'm
wrong,
but
all.
A
D
A
So
I
added
this
just
because
so
as
a
result
of
a
bunch
of
the
conferences,
I've
been
going
to
have
been
like
chatting
with
a
whole
bunch
of
people
about
the
Russ
web,
somebody's
story
and
it's
very
cool,
and
so
previously
I
tried
to
push
benchmarks
on
speed,
and
no
one
really
picked
that
up
and
that's
fine.
But
one
thing
that
I
think
we
really
should
do
and
I
know
for
was
in
packets.
It's
one
of
my
priorities
and
I
think
maybe
the
advise
and
buy
was
in
mind.
A
It
might
actually
be
the
better
place
to
put
it
I'm,
not
sure,
but
one
of
the
things
that
I've
gotten
from
the
folks
in
the
web
assembly
community
group
is.
They
are
very
concerned
about
the
size
of
the
binaries
that
Russ
generated
wesam
is
producing
in
general.
They
think
they
are
too
big
and
okay
and
the
thing
that
I
was
kind
of
struck
by
is
like
to
be
honest.
A
This
way
is
a
good
idea,
and
so
having
like
some
sort
of
canonical
way
to
establish
either
goals
for
what
our
code
size
is,
or
at
least
to
be
able
to
watch
it
over
time
seems
really
useful
if
anything,
because
a
lot
of
the
people
were
trying
to
sell
on
rust,
beacon,
great
language
for
webassembly
seem
incredibly
focused
on
it
for
better
for
worse.
It
definitely
seems
like
something
slightly
easier
to
benchmark
at
this
point
then
speed
so.
D
A
A
So
just
just
knowing
those
things,
because
these
are
also
things
that
we
should
be
able
to
explain
to
other
people
who
care
about
code
size
to
like
not
do
like
pulling
in
all
the
formatting
shenanigans.
It's
pretty
huge,
maybe
you
don't
want
to
do
that
so
I,
don't
know
it's
it's
mostly
just
like.
Do
people
think
that
that
code
size
is
a
good
measurement
to
look
at
right
now
and
if
so,
are
there
other.
B
A
A
Totally,
like
I
I
think
we
actually
have
like
a
fair
amount
of
very
awesome,
tooling
and
again,
as
I
was
saying,
with
wise
impact.
The
fact
that
we
want
to
integrate
a
bunch
of
that
like
in
order
for
me
to
sell
the
added
complexity,
I'm
gonna
want
to
be
able
to
say
like,
and
this
is
what
it
gets
you
and
it's
quite
awesome,
but
I
do
think
right
now,
also,
particularly
for
trying
to
sell
breasts
generated
was
Jay.
A
S
folks
is
like
we
don't
even
have
like
a
baseline
of
what
we
consider
acceptable,
maybe
not
even
acceptable,
just
like
here's,
where
we're
at
that
might
be
useful
and
that
kind
of
comes
down
to
kind
of
creating
this
canonical
program,
like
example,
things
that
we
use
for
it,
but
I'm
like
really
excited
to
to
do
some
stuff
on
this.
So
I
mostly
wanted
to
see
if
people
thought
it
was
a
good
or
a
bad
idea
is
inevitably
when
you
measure
stuff,
it
can
cause
all
sorts
of
effects.
D
That
would
be
cool,
I.
Think
would
also
help
if
we
just
had
some
like
Jas
and
Quinlan
benchmarks.
I
know,
because
people
like
well
I
want
it
smaller
and
I'm
like
okay.
That
might
be
true,
but
like
what's
also
good
enough
and
like
is,
is,
is
just
the
web
assembly
that
we
output
baseline
without
skipping
anything
and
doing
anything
I
sure,
like
still
faster
than
the
JavaScript
equivalent
like
I,
know,
I
know.
D
But
you
know,
there's
there's
a
lot
of
stuff
that
it's
also
being
done
on
the
web
browser
side
to
make
things
faster
and
like
so
where
we
like
I,
just
feel
like
we're
kind
of
like
in
the
dark
at
this
point
so
like
having
anything,
would
be
better
than
nothing
but
like
also
just
kind
of
understanding.
We
have
different
browsers,
are
going
to
implement
things
differently
and
how
does
it
get
rid
of
JavaScript
and
whatever
so
I
think
I?
Think
we're
gonna
have
like
a
wide
variety
of
benchmarks
and
I.
A
Agree,
I
guess:
I
just
figured
that
sighs,
so
one
I've
seen
a
ton
of
comments
both
in
my
own
DMS,
the
wasm,
discord
and
IRC
that
talk
about
code
size
and
the
question
almost
always
is.
Why
is
what
I'm
getting
from
wesson
benjin
and
was
impact
so
much
bigger
than
X
and
I
was
mostly
just
really
embarrassed.
Cuz
I
was,
like
you
know,
I,
don't
even
know
the
size
of
the
thing
that
we're
making,
maybe
I,
maybe
I,
shoulda
friggin
know
that
I
mean.
D
B
A
Them
to
Twiggy,
but
I
also
like
it's
not
that
oh,
my
gosh,
we
have
a
code
size
profile,
I,
go
check,
it
out,
isn't
a
good
answer,
but
it's
also
a
sort
of
RTFM
answer
that,
depending
on
like
the
person
and
how
important
it
is
for
me
to
continue
to
have
them,
be
excited
and
stuff
it.
It
can
be
really
useful
to
also
be
able
to
share
like
some
info
and
then
be
like.
If
you
want
to
look
more
into
your
own
thing,
here's
a
tool
where
you
can
do
it
like.
B
E
C
Just
keep
catalog
of
these
kinds
of
things
like
we
know
how
to
fix
them,
and
so
we,
like
some
of
this,
is
go,
read
the
page
as
to
why
it's
so
big
and
like
there's,
there's
like
gotchas
of
how
to
do
things
and
we'll
try
to
turn
those
on
by
default,
eventually,
and
so
just
having.
That
would
also
be
helpful
to
just
a
bird's-eye
view.
What's
like
the
most
common
things
that
people
keep
getting
tripped
up
on
or
what's
the
most
common
reason,
so
we
can
focus
our
own
efforts.
B
And
I
think
like
like
the
overall
holistic
benchmark
and
like
comparison
to
Jas,
is
going
to
be
kind
of
hard
and
that's
going
to
involve.
You
know
not
just
like
size
to
size
comparisons,
but,
like
you
know,
wasm
is
so
much
faster
to
parse.
You
can
kind
of
parse
and
instantiate
during
streaming
from
the
network,
whereas
you
can't
really
do
that
in
JavaScript,
or
at
least
no
one
is
right.
Now
this.
B
B
They
leave
that
to
like
browser
vendors
because
they
want
to
compete
with
each
other
on
that
and
so
they're
they're
gonna
make
those
benchmarks
eventually
but
like
for
us.
We
should
definitely
have
our
own
kind
of
like
internally
focused
something
like
perf
Wrestling
org,
where
we
are
watching
the
size
and
making
sure
that
we're
not
regressing
it
and
stuff,
and
and
then
like
for
users
who
come
and
ask.
We
can
have
the
documentation
and
other
stuff
yeah
I.
Also.
A
C
A
A
lot
of
people
might
be
running
into
that
stuff,
and
just
like
not
knowing-
and
it's
like
that
attitude-
that
if
my
code
size
is
friggin
huge
like
a
lot
of
people,
don't
read
that
as
oh,
that's,
a
bug
they
just
read
it
as
oh
rust
makes
huge
binaries
and
so
having
a
way.
It's
a
signal
like
actually,
no
those
are
probably
bugs
and
we'd
love
to
fix
them.
Please
file
them.
That's
like
not
like
a
call
to
action.
We
really
have
yet.
A
B
A
That
is
gonna,
be
really
important
for,
like
the
success
of
webassembly
in
general,
like
kind
of
shifting
people's
minds
and
getting
them
to
understand
the
problems
that
it
solves
and
what
it
solves
well
and
so
I
know
till
who's.
The
web
assembly
manager
at
Mozilla
and
et
is
starting
to
give
like
a
lot
more
conference.
A
Talks
and
I
know
that
the
ask
for
conference
talks
is
getting
larger,
but
I
wonder
if
there's
not
a
way
that
we
could,
particularly
as
we
start
talking
about
the
website
page
and
just
in
general,
like
we
can
build
all
this
awesome
tech.
But
if
nobody
uses
it
like.
That's
not
super
great.
So
maybe
thinking
about
setting
a
goal
for
maybe
evangelism
was
the
right.
Word.
B
A
I
think
even
just
having
a
deck
in
our
org,
that's
like
a
weird
once
we
get
all
the
vision,
posts
and
stuff
out
I
think
you
already
have
like
a
really
good
start
to
that.
Nick
from
your
presentation
at
the
Mozilla
All
Hands,
so
yeah,
something
that's
like
a
reusable
like
reusable
decks
are
complicated
but,
like
maybe
that's
a
good
start.
Yeah
I
just
know
that
a
lot
of
folks
in
webassembly
right
now
are
thinking
about,
like
we
need
people
who
focus
on
the,
not
tech
part
too,.