►
From YouTube: wasmCloud Community Meeting - 30 Aug 2023
Description
Welcome to the wasmCloud community! Tune in live where we discuss the latest developments in the wasmCloud ecosystem, WebAssembly standards, and break out sweet demos.
Agendas for wasmCloud community meetings can be found at: https://wasmcloud.com/community
A
All
right,
I
think:
that's
it
hello.
Everyone
welcome
to
the
waslam
cloud
community
meeting
for
Wednesday
August
30th
I'm,
going
to
get
into
the
agenda
here
in
a
second,
but
we
actually
have
a
new
Community
member,
not
new
to
the
community
but
new
to
the
call
here
so
yourdis.
Would
you
like
to
do
a
little
introduction?
Just
you
can
say
whatever
you'd
like,
but
if
you
want
to
talk
about
what
what
brought
you
here
and
what
you
do
for
work,
that'd
be
great.
B
Yeah
so
yeah,
my
name
is
Jordan
I'm
from
Cuba
I've
been
doing
programming
for
over
a
decade.
B
And
for
the
last
seven
years,
I've
been
focusing
Elixir,
primarily
and
nine
years
in
react,
so
I
was
doing
fintech
and
a
lot
of
even
sourcing
even
driven
architecture
at
a
bank.
And
what
brought
me
here
is
I.
I
pushed
the
boundaries
of
my
code,
so
much
I'll
control
the
side
effects
so
much
where
the
Elixir
itself
don't
really
matter
per
se
and
I'm
chasing
better
developer
experience
when
it
comes
to
the
programming
language
while
keeping
a
runtime
that
will
give
me
more
or
less
the
same.
C
A
Awesome
yeah
thanks
thanks
Curtis
for
for
being
here
for
for
doing
the
intro
I
know,
there's
been
some
really
awesome
discussion
in
our
slack
over
the
last
few
days,
especially
around
event
sourcing.
So
if
you're,
not
in
the
slack
and
interested
in
that
topic,
that's
a
it's
a
great
place
to
to
go.
You
would
just
have
some
really
awesome
insights
there
all
right.
Well,
why
don't
we
go
ahead
and
get
started
with
the
agenda?
Oops
spoilers.
A
So
what
I
want
to
go
ahead
and
do
today
is
give
a
really
quick
demo.
Just
it's
gonna
be
the
basic
inner
workings
of
of
like
a
wasmcloud
app,
but
it's
actually
going
to
be
using
the
rust
host
and
do
a
little
update
on
the
OTP
feature,
parity
and
then
we've
got
some
discussions.
It
looks
like
I
left
off
this
sentence
here,
but
we've
got
some
discussions
on
the
initial
release
of
the
rust
host.
A
Take
a
look
at
the
road
map
and
then
just
our
weekly
final
week
reminder
about
the
wasn't
Con
coming
up
soon.
I
guess
we
can
still
touch
on
bacon
then
as
well,
because
it
won't
be
Friday
yet
so
without
further
Ado.
Why
don't
we
go
ahead
and
get
started?
I
just
wanted
to
show
One
update
in
the
wasmo
cloud
wasm
cloud
repo
before
we
get
started.
If
we
go
ahead
and
take
a
look
at
the
issue
Milestones,
you
can
see,
we
made
awesome
progress
towards
widification.
We
have
so
many
so
much
progress
here.
A
Just
a
couple
of
open
issues
remaining
and
I
actually
think
that
the
open
ones
are.
Some
of
them
are
kind
of
small
like
migrating
one
or
two
crates,
but
the
other
Milestone
that
we've
been
tracking
for
the
last
few
weeks.
Otp
feature
parity
is
almost
complete.
We
have
a
PR
open
to
close
this
final
task,
around
policy
checking
and
that's
been
reviewed
as
just
a
couple
of
nits
there
to
update,
but
I
want
to
give
a
huge
shout
out
to
I
know.
A
I
did
some
work
here,
but
Connor
and
Roman
and
Victor
for
a
huge
amount
of
work
on
the
rust
toast
and
getting
it
up
to
speed
with
the
OTP
host,
which
is
which
is
really
exciting,
and
you
know
we've
had
a
couple
of
discussions
in
terms
of
as
a
wasm
cloud
developer.
What
what
does
this
really
mean
to
you
like?
What
does
the
rustos
being
featured
parody
with
the
OTP
host
mean
and
really
what
it
is,
is
when
you
come
and
you
launch
the
rust
host?
A
Eventually,
this
will
be
done
when
you
run
wash
up,
but
if
you
run
the
wasmcloud
rust
host,
then
it
actually.
Let
me
show
you
the
help
text
real
quick
more.
If
you
look
at
the
help
text
for
the
OTP,
sorry
for
the
rest
host,
you
can
see
that
the
options
here
mirror
exactly
what
we
have
in
the
Watson
Cloud
OTP
host.
A
You
know
being
able
to
specify
and
that's
authentication
parameters,
lattice
prefix,
your
validated
cluster
issuers,
things
like
that
and
when
you
run
the
Watson
Cloud
rust
host-
and
you
say:
hey,
you
know
what
host
do
I
have
in
my
lattice
we're
going
to
get
the
one
back
which
is
running.
We
can
get
the
host
inventory.
We
can
also
do
things
that
we've
been
used
to
now
that
we've
started
exercising
the
wadum
or
the
declarative
application
management
flows.
A
So
if
we
take
a
water
manifest
like
for
the
key
value
counter,
which
includes
an
actor
to
capability
providers
and
then
to
linked
apps
as
well,
we
can
deploy
this
manifest.
Just
kind
of
like
you
would
with
like
a
cube
control
apply
and
we
take
a
look
at
the
inventory
of
the
host.
We
can
see
that
all
of
those
resources
have
launched
and
we
can
curl
the
endpoint
that
we
defined,
which
I
think
was
8081.
A
And
we
can
see.
Okay,
I
was
doing
a
little
bit
of
load
testing
on
this
earlier.
So
that's
why
it's
3
000
something,
but
but
really
what
you
need
to
know
as
a
developer
in
the
waspod
community.
Is
that
all
this
hard
work,
that's
gone
into?
The
rustos
brings
a
backwards
compatible
experience
to
wasm
Cloud.
A
So
when
we
switch
over
to
using
the
rust
host
with
wash
you're
not
going
to
notice
anything
different
in
terms
of
launching
your
applications,
but
what
this
really
lets
us
do
is
stay
really
close
to
the
webassembly
standards
and
as
new
things
come
out
there,
as
there
are
new
releases
of
wasm
Time
new
functionality
released
for
webassembly
components,
we'll
be
able
to
really
quickly
iterate.
On
that
release
that
to
to
you-
and
really
this
is
just
very,
very
forward-looking,
so
just
to
sum
it
up
again
and
just
maybe
harp
on
it
a
little
bit
more.
A
What
this
means
is
that
getting
to
transition
to
use
the
rustos
won't
require
you
to
change
anything
for
now,
but
it
will
and
it
will
let
you
iterate
quicker
on
components.
So
we're
really
excited
I
can't
say
that
I've
done
any
of
the
work
on
terms
of
getting
our
examples.
Componentized,
but
I'm
really
excited
to
to
get
those
to
show
those
to
you.
I
know:
there's
going
to
be
some
demos
next
week
at
the
at
wasn't
con
and
then
our
examples
right
now,
there's
actually
a
PR
out
there
for
the
key.
A
The
KB
counter,
for
example,
that's
generated
with
wit,
is
a
component
really
awesome
stuff,
so
I'll
go
ahead
and
paint
this
in
the
chat.
Just
just
in
case.
People
want
to
see
that
Bailey
I
I
know
that
you
said,
you
said,
show
the
size
which
one
did
you
want
me
to
show
like
how
much
which
thing
how.
A
Yeah,
let
me
take
a
look
at
that,
so
if
we
take
a
look
at
each
stop
modern
Cloud,
we
can
see
that
right
now
running
an
actor
and
a
capability
provider.
We
got
like
about
31
Megs
of
of
ram
here
to
run
these
different
resources.
I
know
that
the
idle!
So
if
we,
if
we
stock
this
thing
and
then
take
a
look
at
the
idle
memory,
usage
of
wazen
cloud,
I-
think
it's
really
low.
I
haven't
actually
taken
a
look
at
this
yet,
but
let
me
see
if
I
can
filter
this
again.
A
A
A
I
think
this
is
really
exciting
for
what
it's
worth
Beyond.
You
know
just
the
great
engineering
Minds
behind
the
rust
host,
but
I.
Don't
we
haven't
done
really
any
optimization
passes
on
making
this
as
small
as
possible
or
making
the
memory
usage
as
efficient
as
possible?
So
it's
really
just
exciting
to
see
what
we
get
with
this.
A
Let's
see
so
I
know
that
I
wanted
to
well
here.
Let
me
let
me
pause
here,
because
I
did
a
little
bit
of
a
demo.
Does
anybody
have
any
questions
on
the
oh
wait,
I'm,
probably
sharing
that
on
I.
Anybody
have
any
questions
on
this
demo.
The
differences
with
with
the
rest
host
or
or
like
to
see
anything
else.
A
Yeah
I
know
Justin
had
a
question
in
the
chat
around
the
Ye
Old.
The
ye
old
rebel
that
used
to
come
up
with
with
wash
up
I
think
that'll
be
a
really
that
can
be
a
fun
brainstorming
topic
to.
Maybe
we
could
could
talk
about
at
the
end
of
the
call,
but
I
know
that
we
haven't
talked
about
a
ripple
and
in
a
hot
minute,
though,
that
was
a
really
fun
project.
A
Okay,
well,
why
don't
we
go
ahead
and
keep
moving
with
the
the
agenda?
I
put
two
little
discussions
here.
I
really
wanted
to
talk
about
now
that
we
have
the
rust
hostos
with
the
OTP
feature,
parody,
we're
running
components
we
are,
you
know,
be
able
to
use
things
like
Wazi
HTTP,
really
exciting
stuff
in
the
webassembly
world.
When
are
you
all
actually
going
to
be
able
to
use
it
minus
doing
what
I
did,
which
was
just
run
from
you
know,
run
from
Maine
in
GitHub
and
what
we're
looking
at?
A
On
the
on
the
maintainer
side,
we've
been
talking
about
an
initial
release
and
if
you
all
remember,
this
was
a
little
bit
back
in
the
day,
but
when
we
moved
to
OTP
for
the
initial
release
of
the
wasum
cloud
OTP
host,
we,
it
was
a
significant
enough
change
that
we
decided
to
do
not
1.0
but
significant
version
bump
to
signify
that
we've,
like
basically
significantly
changed
with
the
host-
and
you
know,
we've
played
with
a
couple
of
different
things
with
the
rest
host.
We
thought
about
releasing
v0.100.0
or
something
like
that.
A
We
played
with
releasing
a
V1,
Alpha
and
I.
Think
what
we've
decided
we
want
to?
We
want
to
release
something
that
signifies
that
we're
making
a
really
significant
release,
but
we're
not
going
to
call
it
1.0
yet,
and
so
someone
on
the
team
I
think
it
was
Lachlan
which
I
don't
know
if
he's
here
suggested
the
very
tongue-in-cheek
v78,
which
is,
if
you
turn
all
of
the
letters
in
Rust
into
numbers
and
then
add
them
together,
you
get
78..
A
This
is
very
tongue-in-cheek,
we're
having
a
lot
of
fun
here
in
the
open
source,
world
and
I.
Personally,
don't
have
any
reservations
about
this.
This
is
kind
of
funny
to
me
and
really
it
is.
It
is
a
temporary
bumping
to
get
us
to
to
signify
it's
a
major
release,
not
a
major
release,
but
a
large
minor
release
and
as
components
stabilize
and
we
create
our
SDK
and
we
have
a
stable
experience.
A
We're
pretty
confident
that
the
wasm
cloud
fundamentals
are
in
a
pretty
good
space
right
now,
I
think
there's
some
things
that
we
want
to
address
specifically
around
running
multiple
entity
versions
in
lattice,
which
is
an
RFC.
That's
in
the
wasm
cloud
was
on
cloud
repo
and
then
there
may
be
one
or
two
others
that
I'm
that
I'm
missing
in
the
RFC
side,
but
realistically
we're
really
happy
with
The
Primitives
and
the
the
concepts
that
Watson
Cloud
uses.
So
we're
rapidly
approaching
a
1.0
release
for
wasm
cloud.
A
What
we
really
want
to
be
sure
is
that
when
we
drop
a
1.0
that
the
experience
for
people
using
the
SDK
we're
going
to
be
able
to
iterate
on
that
without
a
major
breaking
release,
you
know
turning
around
and
doing
that
right
away.
So
I
would
love
to
offer
this
up
as
time
for
anybody
who
feels
serious
reservations
about
going
to
v78
has
any
other
suggestions
or-
or
things
like
that,
because
this
can
always
be
a
discussion.
A
All
right
silence
is
acceptance,
we're
doing
it
anybody's
welcome
to
chime
in
on
the
on
the
awesome,
Cloud
slack
as
well
or
or
on
YouTube.
We
are
probably
going
to
release
a
little
bit
of
a
tongue-in-cheek
block
for
this
one,
but
we're
just
having
a
good
time.
I
I,
don't
see
any
harm
in
that
all
right.
So
that
is
what
we're
planning
on
I.
Don't
think
I
have
a
timeline
for
this
right
now,
but
we
should
be
able
to
look
out
for
a
v78
release
here.
A
Pretty
soon,
we've
got
the
workflows
in
place
to
do
so
to
publish
you
know
the
the
different
architecture
binaries
for
the
host
that
we
already
support
with
OTP,
and
we
also
have
something
that
publishes
an
oci
image.
You
know
a
Docker
image
that
you
can
run
so
it's
going
to
be
effectively
the
same
experience
following
the
initial
release
of
the
rust
host.
Probably
soon
following
we
will
be
able
to
have
that
changed
in
wash
lib
to
download
and
run
the
rust
host.
Instead.
Now.
A
From
the
OTP
to
the
rest
host,
especially
with
wash
wash
up,
which
you
know,
there's
no
indication
here
that
we're
starting
the
wasm
cloud,
OTP
host
or
or
what
have
you,
but
it
is
going
to
be
something
that
that
will
likely
do
just
to
make
it
more
efficient,
just
to
use
the
most
up-to-date
versions
of
components
and
things
like
that,
all
right
last
last
stop
there.
A
Just
before
we
get
started
or
move
on
to
looking
at
the
roadmap
is
that
when
you
have,
if
you
have
a
rust
host
and
an
OTP
host
running
in
the
same
lattice,
meaning
they're
connected
to
the
same
Nats
connection,
you
know
you
can
have
actors
running
on
one
and
providers
running
on
the
other.
They
can
communicate
back
and
forth.
Just
fine,
like
I,
said
completely
backwards,
compatible
upgrade
here,
okie
dokie,
then.
The
last
thing
that
I
have
planned
on
our
discussion.
Part
for
today
is
just
taking
a
look
at
the
Watson
God
roadmap.
A
I
really
like
taking
a
look
at
this.
Each
Community
call
just
to
look
at
the
things
that
we're
working
on
this
is
I
guess
we
can
move
these
to
now.
We're
going
to
do
a
little
live
updating
of
the
road
map
too.
Taking
a
look
at
the
efforts
that
we
have
in
progress,
you
can
always
look
at
the
high
level
roadmap
for
the
now
column,
things
that
we're
working
on
like
right
now
and
then
next
to
take
a
look
at
what's
coming
soon,
but
the
work
status,
column
or
the
work
status.
A
A
I've
been
pleasantly
surprised
with
how
robust
this
this
view
is
in
GitHub
projects,
but
we're
currently
working
on
just
a
couple
of
things
left
in
the
Watsons
live
repository,
standardized,
Wazi,
Cloud
worlds
is
one
of
them.
I
know
that
we
kind
of
actually.
This
is
definitely
in
progress,
we're
definitely
working
on
HTTP,
key
value
and
I.
Think
some
things
have
been
done
for
blob
store
as
well.
A
Bailey
and
Taylor
feel
free
to
hop
in
if
I'm,
making
the
wrong
claims
here
and
then
defining
interfaces,
using
wit,
I
know
that
we're
really
strongly
into
this
RFC.
This
one
should
be
accepted.
Oh
Bailey
said,
is
that
you.
D
D
E
D
Roman's
I
think
that
was
yesterday,
I
had
a
couple
things
merge
for
wazzy,
key
value,
for
example,
and
so
there's
there's
going
to
be
some
more
changes
that
are
happening
in
those
linked
repos
before
we
can
consume
them
within
wasmcloud
and
if
we
do
consume
them
in
wasm
Cloud.
Now
some
of
these
have
our
versions
of
the
PRS
that
we've
put
up
Upstream.
So
we
can
keep
moving
forward.
A
Awesome
well
I'll,
see
if
see
if
we
can
get
any,
maybe
this
one
can
be
broken
out,
because
it's
kind
of
a
this
is
definitely
an
epic
level
of
an
issue,
but
we
can
start.
You
know,
check
boxing
these
or
crossing
these
off,
and
this
is
really
exciting,
because
we
have
a
lot
of
completed
work
and
this
blocked
column,
which
I
just
added,
is
a
a
way
to
signify.
What
you
know
depends
on
other
efforts.
A
The
Roswell,
clad
restos
being
launched
with
wash
up
really
just
depends
on
us
cutting
a
release.
You
know
the
the
fabled
v78,
so
we're
making
really
awesome
progress
on
our
roadmap
that
we've
got
laid
out,
which
is
through
quarter
three
quarter
four
of
this
year,
so
I
guess
we'll
just
we'll
just
keep
checking
in
here.
Anyone
who
is
tuning
in
new
who
hasn't
seen
this
document
on
our
website
I
would
definitely
recommend
taking
a
look
at
this
one.
A
It's
a
a
great
I
guess
textual
outline
for
the
things
that
we're
trying
to
do
right
now
and
then
the
GitHub
project.
What
I
was
showing
for
the
past
few
minutes
is
really
just
a
view
of
how
the
work
is
going.
So
you
can
see
our
number
one
goal
is
using
all
the
web
assembly
standards
as
possible.
So
it's
really
I
can't
say
it
enough.
It's
really
exciting
work,
we're
making
great
progress.
A
Actually
Bailey,
would
you
mind
keeping
an
eye
on
YouTube
just
in
case
there's,
there's
questions
there,
I
didn't
bring
it
up
ahead
of
the
call.
Oh.
A
Thank
you
all
right,
then,
the
where
was
I,
and
the
last
thing
that
I
have
to
talk
about
today.
I'll,
just
pull
it
up
through
the
the
last
week
of
community
notes
is
really
just
to
get
excited
for
wasmcon.
We
are
coming
up
on
this
rapidly.
It's
going
to
be
happening
next
week,
a
lot
of
us
on
the
Watson,
Cloud,
maintainer
side
and
tangently
people
who
work
at
cosmonic
are
going
to
be
here.
The
schedule
looks
packed
we're
going
to
be
running.
A
If
you
take
a
look
at
the
schedule,
we
have
many
talks
on
the
awesome.
Cloud,
maintainer,
side
and
Bailey
is
going
to
be
doing
things
like
a
a
panel
as
well
and
a
keynote
it's
kind
of
hard
to
keep
track
and
keep
reminding
everybody
of
these.
But
you
can
see
it
on
the
schedule
here
on
the
wasn't
con
site
and
then
cosmotic
is
also
going
to
be
sponsoring
a
napkin
sketch
to
apps
that
scale
Workshop.
This
is
going
to
be,
of
course,
because
wasn't
cloud
is
under
the
hood.
A
It's
going
to
be
a
very
wild,
focused,
very
wazzle,
Cloud
focused
Workshop,
where
we're
going
to
be
building
some
apps
together.
A
So
you
all
should
definitely
attend
if
you're
going
to
be
here
in
Seattle
I
believe
that
the
talks
are
going
to
be
live,
streamed,
I
think
we
keep
going
back
and
forth
on
that
on,
on,
where
they'll
be,
if
they're,
if
they're
here
and
just
a
quick
shout
out
I
wanted
to
share
it
I'm
going
to
show
you
because
I
know
that
it's
here,
but
it's
not
required
to
go
here
that
we,
if,
if
anybody
is
looking
to
register
for
wasmcon,
we
actually
cosmonic
has
a
sponsor
code
that
they
green
led
us
to
share
with
everybody.
A
So
if
you
are
looking
to
attend
wasmcon,
you
still
need
to
register,
even
if
there's
a
potential
an
online
tier
as
well.
Please
use
the
code
was
on
sponsor
30.
I
mean
it's
not
like.
We
don't
get
any
Kickback
from
this.
It's
just
30
off
for
you
all.
So
please
help
yourself
to
to
this.
If
you'd
like
to
attend
and
then
thank
you
Bailey,
the
here
is
the
virtual
attendance
guide.
A
We're
going
to
be
live
stream,
they're
going
to
be
live
streaming
to
the
YouTube
channel
looks
like
that
is
going
to
not
require
virtual
registration.
So
if
you
are
not
able
to
attend
in
person,
you
still
get
to
take
advantage
of
all
the
all
the
fun
talks.
So
we
hope
to
see
you
all
on
the
live
stream.
D
Yeah
so
it'll
be
on
the
YouTube
channel,
where
Liam
and
I
are
asking
the
Linux
Foundation
to
give
us
a
a
channel
ahead
or
a
you
know,
a
I
guess
a
link
ahead
of
time
so
that
we
can
start
sending
that
same
link
everywhere
versus
people
having
to
kind
of
fish
around
and
find
it,
but
yeah
I'm
really
looking
forward
to
it.
I
think
you
know
some
things
are
still
coming
together
for
it.
So
it's
very
exciting.
D
On
the
program
committee
side,
I'm
I'm
really
really
really
excited
about
the
thing
that
happens
on
Friday,
which
is
also
free
for
in
person
and
we'll
have
remote
stuff,
and
when
I
talk
about
things
coming
together,
I
think
AV
Liam
is
gonna,
be
helping
hook
up
mics
and
things
so
that
this
works
well.
For
the
remote
side
of
things
for
the
bytecode
alliance
caponatize,
the
world
event,
quick,
I.
F
Think
we
came
up
with
another
strategy
for
it
we
actually
have
switched
out
of
three
rooms
that
the
Microsoft
Center
is.
Our
current
is
our
current
plan,
but
it's
definitely
coming
in
hot,
but
there's
we've
got
an
awesome
turnout,
I
think
we've
got
right
now
close
to
90
people
registered.
So
we
should
have
a
really
really
good
event,
and
you
know
I
mean
there's
a
there's
a
lot
for
a
free
event.
You
know
you
get
fed
twice,
and
you
know:
snacks
and
drinks
and
stuff
and
a
cool
t-shirt
and
there's.
F
That
doesn't
sell
it
and
it's
a
Bella
canvas
tri-blend.
We
don't
really
want
to
go
down
the
T-shirt
route.
I'm
going
to
get
too
excited
are.
F
D
Right,
T-shirt,
bribes,
I'm,
gonna,
I'm
gonna,
get
it
reported
for
bribery
here,
but
yeah,
no
I
I'm,
really
looking
forward
to
having
a
collaborative
hackathon.
It's
not
a
competitive
one.
The
idea
is
that
there's
there's
a
lot
in
the
component
space
to
learn,
so
we're
going
to
be
running
a
workshop
from
Alex
he's
going
to
be
working
through
a
tutorial
there,
but
then
we're
also
going
to
be
working
on
the
language,
various
language
ecosystems.
D
So
if
you
want
to
write
a
go
component
or
a
JavaScript
component,
rest,
one,
those
are
all
fair
game
and
then
there's
also
a
documentathon
so
that
we
get
better
documentation.
We
we
actually
are
getting
pretty
pretty
far
along
on
the
dock.
Thanks
to
Kate
golden
ring
and
Ivan
they've
been
leaning
that
up
in
the
bytecode
alliance
space,
which
is
really
good,
and
then
we
also
have
some
a
ton
of
docs
that
have
been
going
into
the
cosmotic
side
too.
A
That's
super
exciting
stuff,
and
just
for
anybody
I
know
the
the
terminology
can
get
mixed,
sometimes
because
you
know
we're
running
web
assembly
components
and
in
wasm
cloud
and
that's
what
you'll
be
building
when
you
use
like
the
new
actor
sdks
and
things.
But
despite
code,
Alliance
hackathon
is
completely
around
pure
webassembly
components,
and
so
you
know
it
can
be
used
with
with
any
runtime
that
supports
webassembly
components.
A
It's
really
exciting,
like
the
we
talked
about
it
a
little
last
week,
but
I
know
that
different
groups
come
to
the
Community
College
time
the
prospect
of
being
able
to
find
a
library.
That's
that's
written
in
Rust,
maybe
not
implemented
in
other
languages
and
turn
that
into
a
webassembly
component,
which
then
becomes
something
that
you
can
interact
with
and
use
from
go
from
Hey
python
after
the
component's
highest
Pi
announcement
yesterday
and
see
any
anything
they
can
use.
A
The
webassembly
component
model
is
super
exciting
and
I
can't
begin
to
call
out
everybody's
names
who
have
worked
on
it
over
the
last
few
years,
but
a
huge
shout
out
to
everybody
in
the
webassembly
standard
space
who's
been
who's
been
working
on
this.
As
as
Bailey
said,
it's
culmination
of
years
and
years
of
hard
work.
A
Right
here
let
me
go
ahead
and
prop
that
up
Bailey,
because
I
think
that's
completely
worth
worth
showing.
This
was
last
night
right
that
you
all
ran
the
or
no
I
guess
it
was
just
yeah.
D
It
was
last
night
I
got
to
hang
out
with
Joel.
It
was
like
nine
o'clock
my
time,
if
you
jump
like
halfway
through
you,
can
see
where
he's
running
it
yeah
there's
the
Matrix
math,
it's
real
y'all.
Another
cool
thing
that
he
highlighted
is
that
the
generated
bindings
have
the
annotations
in
them,
so
that
you
also
get
some
type
checking
which
is
really
nice
for
python.
So
watching
him
do
it.
D
It
looked
really
ergonomic
compared
to
a
lot
of
the
other
languages
that
are
in
the
scripting
space
they're
very
much
in
the
I
call.
It
hold
your
mouth
right,
but
you
might
consider
it
like
standing
on
one
foot
trying
to
make
it
all
work
this.
This
actually
looked
pretty
nice.
The
developer
experience
was
not
so
bad,
so
it's
the
first
cut
of
everything.
So
you
know
how
it
is,
but
yeah
I
really
I
really
encourage
folks
who
are
excited
about
Python
and
python
experts
to
help
us
keep
evolving.
It.
A
Yeah
this
is
this
is
super
cool,
hey
I
would
rather
use
Python
than
Russ
to
do
some
Matrix
math,
but
maybe
that's
just
me.
A
All
right,
well,
I,
think
that
that's
all
that
we
had
planned
for
the
the
regular
Community
agenda.
You
know
demos
discussions
going
over
the
roadmap
all
that
stuff
again,
a
lot
of
us
have
been
really
heads
down
on
future
work
and
getting
demos
and
talks
together
for
wasmcon,
which
is
such
a
such
an
exciting
culmination
of
effort
on
on
our
side.
So
really
looking
forward
to
seeing
people
seeing
people
there
and
you
know
getting
the
talks
done.
I
think
now
is
a
great
time
for
just
open,
Community
call.
A
So
any
questions
in
the
webassembly
community,
broader
was
on
cloud
Community,
and
things
like
that
would
be
would
be
perfect.
Hey
I,
I
see
one
that
just
went
through
in
the
chat.
Actually
yortis
and
Bailey
all
are
going
back
and
forth
you're
looking
for
documentation,
you
said.
B
Yeah
I
think
like
personally
for
me
like
there
is
a
real
tricky
situation
for
what's
on
cloud
itself,
is
a
I
came
with
trying
to
find
a
solution
to
a
problem,
but
now
I've
realized
that
wasum
is
a
way
to
get
there
and
I
learned
through
Western
Cloud.
So
now
it's
too
many
campuses
to
understand
too
many
things
to
know
what
is
what's
on
cloud
related?
B
What
is
actually
the
you
know,
Upstream
work
like
with
now
that
is
working
going
on,
and
you
know
how
to
how
to
put
all
that
those
things
together,
right
and
and
just
beyond
that
be
able
to
collaborate
and
contribute
to
the
to
the
prayers
it
feels
like
the
code
is
there
we
read
the
code
and
you're
able
to
eventually
figure
out
everything
you
could
contribute,
but
you
know
for
me
personally:
I
would
like
to
see
like
more.
B
You
know,
work
put
into
the
documentation
because
sometimes
for
me,
for
example,
like
I,
have
the
programming,
skills
and
I
understand
more
or
less
fundament
architecturally.
What
is
going
on,
but
way
too
many
tools
all
over
the
place.
For
me
to
just
learn,
say:
hey
I.
Have
this
task
I
can
help
right
now,
but
I
just
don't
have
the
time
to
learn
all
of
them
which
I
can
learn
as
I
go,
but
there's
no
a
cohesive
documentation
that
would
more
or
less
help
me
with
that.
D
Yeah,
it's
it's
a
big
space
and
we
totally
recognize
this
as
a
major
Gap.
So
there's
the
component
docs
book
and
it's
got
issues
filed
for
all
the
things
that
we
want
to
document.
So
that's
like
a
pretty
good
like
getting
started
kind
of
task
list.
That's
enumerated.
D
I
also
just
wanted
to
call
out
the
the
preview
2
roadmap
even
has
like
just
docs
as
like
one
of
our
major
epics
that
we
have
to
do
before.
We
say
just
even
the
lazy
side
of
this.
That's
that's
where
this
train
starts.
D
It
starts
in
the
webassembly
org,
with
the
the
YZ
and
component
model
specs
and
then
and
then
it
goes
into
bycode
alliance,
with
some
common
shared
tooling
and
then
and
then
it
gets
to
Asin
Cloud
so
easily,
spanning
three
different
GitHub
orgs
is
pretty
tough
and
digging
in
is
kind
of
hard
up
until
I
think
now-ish.
D
Before
this,
you
really
kind
of
had
to
be
it
in
it,
living
and
breathing
it
every
day
to
know
where
everything
is
happening
and
flying
around,
because
there's
so
much
change
at
every
layer
of
the
sack.
But
that
was
the
goal
of
the
componentized.
The
world
event
was
to
like
okay,
let's,
let's
stake
in
the
ground.
This
is
the
day
when
we
invite
other
people
to
come
along
and
try
to
see
what
we
made
and
describe
it
to
the
other.
Outside
people
can
start
building
with
it.
G
I
know
that
the
way
I
approach,
this,
of
course,
I'm
coming
from
more
of
the
architecture,
nuts
and
bolts
kind
of
background,
rather
than
on
the
the
front
end
component
side,
but
the
way
I
approached
this
was
actually
learning
Nats
first,
so
I
downloaded
Nats
on
its
own.
G
This
is
in
the
last
couple
of
weeks,
so
I'm
still
very
much
a
newbie
on
this
guys,
but
it
really
helped
me
to
actually
really
get
gnats
under
my
belt,
because
then,
when
you're
talking
about
all
the
end
keys
and
the
way
things
communicate,
and
things
like
that,
it's,
like
oh
okay,
I,
see
what
this
lays
on
top
of
and
I'm
just
now,
starting
to
actually
get
into
the
okay.
What
is
the
what
I'm
doing
and
and
things
like
that,
but
that
that
helped
me
along
quite
a
bit
was
just
writing.
G
Writing
some
quick
process
stuff
to
do
gnats
back
and
forth
and
go
okay,
I
get
it,
and
then
that
took
the
whole
complicated
communication
aspect
out
of
this
sort
of
out
of
the
out
of
my
space,
where
it's
like.
Okay,
I
get
that,
and
now
it's
like.
What
is
what
are
they
doing?
On
top
of
it,
so
I
know
that
that
direction
helped
me
a
lot
yeah.
B
Yeah
I
mean
for
me:
I
knew
nuts
before
Dave,
but
it's
more
like
when
I
I
wanted
the
over
even
sourcing
provider,
which
one
already
exists.
But
it's
like.
Okay,
okay,
this
Mighty
thing
I
have
to
learn
her
first,
that
was
a
figure.
I
had
to
figure
that
out,
like
okay,
how
how
many
tools
and
in
what
order
actually
have
to
run
in
order
to
compile
things
or
download
the
property,
like
things
like
that
is
like
all
right,
I,
just
I'm
reading
code,
that
it
makes
sense
in
isolation,
but
how
they're.
G
A
Yeah,
there's
there's
always
going
to
be
a
really
interesting
balance
that
we
have
to
strike
on
the
waslam
cloud
side
and
and
I
really
hope
that
we
can
help
contribute
to
the
webassembly
documentation
as
well
from
the
from
the
wasm
cloud
side,
like
a
person
who
comes
to
the
project,
if
we're
doing
everything
perfectly,
the
developers
that
use
wasmo
cloud
shouldn't
have
to
deal
with
the
implementation
details
of
properly
building
a
webassembly
module
and
linking
it
to
two
components
and
additionally,
the
the
things
you
get
with
naps
like
service,
Discovery
and
making
sure
things
fail
over
and
like
our
whole
goal
is
to
get
users
to
not
have
to
care
about
that,
and
we
always
want
to
be
able
to
have
like
links
out
for
people
who
want
to
know
how
it's
actually
working
to
to
go
and
understand.
A
It.
I
think
that's
a
key
point
that
we
need
to
keep
in
mind
and
and
I
know
that
our
initial
document
station
is
going
to
be
tailored
to
leaving
those
things
off
until
people
want
to
go
digging
for
for
more
information,
I
I
know
you
put
a
comment
in
there
and
I'll
just
call
it
out,
because
I
know
people
are
got
their
hands
up
too.
A
I
think
that
that
is
also
a
great
lens
to
look
at
it
through
the
contributor
lens
to
not
just
the
the
consumer,
because
a
lot
of
our
a
lot
of
our
documentation
is
I
mean
I.
I
can't
lie
it's
very
robust.
It's
just
very
geared
toward
the
consumer
of
wasm
cloud,
whether
it's
wadham
or
you
know,
being
or
or
you
know,
developing
actors,
and
things
like
that.
A
E
Yeah
I
think
I
just
wanted
to
kind
of
give
some
context
here
in
that
you
know
we
started
doing
this.
This
wasn't
Cloud
stuff
years
and
years
and
years
ago
feels
like
forever,
and
you
know,
when
you
start
on
a
pre-release
of
a
pre-release,
then
you
know
we
had
to
basically
do
everything
ourselves
because
none
of
the
foundational
layers
existed.
So
we
had
to
build
our
own
way
to
talk
to
the
web
assembly
modules.
We
had
to
build
our
own
clustering
and
stuff.
We
had
to
build
everything
from
scratch.
E
We
were
building
the
bridges
as
we
were
walking
across
them
and
you
know
so
what
the
produced
was
a
bunch
of
layers
and
gradually,
as
the
webassembly
ecosystem
has
been
maturing
and
as
the
component
model
has
been
maturing,
we've
been
scraping
away,
our
own
layers
that
we
started
a
while
ago
and
just
using
the
standard
stuff.
So,
like
Brooks,
said
the
ultimate
goal
is
you
should
just
be
able
to
walk
up
to
a
compiler,
create
a
off-the-shelf
webassembly
component
and
throw
it
into
wasmcloud
and
everything
works.
F
Yeah
I
think
that's
the
right,
that's
absolutely
the
right
place
to
keep
the
focus,
and
it's
not
just
you
know,
cosmonic
and
wasmcloud
that
are
heading
in
that
direction.
You
know
when
you
look
at
the
goal
of
platform
engineering
when
you
look
at
the
goal
of
you
know:
service
mesh,
it's
to
pull
capabilities,
it's
the
the
spinal
abstraction
is
the
library
layer
that
we
have
in
applications,
and
that's
where
you
know
95
of
the
source
code
is
and
it's
80
of
the
work
is
just
boilerplate.
F
You
know
dozens
of
different
industries
that
we've
that
we've
worked
with
and
then,
when
you
look
at
what
you
know
and
I
think
the
sort
of
obvious
implication
from
that
is
is
that
this
Home
Depot
model
cloud
computing
is,
is
you
know,
kind
of
threatened?
You
know
that
is
what
we
used
to
do
like
we
used
to
build
data
centers
like
we
used
to
deploy
physical
machines
like
we
used
to
do
all
of
you
know.
F
You
know
all
of
these
individual
tasks
and
just
raising
this
abstraction
up
even
higher
is
you
know
where
fastly
and
cloudflare
arguably
already
are
where
cosmonic
is
working
to
deliver
on
I
think
even
a
next
generation
of
that
outside
of
a
closed
loop.
You
know
we
give
you
the
ability
to
deploy
your
own
faster,
your
Cloud
flare,
you
know
type
functions
and
mash
across
your
own
infrastructure
and
edges
and
I.
F
Think
it's
a
super
fascinating
time
to
to
have
the
privilege
to
participate
in
the
evolution
of
this
next
epic
attack
and
the
artist
to
speak
to
your
point.
There
is
then
definitely
room
for
those
of
us
that
are
working
on
the
complexities
of
swallowing
the
stack
you
know
like
what
does
it
look
like
for
the
users
will
just
get
this
high
level
view
of
just
bring
my
business
logic
and
the
platform
provides,
but
there's
those
of
us
that,
as
Kevin
have
mentioned,
have
been
struggling
with
the
okay.
F
How
what
do
we
make
work
today
and
what
works
right
now
and
what
I
really
appreciate
is
you
know,
with
our
full
Embrace
of
Standards
the
Watson
Cloud
rust
host?
That's
there.
Now
that
that
is,
for
all
intents
and
purposes,
aligned
with
the
standards
as
they
are
today,
there's
still
a
few
things
to
land
there
that'll
iterate
through,
but
you
know
we're
there
I
it's
an
amazing
world,
because
we're
focused
as
a
community
at
the
right
place.
Bailey
mentioned
that
you
know.
F
Joel
dice
was
working
on
componentized,
Python
and
what's
amazing
about
our
focus,
is:
is
that
there's
already
componentizer
us
and
Jayco
componentized
JavaScript
and
all
of
those
tools
create
an
artifact
a
component?
That's
completely
portable
across
other
platforms
and
systems,
and
that
is
the
Real
Alignment
that
we
needed
as
an
ecosystem.
So
we're
not
competing
on
like
adding
language
sdks
or
any
of
this
crap.
We
can
now
start
building
around
this
Central
artifact
called
the
component,
that's
portable
everywhere,
and
that's
that's
the
dream.
F
That's
what
developers
want
and
that's
what
that's,
what
we're
I
think
that's
we've
already
built.
So
it's
an
exciting
time.
A
Hey
Jordan
I
know
that
you're
a
little
short
on
time
here,
but
you
sent
something
very
casually
into
the
chat
that
I'm
trying
not
to
freak
out
about.
Do
you
want
to
do
you
want
to
share
that?
Are.
H
You
free
you've
already
shown
you've
already
shown
the
rust
one.
That's
freak,
outable,
yeah,
so
I'll
to
Liam's
Point,
actually
of
everything
you
just
said
about
things
being
like
super
portable.
How
do
I,
okay,
I'm
gonna,
try
to
share
my
whole
screen
again,
so
everyone
can
see
my
bills,
let's
see
so
we
got
the
the
KV
counter
and,
and
so
everybody's
seen
this
right,
and
so,
while.
I
H
Absolutely
So
like
so
this
is
a
small
program
in
wasmo
Cloud
that
takes
the
HTTP
server
provider
and
the
redis
provider.
You
send
it,
you
send
it
a
a
get
it
increments,
your
counter
stores
it
in
redis
and
then
you
can
do
things
like
different
different
key
names,
so
it's
fun,
and
this
this
example
has
been
around
for
a
while.
H
H
So
Victor
was
able
to
report
Port
it
to
a
componentized,
rust
and
I
was
able
to
copy
all
his
code
and
Port
it
to
a
container
or
a
componentized
go,
and
it's
very
interesting.
The
codes,
the
codes
of
it
verbose,
the
the
co-generation,
creates
some
really
long
names
which
the
the
go
Community
is
is
working
on.
You
know
slimming
down,
but
what
I
find
extremely
interesting
is
the
go
module
when
we
open
it,
there's
nothing
there.
So
there's
nothing!
Wasm,
Cloud
specific!
There's!
Nothing
web
assembly
specific,
there's,
there's
nothing
which
I
find
mind-blowing.
H
What
we're
actually
importing.
It
is
a
few
pieces
of
the
standard
library
in
our
Cogen,
and
our
Cogen
is.
Let
me
go
back,
is
nothing
more
than
the
bytecode
alliances
whip
buying
gin
tiny,
go
tooling,
so
yeah
I,
just
I,
wanted
to
share
that,
because
I
know
Bailey
has
been
preaching
it
for
months
and
months
and
I
never
really
clicked
to
me
until
I
wrote
this
and
then
looked
at
this
and
realized
it's
extremely
portable,
because
it's
got
there's
nothing
there.
H
C
H
A
Is
this
is
super
awesome,
I,
regret
being
heads
down
enough
on
some
of
the
like
host
stuff,
that
I
haven't
seen
this
and
like
even
the
like
the
key
value
counter,
because
this
is
huge.
It's
doing
exactly
what
we
want
to
do
as
a.
A
F
We
have
if
anybody
still
needs
to
register
for
bacon
it's
free
for
wasencon.
We
do
have
a
discount
code,
we'll
throw
that
into
slack.
You
know
30
off
or
something
like
that,
for
anybody,
that's
interested
and
if
you
can't
make
it
it
will
be
streamed,
live
online
I'll.
Make
sure
that
we
do
some
calls
to
action
in
the
Watson
Cloud
slack.
D
Many
of
those
did
we
solicitly.
F
We
you
and
I
put
15
of
those
on
the
schedule
that
we
asked
like
after
you
know,
to
sort
of
like
design
the
schedule,
and
we
really
spent
a
ton
of
time.
You
know
like
reaching
out
to
folks.
We
know
that
are
like
maybe
working
comp.
You
know
like
like
at
a
startup
or
just
cool
things
that
we've
seen
like
red
panda
or
car
Carl
severe
will
be
there
sharing
some
of
his
work
that
he's
doing
around
distributed.
F
F
You
know,
so
we
I
think
we
spent
a
lot
of
time
on
it,
but
we
did
have
over
100
submissions
or
around
100
submissions
even
before
we
solicited,
and
it
was
so
hard
to
pick.
You
know
to
narrow
it
down
this
year.
I
don't
know,
I
mean
it
I,
don't
know
how
many
tracks
we're
gonna
have
to
have
next
year.
You
know
I
mean
60,
80.
I
mean
it
just
blew
up,
Blossom
is
everywhere
and
the
customer
talks
we've
got
Bosch
on
stage.
F
We've
got
Siemens
on
stage,
we've
got
marsk,
you
know
the
biggest
shipping
containers
in
the
world.
We've
got
bite,
dance
on
stage,
we've
got
Adobe,
we've
got
Shopify,
we've
got
Adobe
I
mean
we've
really
got
a
Who's
Who
and
I'm
a
little
disappointed
about
something
that
we
missed.
You
know
we
that
you
know
folks
just
didn't
work
out,
scheduling
wise,
but
there's
still
a
ton
of
great
more
stories
to
tell.
But
we've
got
stories
that
have
never
been
told
before
so
it'll
be
a
lot
of
fun.
D
Supplement
a
web
assembly
inside
their
browser
runtimes,
but
you
know,
make
them
fight,
I,
don't
know:
I,
I'm,
I'm,
really
looking
forward
to
that
conversation
and
having
Conrad
Watt
on
there,
who
is
one
of
the
co-chairs
of
the
web
assembly
standards.
I
think
it'll
be
a
really
interesting
discussion
really
getting
into
the
I.
Think
the
nuts
and
bolts
of
how
to
implement
webassembly
from
a
runtime
perspective.
A
We
had
one
more
comment
in
YouTube,
which
I
I
tried
to
respond
to,
but
I
I
think
could
be
a
great
way
to
kind
of
close
out
this
Community
call.
You
know
it
was.
It
was
permanent.
You
asked
it'd
be
really
interesting
to
see
what
it's
like
to
take
an
existing
project
and
convert
it
to
use
a
componentized
model
like
if
a
node
project
uses
Docker.
You
know
Docker
compose.
A
How
do
we
end
up
converting
that
to
webassembly,
and
you
know,
pick
language
of
your
choice
and
back
end
of
your
choice
and
all
that
stuff
I've
got
some
rudimentary
thoughts,
but
Kevin
was
quick
on
the
hand
and
I
think
Bailey
unmuted,
so
I'll.
Let
them
talk
my.
E
Avatar
has
lower
latency
than
I.
Do
so
I
got
to
the
hand
quicker
yeah,
I
guess
it's
been
kind
of
in
the
back
of
my
head
for
a
while,
but
I've
got
plans
for
like
a
series,
either
a
blog
posts
or
videos
or
whatever
that
you
know
goes
from
takes
one
or
more
sample
microservices
and
converts
them
into
a
wasm
cloud
application.
And
you
know
you
can
kind
of
take
a
look
at
the
before
and
after,
and
you
know
why
components
are
better
and
so
on.
A
Alrighty
folks,
I
think
we're
getting
to
the
top
of
the
hour
here
unless
there's
any
other
questions,
things
that
we
wanted
to
share
here,
I
think
we
can
go
ahead
and
call
this
one.
A
Oh
well,
you
already.
She
had
a
good
question,
you're
wondering
how
to
share
types
between
modules
and
you're,
wondering
what
tools
to
use
to
compile
those
things
per
se.
Yeah.
B
I
always
see
the
the
last
time
examples
in
every
programming
language,
here's
how
you
load
the
module
but
like
okay,
how
you
produce
that
module
I
have
to
be
put
in
the
Watson
module
myself,
because
pretending
that
I
know
what
I
was
doing
and
I
could
not
figure
out
what
tools
I'm
supposed
to
be
using
for
that,
especially
inside
rust
and
like
a
Golan
for
example,
or
JavaScript
yeah
showed
like
the
compilation
tours
browser
like
I.
Don't
have
the
browser,
one
I
don't
want
the
browser
go
ahead.
D
I
I
would
say,
check
out
Jordan's
KV
counter
example
that
he
posted
here
where
he
shows
defining
the
wit
definition.
He
shows
how
to
use
some
of
the
tools
like
with
binding
is
one
of
the
key
tools
to
generate
The
Language
by
needs
based
on
the
wit
definition
and
width
stands
for
webassembly
interface
types,
and
so
those
are
basically
the
types
for
components
to
talk
to
each
other
between
components.
But
it's
also
the
way
for
the
host
to
know
what
types
are
available
in
the
component.
D
So
it's
also
part
of
the
glue
that
you
need
from
a
host:
okay,
the
web
assembly
runtime
and
your
webassembly
module.
So
yes,
that's
the
way
we've
got
a
lot
of
stuff
coming
in
real
hot,
because
we're
trying
to
get
it
all
done
for
the
conference
when
I
say
we
here.
D
This
is
me
wearing
my
wazzy
co-chair
hat
and
bike
coat
Alliance
director
hat
we're
we're
trying
to
get
a
registry
stood
up
so
that
you
can
push
your
like
your
wit
definitions,
basically
to
a
registry,
so
that
you
can
share
it
through
that
registry
API
and
so
there.
Some
of
that
tooling's
evolving
is
what
I'm
trying
to
say,
but
if
you
see
wit-
and
you
see
Whit
binding-
that
that
is
the
way.
F
You
know
what
I
would
love
is
you
know
the
week
after
wasmocon
Bailey?
What,
if
the
two
of
you
guys
hopped
on
Twitch
together
and
you
just
did
like
like
a
little
tutorial.
Could
we
do
that?
Would
you
two
be
open
to
that.
F
I
think
I
don't
know
yeah
yeah
I
mean
we
could
just
start
with
the
like.
You
know:
what
are
you
trying
to
do
and
just
go
build
some
stuff
together,
I
mean
I
can
always
show
up
and
ask
dumb
questions.
You
know,
there's
you
know
if
you
always
just
need.
You
know
like
the
generally,
when
you
have
like
a
talk
show
you
know,
you've
got
like
the
expert
and
then
the
color
commentary,
who
usually
just
pretends
to
be
an
idiot
in
this
case,
is
great
because
I
actually
am
one.
So
you
know.
G
G
An
audience
in
that
that
show
too
you're.
C
F
I
think
we
might
have
to
have
you
on
to
show
off
some
of
the
stuff
you've
been
building.
I,
know
you're,
doing
a
lot
of
cool
stuff
and
and
I
don't
know
if
I,
if
it's
too
inappropriate
but
I
know
you've
got
something
coming
up
at
TM
Forum,
that
is
in
Copenhagen
in
September,
I
think
September,
the
16th.
You
know
you
have
something
where
I
think
you're
going
to
be
featuring.
Wilson
Cloud
right.
I
Yeah,
so
we've
got
a
web
assembly
focused
Catalyst
project.
I
I
So
we're
running
real
code
that
I
I
posted
a
picture
of
some
Hardware
that
we're
taking
there
that
was
sort
of
running
it
locally
on
little
arm
servers
and
and
and
and
then
running
the
Telco
workloads
that
they're
used
to
running
in
the
data
centers
and
spending
a
lot
of
money
on
an
energy
and
whatever
and
so
really
showing
hey.
This
is
exciting.
I
This
is
new
and
this
is
really
Edge
focused
and,
and
it's
it's
green,
all
the
you
know
hits
all
the
hot
buttons
so
I
think
it's
going
to
be
quite
a
successful
event
after
or
during
I
would
love
to
share
with
with
as
many
as
people
as
possible.
What
we've
actually
done
so
yeah,
that's
19
through
the
21st,
so
some
somewhere
in
that
time
frame.
D
D
We'd,
have
it
I've
been
living
and
breathing
a
lot
of
this
stuff
and
it's
past
time
to
make
it
digestible
for
people
who
are
who
want
to
jump
on
and
start
contributing.
Yeah.
B
And
please,
by
the
way,
feel
free
to
ask
me
to
try
to
document
it
and
whatnot.
You
know
I
just
I.
Just
hopefully
you
don't
mind
that
I'm
asking
questions
and
like
how
you
do
this
yeah,
because
Yeah
It's,
Tricky
and
I
I
personally
gonna
try
to
figure
out
how
to
put
all
this
thing
together,
like
as
a
Roma.
Okay,
what?
What
is
your
role?
What
are
you
trying
to
at
what
level
you're
dealing
with?
Are
you
going
in
the
application,
development
or
infrastructure
side
of
things
or
like
the
runtime?
B
A
Yeah,
this
is
going
to
be
whether
we,
whether
we
do
a
an
extra
live
stream
or
we
just
I-
could
totally
see
us
doing
like
you
know,
breaking
down
the
components
series
and
in
the
community
call
here
like
we've,
got
a
lot
of
great
opportunities
for
for
actually
demoing
this,
and
you
know
talking
about
it
here
in
the
community-
call
because
it's
going
to
be
so
core
to
the
the
wasam
god
community.
A
So
looking
forward
to
that,
I
know
we're
at
the
top
of
the
hour
here,
so
I'll
go
ahead
and
close
up
the
live
stream
just
so
that
we
can
kind
of
wrap
it
up
here
for
folks
that
are
moving
on
to
their
next
2PM
thing,
but
really
appreciate
everyone
for
for
coming
to
the
community
call
today,
especially
the
artists
who
is
new
to
the
community
call,
but
I
can
totally
see
coming
to
the
Future
ones,
so
really
excited
for
that.
A
Thanks
to
everybody
who
come
or
came
on,
Twitter
YouTube
all
the
things,
but
just
a
quick
heads
up
that
next
week
we
will
be
at
the
conference
out
at
wasn't
con,
so
the
community
call
is
likely
to
be
either
abbreviated
or
loud
depending
on
if
we
do
it
at
the
booth
or
in
the
back
room
or
something
like
that.
But
you
know
some
of
us
will
probably
get
together
in
a
room
and
and
say
hey
depending
on
where
we're
where
we
are
with
the
workshop
and
talks
and
all
that
stuff.