►
From YouTube: 2019-02-21 Rust and WebAssembly Working Group Meeting
Description
A
A
So
if
you
have
an
opinion
about
what
you
think
we
should
be
working
on
in
2019,
that's
a
place
to
go
and
the
others
are
for
integration
with
JavaScript
one
for
allowing
rust
crates
to
say
that
they
depend
on
an
NPM
package
when
they're
compiled
wisdom
and
the
other
for
saying,
hey,
I
have
this
little
snippet
of
JavaScript.
That
I
want
to
include
for
use
in
my
web,
so
check
this
out
as
well.
B
A
D
C
D
C
A
E
E
A
C
Of
a
minute
ago,
specialist
initial
comment
on
the
the
meeting
issue
saying
that
fix
for
the
producer
section
was
in.
There
was
the
previous
book
this
week
and
he's
currently
working
on
fixing
the
WebGL
example,
which
is
this
issue
and
affects
not
just
the
WebGL
stuff,
but
also
a
lot
of
whys
of
my
generated
stuff.
It's
in
the
works.
C
B
Right
so
I
dumped
a
bunch
of
stuff
in
here,
so
the
first
thing
to
say
is
alex,
has
a
open
PR
for
making
progress
on
the
progressive
enhancement
output
for
the
CLI
output,
which
is
great
I
left
you
a
couple
comments,
Alex
I,
don't
know
if
you
saw
but
there's
a
wise
impact
test
failure.
There's
there's
test
failures
unrelated
to
your
PR
that
are
making
that
a
red
Travis,
which
is
a
bummer.
We
should
look
into
that
and,
if
you're
interested
in
that
mini
RFC.
B
E
A
B
A
D
A
B
B
All
right,
so
all
the
closer
I
was
just
doing
triage
this
morning.
So
sorry
about
that,
so
the
next
thing
was:
we
got
some
some
Twitter
feedback
from
some
users
and
one
of
the
asks
which
I
actually
think
I
need
to
double
check.
If
resin
binder
actually
already
does
this,
but
there
was
an
ask
for
like
our
current
default
es6
build
people
feel
like
it
requires
webpack.
Do
we
have
like
a
bare
es6
target?
That's
like
no
modules
but
uses
es6
modules.
B
C
A
B
A
The
wasm,
but
like
I,
don't
know,
I,
don't
really
want
to
like
support
the
combinatorial
explosion
of
like
module
systems
and
likewise
I'm
instantiating
and
bumblers,
and
like
if
the
one
rse
I
forget,
which
one
I
think
it's
the
depending
on
NPM
packages.
Has
this
table
of
like
kind
of
like
target
environments.
That
I
think
is
useful
to
look
at
here,
which
is
like.
We
will
always
have
like
something
you
can
use
without
a
bundler
and
like
just
making
sure
that
we'd
have.
That
is
like
super
critical
and
like
having
something.
A
That's
like
the
future
with
like
yes,
modules,
integration
and
everything
is
like.
You
know
something
we
should
support
and
like
we
should
push
everyone
towards,
but
like
I.
Just
don't
I
mean
convinced
me
if
you
feel
otherwise,
but
like
I,
just
I
don't
want
to
like
support
every
single
combination,
because
there's
so
many
bugs
were
like
that
only
occur
if
you
use
this
flag
and
that
one
and
like
that
I
totally.
B
A
B
I
can
go
through
my
Twitter
I
think
they
they
somehow
found
me
by
tagging
in
Surma,
and
so
it
seems
like
friend,
is
maybe
not
the
right
word
but
like
friend
of
a
friend
of
a
friend,
some
company
person,
but
I'll
find
it
and
I
can
I
can
definitely
share
it.
I
didn't
have
the
time
this
morning
just
belong
through
my
Twitter's
to
find
it.
A
E
B
B
If
they
watch
this
video
and
I'm
wrong,
please
correct
me:
it
seemed
like
they
were
very
excited
about
the
rest,
Wiseman
story
and
saw
it
as
a
way
to
get
out
of
like
the
build
system
shenanigans
in
GIS,
and
they
felt
frustrated
that
they
had
to
dive
right
back
in,
and
you
know
they
said
something
about
like
configuring
webpack,
even
though
the
web
pack
default
configuration
for
us
is
pretty
pretty
small
but
yeah,
it
was
basically
just
like
I
thought.
I
could
get
out
of
this.
Why
do
I
have
to
do
it
again?
B
Kind
of
sentiment,
gotcha,
which
means
I,
think
that
no
module
stuff
would
work,
but
they
basically
were
asking
like
I
do
think.
There
is
a
fundamental
misunderstanding,
like
one
of
the
insights
that
they
said
we're
like
have
browsers,
not
implemented,
es6
modules.
Why
would
I
need
to
use
a
bundler
to
use
es6
modules
and
so
they're
like
missing
how
wasm
changes
that
story?
And
so
maybe
that's
something?
A
A
That
I've
been
thinking
about,
based
on
like
a
lot
of
people's
kind
of
first
impressions
with
with
our
documentation
and
everything
is
I've,
been
thinking
about.
Maybe
switching
the
tutorial
over
to
use
no
modules.
The
game
of
life
tutorial,
because
all
the
like
NPM
link
is
kind
of
a
bit
of
a
pain
and.
E
A
And
everyone
seems
to
get
like
stuck
on
that,
like
all
of
almost
like
90%
of
the
issues
we
get
for,
the
tutorial
are
like
NPM
link,
didn't
work
and
then
it's
like.
Actually
you
just
didn't,
run
the
commands
and,
like
you,
that's
just
a
bad
situation
to
be
in
so
I
think
like
it
would
be
nice
to
just
making
new
modules
a
little
bit
more.
You
know
front
and
center
yeah.
B
And
I
need
to
finish
out
the
marketing,
pr2
and
I
should
catch
up
with
you
if
it's
shown
exactly
how
we
want
to
do
that
and
we're
but
I
think
there's
a
nice
story
to
be
told
if
the
game
of
life
tutorial
is
like
the
barest
of
bare
and
then
like
all
of
the
QuickStart
guides
are
about
like
integrating
it
into
your
workflows,
but
then
the
game
of
life.
One
is
like:
here's,
the
nuts
and
bolts
all
the
commands
and
like
the
barest
thing,
that
you
can
do
I,
think
that
tells
a
good
story.
B
Alright,
so
that
was
like
that
user
feedback,
thing
and
I
will
add
the
link.
So
I
am
six
days
late
on
my
monthly
release
of
Waze
impact,
but
I'm
going
to
begin
the
work
of
I'm
just
going
to
do
a
minor
bump,
because
I
don't
think
a
patch
makes
sense
with
everything
that's
landed
so
far,
so
I'm
gonna
begin
work
on
the
o
dot
seven
over
lease
today
work
on
the
changelog.
B
If
there's
anything
that
you
want
to
like
sneak
in
or
we
have
a
couple
of
open,
PRS
and
a
bunch
of
the
CI
is
failing
on
them.
I
think
for
very
trivial
stuff.
Do
do
try
and
get
that
in
today,
because
I'd
like
to
at
the
latest
ship
it
this
evening
or
tomorrow
and
I-
know,
there's
some
open
items
and
but
I've
labeled
Oda
eight
that
I
think
I
can
can
move
back
over
to
this,
since
this
is
going
to
be
a
minor
release
or
not
a
patch
release.
B
Sounds
cool
and
then
so
I
wanted
to
talk
about
kind
of
what
I
see
as
the
big
things
on
deck
for
ODOT
8
and
then
maybe,
if
people
had
ideas
for
what
comes
next,
like,
let
me
know,
but
for
Odin
8
I
really
think
we
should
land
the
wasm,
ops,
integration
and
then
I
want
to
also
land
the
progressive
enhancement,
at
least
the
first
step.
That
alex
has
done,
if
not
further
steps
and
then
also
the
gate.
Cargo
generate,
bundled
in
for
wisent.
A
B
B
B
F
F
A
We
actually
probably
want
to
integrate
Rasmus
trip
because,
generally
all
of
the
things
it
does,
we
have
options
to
do
already
in
West
benjin,
an
actually
that
makes
me
think
something.
I
wanted
to
to
kind
of
propose
for
us
an
engine
which
is
like
I,
don't
think
we
should
do
the
producers
at
all,
because
it
seems
like
it's
pretty
dead
in
the
water
after
the
last
CG
meeting.
A
B
A
A
C
This
is
what
I
think
that
you
should
definitely
continue
to
emit
it
by
default
and,
of
course,
have
an
option
to
turn
it
off,
but
and
I
suspect
that
if
we
leave
it
on
that,
no
one's
even
going
to
ask
what
the
option
is
to
turn
it
off.
So
I,
don't
think
there's
much
to
do
on
our
end,
because
we're
still
gonna
have
it.
But
it's
a
question.
There
is
a
question
of
like:
do
you
wanna,
try
and
push
it
further,
I
think.
B
I
I'm
gonna
go
read
whatever
is
written
down
about
this,
but
I
think
I,
think
that
for
the
health
of
the
webassembly
ecosystem
and
like
selfishly
for
us
and
our
desire
for
analytics
like
having
a
way
to
know
who's
producing,
this
stuff
seems
incredibly
important,
and
you
know
I
think
also
just
as
a
working
group
or
as
a
community
group
like
there
needs
to
be
more
realistic,
like
understanding
set
about
like
how
long
adoption
takes
seems
like
that's.
This
is
a
moment
for
maturity
for
the
group
to
understand
that
adoptions
can
take
a
long
time.
A
B
Don't
know
it's
I
mean
everybody
seems
so
positive
on
it
in
the
beginning.
So
again,
if
we
want
to
encourage
this
code,
golfing
like
okay,
but
I-
would
imagine
that
being
able
to
show
the
strength
of
producer
ecosystems
and
attempting
to
sell
these
technologies
to
enterprises
later
on
would
be
incredibly
important,
and
that's
going
to
be
incredibly
important
to
make
this
technology
successful,
so
I
agree.
It
makes
the
bundle
like
a
tiny
bit
larger,
but
I
don't
know
like
this.
Successfulness
of
the
technology
will
need
these
numbers
yeah.
A
B
B
Cool
yeah,
so
I
guess
the
the
only
last
thing
for
me
was
I
want
to
start
having
like
an
idea
of,
what's
gonna,
be
in
the
release
like
a
release
ahead
of
time.
So
right
now
it's
question
marks
for
on
deck
for
Odin
and
oh,
please,
please
feel
free
when
issues
are
filed.
If,
if
you
have
done
anything
unwise,
I'm
pecker,
I've
added
you
as
a
contributor,
so
you
should
be
able
to
tag
milestones,
go
for
it
and
we
can
talk
about
it
more
in
next
painting
and
that's
my
update.
I.
A
Circling
back
to
the
Wesen
ops
bit,
I
talked
to
alone
the
other
day
on
IRC
and
I
brought
up
the
the
distribution
binary
stuff
that
we
have
like
I,
think
to
kind
of
work
in
progress
or
requests
for
binary,
and
he
seemed
like,
like
he
was
fine
merging
those.
He
just
had
like
an
outstanding
question
of
like
whether
they
were
like
work
in
progress
or
ready
to
merge
or
not
so
I
think
just
to
know
it
would
be
good
till
I
circle
back
and
make
sure
that
those
are
ready
to
land.
B
A
Nothing
in
darks
accepts
I
manually
array.
I
made
sure
that
we're
using
the
latest
MD
book,
which
fixes
this
bug
we're
sections
are
numbered
incorrectly.
If
there's
a
horizontal
rule
between
sections,
so
yeah
I
know
more
section
three
line
section:
five
there
will
be
a
section
four
I
think
that's
it
I.
B
C
We
do
support
very
small
code
sizes,
but
we
don't
actually
track
this
or
test
this,
and
so
this
would
be
something
to
not
a
guide
of
how
to
do
it,
but
something
for
us
sort
of
internally
and
externally,
a
little
bit
of
tracking
this
over
time,
see
finding
progressions
and
also
we're
just
calling
an
improvement.
So
we're
like,
if,
if
we
release
a
new
version
of
some
random
crate,
some
random
tool
and
like
we
improve
the
state
of
libraries,
I
want
to
see
these
over
time
and
kind
of
how
we're
decreasing
size
for
various
benchmarks.
C
And
things
like
that
and
so
I
wanted
to
ask
here.
I
might
have
some
time
this
weekend
to
start
working
on
it
with
some
students
and
would
be
curious
to
see
what
other's
thoughts
on
in
terms
of
what
would
you
like
to
see?
What
would
you
like
to
make
sure
it
definitely
does
and
kind
of
just
general
requirements
there.
So,
like
some
examples,
that
I
would
say
is
I
would
want
it
to
basically
always
be
using
the
most
up-to-date
versions
of
tools.
C
So,
for
example,
it
should
use
the
most
recent
as
impact
the
most
recent
rust
scene,
so
get
snapshots
of
that,
and
so
that
way
we're
not
walking
anything,
and
we
can
actually
look
at
improvements
in
webpack
in
westpac
like
all
of
these
things
over
time.
So
that
would
be
kind
of
like
one
important
thing
that
I
would
want
to
see.
I.
B
C
I
think
we
probably
have
like
I'm,
not
super
interested
right.
I
feel
like
this
isn't
the
most
useful
tool
for
absolute
numbers
for,
like
this
cases,
ten
bytes
large
rather
more
so
this
use
cases
shrinking
over
time
gradually
and
so
in
that
sense,
I
think
I,
look
kind
of
like
purpose
like
a
word,
I
think,
basically
anything
so
like.
C
If
someone
has
a
project
and
throw
it
in
there
and
see
how
it
looks
and
so
I
I
will
probably
have
like
an
ad
like
add
one
and
two
and
just
see
absolute
number
of
how
many
bytes
that
is,
but
beyond
that
I,
don't
think
we're
gonna
have
that's
where
I
also
see
it
is
somewhat
I
start
out
more
of
an
internal
style
tool
as
opposed
to
public
facing,
and
then,
if
it
ends
up
working
really
well
for
us,
we
could
see
how
to
spin
it.
It's
like
a
marketing
kind
of
thing.
Oh.
B
Yeah
totally
I
think
it
should
be
internal
to
start.
You
might
talk
to
Surma
the
wasm
that
the
rust
wasn't
there
using
for
the
squish
app
is
like
a
slightly
more
elaborate.
I
mean
more
than
slightly
elaborate,
like
just
map
transform,
like
it's
print,
just
like
rotating
arrays
of
numbers,
and
so
that
might
be
a
nice
example
because
it's
yeah
it
uses
slightly
more
like
it
uses,
arrays
and
stuff
or
slices.
So
watching
that
size
will
be
useful.
I
think.