►
From YouTube: Rust and WebAssembly Working Group Meeting 2019-04-18
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
A
A
D
A
Yeah
no
I
think
that's
a
really
great
point
to
bring
up
and
we
might
as
well
discuss
it
now.
I,
don't
really
have
a
strong
opinion
either
way.
A
bunch
of
you
are
not
here
which
is
kind
of
unfortunate.
So
maybe
we
should
show
that
for
next
week's
meeting
and
then
hopefully
like
wry,
laugh
and
their
folks
will
also
be
here
to.
B
That
and
one
of
the
things
I
was
thinking
about
and
I
have
selfish
reasons
for
bringing
it
up,
but
I
think
it
probably
is
just
useful,
because
glue
has
brought
kind
of
like
an
influx
of
a
bunch
of
new
people
in.
Maybe
we
should
revisit
like.
Does
this
time
still
work
for
everyone,
because
it
may
be
that
people
are
not
showing
up
because
they
just
the
timing,
really
doesn't
work
for
them.
Yeah.
E
A
C
A
A
F
A
Okay,
so
also
in
flight
and
potentially
will
actually
make
it
better.
Sprint
deadline
awesome.
So
it
seems
like
we're
in
a
pretty
good
place
and
we've
estimated
our
amount
of
work
fairly.
Well,
we'll
see
I
guess
later,
but
yeah.
So
why
don't
we
go
ahead
and
move
onto
status
updates
glue,
so
there
hasn't
the
work
on
glue.
Stuff
has
been
a
little
bit
quieter
this
week
than
last
week.
I
believe
the
big
thing
that's
going
on
is.
A
We
were
very
close
to
accepting
the
file
API
proposal
and
we
also
switch
instead
of
doing
a
kind
of
design
proposal.
Discussion
in
issues
we
have
switched
to
saying
we're.
Gonna
do
PRS
for
those
I'm.
Just
gonna
have
a
little
RFC's
subdirectory
inside
of
glue.
They
make
for
requests
to
to
do
the
RFC
stuff
and
I
think
that
something.
B
A
The
thing
with
glue.
Is
that,
like,
like
almost
everything,
is
that
sort
of
kind
of
a
feature
request
right
because,
like
what
we're
doing
is
we're
designing?
New
API
is
from
scratch
and
that's
all
we're
doing,
whereas,
like
there's
a
lot
more,
just
kind
of
like
maintenance
and
internal
work
going
on
in
our
other
projects
to.
B
A
Yeah
so
like
no
like
considered
like
the
watch
and
serve
like
proposal
like
that's
an
RFC
and
I,
think
that's
like
working
pretty
well
for
like
being
a
place
to
discuss
the
stuff
before
we
actually
implement
it.
So,
like
I
know,
maybe
the
question
is
like:
should
the
glue
our
C's
just
be
normal
RFC's
and
we
should
do
that
design
work
there.
A
F
Just
I
wonder
if
I've
seen
the
poll
requests
in
STD
web,
I
recently
merged
I
haven't
tried
it
here
that
the
one
which
is
to
build
it
on
top
of
what's
my
engine,
it's
really
asked
also
so
we'll
be.
There
are
any
any
plans
for
cargo
web
integration
to
build
one
tool
instead
of
two
or
something
like
that.
Probably
cross
compatibility,
something
like
that
because
they
already
have
watch
stuff.
B
Definitely
sounds
like
something
we
should
talk
about
in
the
RFC
conversation,
so
I
would
definitely
urge
you
to
make
a
comment
on
that
that
RFC
with
that
stuff
and
and
we'll
definitely
take
a
look
at
it,
I
don't
know
if
cargo
ever
standard
with,
like
they
don't
use,
Waze
and
pack,
and
so
maybe
now
that
they
work
on
top
of
wasn't
bind
you
now,
there's
a
question
of
mending
other
splits.
So
I
imagine
the
comment
made
spin
out
into
several
other
types
of
things,
but
that's
probably
the
right
place
to
start.
B
A
B
Yeah
I,
don't
think
so
either
I'm
just
saying
like
that,
could
be
a
concern.
We
should
keep
an
eye
on
it,
but
I
don't
really
have
strong
good
things
about
it.
That's
something
I
was
thinking.
It's
been
had
a
question
which
I
actually
am
kind
of
interested
in
to
what
is
what
would
you
say?
The
size
of
the
glue
team
is
right
now.
A
So
we
have
a
official
team
member
list
right
now,
much
like
maybe
we
should
expand
or
something
that
I
think
it's
it's
myself
how
in
gosh,
I
love,
David,
O'connor,
I,
think
that
might
be
everyone
yeah.
Basically,
it
was
like,
like
people
who'd
been
doing
frameworks
that
I
invited
to
come.
You
know
collaborate
and
responded
positively,
slash
people
who
expressed
interest
in
this
before
we
kind
of
got
the
whole
thing
off.
Slash
people
who've
been
taking
them
apart
and
so
like
it's,
it's
it's
not
like
a
an
elite
club
or
anything
like
it's
like.
A
C
A
A
D
D
A
So
so
what
is
the
so?
You
have
this
abstraction
on
top
of
executor
so
like
because
my
understand
was
an
executor
kind
of
thing.
I
know
what
it's
called
in.
The
new
features
of
this
raker
was
the
abstraction
over
like
running
futures
and
async
stuff,
and
so
now
your
your
abstraction
for
different
backends,
like
Tokyo
or
whatever
it
is.
It's
like
a
super
set
of
Waker.
D
D
A
D
D
Right,
I
I
think
that
mapping
right
now
might
not
be
really
good,
but
a
thing
that
could
be
done
so
separately
from
runtime
is
take
that
idea
of
an
async
main
function
and
sort
of
make
that
that
kind
of
code
very
similar.
So
people
will
have
a
similar
experience
in
running
this
kind
of
stuff
and
one
Swasey
gets
developed
out
and
maybe
even
the
hybrid
environments.
We
get
to
revisit
this
and
be
like
okay.
Maybe
maybe
this
is
a
good
candidate
to
build
that
runtime
on.
C
Do
suspect
that
we're
going
to
have
a
like
a
runtime
for
wisdom
finds
in
which
only
the
ones
the
executor
and
continues
to
return
errors
for
everything
like
the
thoses
open,
although
I
suspect,
also
have
one
for
y'see,
which
will
probably
not
have
an
executor
because
it
doesn't
have
the
async
API.
So
he
can't
actually
do
anything
there,
but
it
could
have
a
like
stuff
for
the
things
I'm
in
of
it
was
he
probably
needs
async
anything
before
we
didn't
know
what
the
runtime
business
but
I
mean
we
are.
C
We
could
polyfill
things
on
the
web
on
the
unknown
website
of
like
the
wise
of
mind
yet
side
of
things
as
it
becomes
available
like
if
this
file
system,
if
is
networking
but
so
I,
think
like
it
kind
of
depends
on
like
we
can
certainly
provide
an
executor
and
I.
Think
our
job
once
futures
are
stable
in
the
state
of
libraries
referred
to
need
to
provide
an
executor
for
state
of
library
futures
and
was
a
by
Jim.
But
that
won't
be
two
words
way.
C
E,
we
wouldn't
even
bother
because
nothing's
async
and
her
wisdom,
we
do
all
of
the
executor
stuff
and
then
just
return
errors
from
everything
else.
Cuz
you
can't
really
get.
Even
we
can't
even
have
like
feature
Plex.
My
pretend
a
WebSocket
is
TCP
or
something
like
that.
I
know
that
all
right,
I'm
scripted,
has
a
bunch
of
polyfills
here,
so
we
could
presumably
map
those
polyfills.
Like
maybe
there's
like
a
virtual
file
system
that
every
eats
your
light,
we
could
think
slide.
It
would
have
been
one
thing
right.
D
No
I've
already
no
kidding
sorry
gathering
my
words
yeah.
What
what
I'm
thinking,
because
this
is
kind
of
like
hey,
it's
both
async
and
its
plasm,
and
it's
both
the
working
groups,
I
think
kind
of
like
a
natural
place
for
this
to
live,
would
be
under
the
runtime
repo
itself.
That's
just
in
our
back-end.
D
C
Already,
like
I
was
reading
it
and
the
default
is
like
a
native
runtime,
but
there's
some
default
runtime,
which
does
everything
reasonably
and
I
would
imagine
that
for
wisdom,
this
would
probably
just
be
the
default.
I
mean
like
either
away
somebody's
interested
most
I.
Don't
think
we
just
some
there's
some
default
for
wisdom,
which
does
the
really
I
think
returns
errors
in
three
years.
Excellent
features
yeah.
A
B
B
The
big
thing
is
like
clogging
up
all
the
pipelines
and
I
will
take
complete
blame
for
this
is
I
am
just
feeling
incredibly
stuck
on
how
to
test
the
generate
command
and
I
have
not
been
giving
myself
enough
time
to
really
figure
it
out.
So
if
there's
someone
who's
interested
in
just
being
like
at
least
leaving
some
comments,
I
got
a
bunch
of
really
good
feedback
on
the
PR
and
that's
stuff
in
general
and
I've
totally
implemented.
B
All
of
that
and
I
just
really
need
some
feedback
on
like
a
testing
strategy
here,
because
our
general,
like
fixtures
structure
like
the
generate
command,
is
kind
of
different
than
all
of
our
other
ones,
because
it
doesn't
operate
on
stuff
that
already
exists.
It
like
creates
a
bunch
of
new
things
and
I
don't
want
to
be
testing
cargo
generates
like
the
really.
The
only
thing
to
test
here
is
like:
does
the
command
exist
and
like
does
it?
B
Do
a
testing
PR
later,
because
that
is
blocking
the
wasm
opt
PR
from
Alex,
which
I
think
is
pretty
much
ready
to
go
and
then,
after
landing,
it
I'm
going
to
adapt
just
a
little
bit
of
what
it's
doing
with
the
binary
installed
to
use.
The
new
generalized
binary
install,
which
is
in
the
cargo,
generate
PR
for
the
future.
I
probably
should
not
have
slammed
generalizing
that
logic
and
a
new
command
into
the
same
PR,
and
now
it's
like
two
thousand
lines,
but
this
is
where
we
are.
B
Then
there
are
two
other
open
pr's
that
are
for
this
sprint.
One
is
from
a
new
contributor
which
is
in
response
to
the
issue
you
filed,
fit
gen
about
being
able
to
recurse
up
to
find
a
cargo
tamil.
So
you
can
like
run
in
cargo
or
was
impact
test
like
not
from
route,
which
is
a
very
good
feature
if
I
wish
that
cargo
format
had
this,
it
would
be
amazing.
So
if,
if
you
or
maybe
available,
if
it's
gen,
to
give
that
a
review,
otherwise
I
can
definitely
take
a
look
at
it.
B
But
my
primary
concern
is
this:
generate
PR
and
this
plasm
up
PR
and
then
Alex
just
filed
this
test
filters
for
was
impact
tests.
Those
test,
docks,
I,
believe
are
in
this
weird
hybrid
state
of
bison,
benjin
and
wiesen
pack,
so
I
think
just
some
really
preliminary
just
interface
docs
for
that
and
we
can
get
that
landed.
Yeah.
B
It's
all
still
make
sense
cool,
but
otherwise
that
the
pr
I--'s
don't
look
fine,
then
what
is
left
in
this
sprint.
So
there's
a
couple
of
things.
I
have
like
the
start
of
an
NPM
dependencies
thing,
but
I've
been
blocking
on
it
because
of
this.
Cargo
generate
shenanigans,
but
I'm
gonna
push
ahead
today
and
do
that
that
I
think
should.
Is
it's
actually
like
incredibly
straightforward?
So
thank
you
who
hasn't
been
doing
folks
for
like
making
that
a
relatively
pleasant
thing
to
do.
B
One
thing
that
I
feel
like
is
gonna
slip
and
I
have
been
kind
of
raising
that
I
think
it's
gonna
slip.
Is
this
isomorphic
Jas
target
I'm
very
happy
if
somebody
else
wants
to
take
that
on,
but
I
I
would
assume
that,
because
we
haven't
documented
the
design
terribly
well,
whoever
picks
it
up.
If
it
is
not
like
Alex
fetch
in
our
eyes
should
probably
try
and
talk
to
Al.
B
Don't
know
if
anyone
else
has
any
thoughts
on
that
sounds
good.
Well,
we'll
certainly
have
enough
features
in
this
to
make
the
release
feel
pretty
full.
So
there's
like
a
lot
of
new
functionality
and
then
there's
like
to
kind
of
small,
very
J
s
focused
features
that
I
had
tagged
on
this
spring.
One
is
the
NPM
install
package
and
the
other
one
is
our
install
page
is
using
logic
that,
like
I,
think,
is
like
very
good.
B
That's,
like
kind
of
always
been
like
sort
of
cut
and
paste
to
all
the
install
pages,
I
think
Alex
I,
don't
know
if
that's
true,
but
it
doesn't
call
out
like
that.
Cargo
install
is
a
thing
we
could
do
and
like
it
just
could
use
a
little
cleanup
again.
These
last
two
I,
don't
think,
need
to
be
in
this
print.
But
if
we've
got
people
with
like
vague
joyous
chops
that
are
like
looking
to
contribute
like
these
two
I
think
are
like
super
quick
wins.
G
B
Would
be
like
a
great
way
for
two
people
to
get
involved
so
I'll
probably
try
and
tweet
something
out
but
like
if
you
have
people
like
please
direct
them
in
this
direction.
This
is
like
they
I,
don't
imagine
they
could
take
very
long
and
it'd
be
happy
to
like
mentor.
Whoever
wants
to
do
it
so
and
yes,
so
that's
kind
of
where
we're
at
so
I
feel
very
confident
that
all
the
things
that
are
open,
PRS
and
the
NPM
dependencies
will
land
these
last
three
are
the
ones
that
I'm
kind
of
like
I.
A
Gonna
throw
there's
an
hour.
Reverser
has
another
speed
up
for
a
string
related
stuff
and
which
is
about
encompassing
strings
from
JavaScript
into
wasm,
and
it's
a
real
nice
man
I
think
it's
like
80%
faster
in
Chrome,
then
using
text
encoder
for
ASCII
strings,
which
turns
out
most
strings
well.
At
least
mini
strings
are
ASCII.
A
No
updates
for
monitoring
profiling
and
testing
infrastructure
as
far
as
I
know.
Actually
there
is
an
update,
so
we've
had
this
long
kind
of
split
due
to
the
way
that
it
wasn't
binary
and
test
was
designed.
We're
like
in
order
to
get
something
running.
You
know
we
needs
to
generate
different
bindings
depending
on,
if
you're,
testing
versus
testing
in
a
browser
and
so
like
in
order
to
get
that
I've
been
working.
The
original
implementation
was
like.
A
Here's
like
wacky
macro
that
like
enables
running
this
in
browsers
instead
of
node,
but
then,
like
kind
of
the
UI
experience
we
want.
You
know
users
to
use
the
user
experience
we
want
to
have
is
like
I
type,
wise
impact
test,
which
thing
do
I
want,
and
so
that
was
kind
of
like
what
we
made
when
we
first
had
a
Westpac
test,
but,
like
it
turns
out
we're
in
this
weird
state
where
you
actually
have
to
do
both
things
together
and
so
Alex
made
a
PR.
A
That's
on
the
way
to
reconciling
those
things
where
you
can
say:
I
only
want
to
run
these
tests.
You
can
tell
Wesson
budget
and
test
I'm
only
intending
to
run
tests
on
note
or
I'm
only
intending
to
run
tests
on
the
web,
and
so
the
the
Westpac
test
command
can
use
this
to
tell
as
divided
tests
what
its
intentions
are.
We
can
kind
of
reconcile
those
things
so
yeah
that
will
need
a
real
small,
quick,
PR
Westpac
after
that
man
wait.
B
C
This
does
remind
me,
though,
in
terms
of
the
motivation
for
this
was
actually
coming
from
stood
Webb
and
it's
worth
pointing
out
just
as
an
official
under
the
toolchain
point.
Stood
Wed
now
has
support,
I,
think,
publish
and
Christopher
was
App
Engine,
and
so,
if
you
dependence
a
web
and
use,
wasn't
benjin,
it
should
just
work
with
zero
action
on
your
part.
I
think
that's
also
the
default.
Now
right.
C
It
depends
on
the
tooling
you're
using
if
you
use
carbo
web,
it's
not
the
default,
but
if
you
don't
use
carter
web,
it
is
the
default
to
you
as
a
budget
and
so
kind
of.
If
you
take
Westpac
build,
you
can
use
stood
web.
If
you
type
cargo
web
do
I'm,
sorry,
I,
don't
actually
know
it's
me
with
the
tool
chain.
There
I'm,
not
I,
don't
I'm,
not
sure.
C
B
C
B
Sure
so
this
meeting
is
very
structured.
We
have
this
lovely
agenda
and
we
go
through
the
points,
but
there's
also
a
lot
of
just
kind
of
cool
things
going
on
in
the
web
assembly
space
and
while
we
do
have
office
hours
doing
it
immediately.
After
all
of
this,
like,
let's
get
the
work
done.
Thing
isn't
always
like
the
best
affordance
for
like
let's
chat
about
like
cool
stuff.
B
That's
happening
on
the
web
assembly
so,
like
the
other
day
like
fiction,
Alex
and
I,
got
to
talking
about
like
the
dynamic
linking
stuff
and
we're
like
hey,
it'd,
be
really
cool,
who
created
space
for
us
to
do
it.
You
know
as
a
full
group,
and
so
we
kind
of
came
up
with
this
idea
of
like
maybe
we
can
have
a
meeting
that
is
like
different
than
this
meeting
like
monthly
or
something
where
it's
it's
really
more.
B
C
A
I
think
like
the
observation
to
make,
is
that,
like
our
office,
hours
are
not
really
being
leveraged,
that
much
and
and
maybe
that's
because
of
kind
of
what
you
mentioned.
Actually
that,
like
we're
very
you
know,
we
have
all
this
like
stuff
that
we
need
to
get
through
and
by
the
time
we
get
to
office
hours.
It's
like
maybe
a
bit
intimidating
or
like
the
vibe,
isn't
right
anymore
for
just
like
hanging
out
and
asking
questions
or
for
chit
chatting
about
lazon
rough
stuff.
A
So
yeah
I
think
also
like
we
can
also
evolve
kind
of
what
we're
after
as
well
like
I.
Think
it's
nice
to
just
like
have
a
time
to
hang
out
and
just
talk
and
like
get
to
know
people
a
little
bit
who,
like
we
end
up
interacting
with,
without
seeing
each
other's
space
or
hearing
each
other's
voices
or
whatever.
A
B
B
People
who
use
this
seems
cool,
I
I,
don't
currently
sense
any
type
of
like
conflict
of
interest,
but
I
know
this
can
be
like
a
tricky
thing,
so
I
just
wanted
to
get
people's
vibe
and
the
strongman
proposal
was
have
them
just
comment
with
those
job
stuff
on
the
like
news
issue
and
just
include
it
in
the
weekly,
maybe
in
its
own
section,
but
whatever.
A
What
I
like
about
the
newsletter
is
like,
like
at
least
a
policy
that
is
easy
to
implement
and
keep
track
of
is
like
will
post
it
will
post
your
thing
on
the
next
newsletter
and
then,
like
you
know,
that's
it
great.
We're
not
gonna
keep
posting
it
until
you,
you
know,
fill
your
position
or
something
I.
B
B
But
since
we
have
the
opportunity,
where
I
think
it's
kind
of
like
a
small
group
of
people
who
are
trying
to
just
do
the
right
thing
which
is
like
if
they
post
it
on
their
thing
on
the
on
the
news
issue-
and
we
say
it'll
go
out
in
the
next
weekly.
If
they
like,
don't
fill
the
role
they
could
like
post
it
again
to
the
news
thing
like
a
month
later
and
just
be
like.
Would
you
run
it
again?
B
I'm
not
I,
don't
think
I'd
be
opposed
to
that
I
think
I'd
start
getting
mad
if,
like
we
start
getting
recruiter
spam
on
the
news
issue,
which
is
like
I,
think
a
legitimate
threat
but
I
mean
also
may
be
indicative
of
like
a
good
problem
to
have
like
people.
Think
it's
worthwhile
I,
don't
know
I
really
like
my
general
thoughts.
I,
don't
feel
like
terribly
strongly
about
any
of
it.
So
I.
F
Can
share
some
experience
which
I
saw
in
my
community
if
they
have
slack
and
there
is
a
topic
jobs,
it
is
moderated
and
they
have
rules,
and
they
just
take
her
that
people
who
post
jobs
they
follow
the
rules
and
similarly,
probably
we
can
have
a
discord
chat.
So
people
could
post
a
first-ball
and
just
someone
could
moderate
them
or
report
if
someone
is
get
interested
funny
or
something
like
that,
so
they
just
post
a
job
description
and
several
important
aspects.
For
example,
is
it
remote
friendly
or
a
location,
or
something
like
that?
B
This
guy
doesn't
seem
really
useful,
so
I
mean
maybe
what
we
could
do
since
there's
like
the
news
issue.
Maybe
if
we
open
a
jobs
issue
and
just
like
the
body
of
the
issue
is
I
mean
I
would
love
if
we
just
I,
have
no
problem
just
taking
exactly
what
Ellen
doesn't
musing.
That
sounds
like
it's
working,
we'll
just
put
that
in
the
issue
and
then
have
people
comment
and
get
up
as
like
good
moderation,
stuff.
So
people
are
goofing
like
we
can
lock
and
delete
their
stuff.
B
B
I
guess
the
thing
I
was
thinking
is
so
the
first
thing
was
I
think
we
have
more
people
reading
the
newsletter
than
we
have
in
discord.
That
could
be
wrong.
I
think
we
have
more
people
looking
at
the
github
than
we
have
in
discord
could
also
be
wrong
there,
but
my
expectation
was
that
this
would
be
a
kind
of
like
the
news
issue
where,
like
we
don't
like
clean
up
the
news
right
like
I.
A
B
F
A
D
C
Is
where
the
the
wiser
subgroup
of
the
CG
now
officially
has
a
chair
officially
as
charter
and
officially
is
more
official
I.
Think
basically,
so
this
is
the.
This
is
the
first
meeting
of
the
subgroup
to
start
discussing
and
I.
Imagine
and
the
chair
I
think
Sam
is
a
co-chair,
will
be
having
an
agenda,
so
we
actually
just
going
to
talk
about
or
something
structure
to
talk
about.
I
was
supposed
to
go
figure
things
out.
Sam.
C
B
A
B
Had
previously
mentioned
to
me
this,
that
inscription
was
willing
to
do
some
dynamic
linking
stuff.
There's
the
working
group,
the
community
groups
like
Doc,
which
is
not
really
been
updated
recently.
Do
you
have
any
links
for
like
where
that
stuff's
happening,
or
is
it
just
in?
Is
it
just
spoken
conversation
so
far?
We.
G
C
There
is
some
there
is
stuff
going
on
at
OPM.
I
know
that,
like
the
LVM
Tippa
tree
right
now,
we
have
to
compile
differently
in
rust,
because
otherwise
everything
goes
gets
really
weird,
so
something
has
happened
there
and
stuff.
This
happened
in
there,
but
I
I
suspect
that
what
is
in
LVM
to
the
tree
is
the
source
of
truth
of
what
wants
to
happen.
C
The
dynamic
linking
document
in
the
tool
conventions
record
link
there
might
reflect
some
historical
snapshot
of
what
LLVM
does
maybe
pretty
recent,
maybe
not
sort
of
recent,
but
for
the
actual,
a
lot
for
more
news
about
what
that
I
mean.
What's
going
on
with
dynamic,
linking
you'd
have
to
get
in
contact,
I
think
directly
with
the
inscription
folks
or
just
like,
with
the
with
people
working
on
that,
because
they're
gonna
know
way
better
than
I
am
about
what
their
use
cases
are,
what
their
targets
are.
C
Cool
noose
thing
that
I
just
saw
on
reddit
today
was
apparently
Mozilla
has
granted
a
moss
grant
to
the
amethyst
amethyst
project
in
rust,
so
I
think
amethyst
I
believe
amethyst
is
a
game
engine
written
in
rust,
and
so
they
had
a
grant
so
get
better
rise.
Some
support
for
that.
So
that's
that's
exciting
and
maybe
start
seeing
some
cool
rust
games
on
the
web.
That's.
E
B
C
A
PR
on
a
couple
of
you
posts
or
two
different
poses
that
are
kind
of
major
progress
on
this
I
think
the
one
on
GFX
or
a
different
one
uses
to
web
the
other
one
just
wasn't
by
gen
they're,
both
very,
very
old
and
outdated.
At
this
point,
so
I
think
the
goal
was
to
kind
of
get
this
up
speed,
but
I
do
think
you're
right
in
terms
of
like
it's
the
GFX
layer
that
meets
a
lot
of
support
and
then
probably
extra
tools
and
whatnot
and
like
win
it.