►
From YouTube: wasmCloud Community Meeting - 12 April 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
Okay,
hello:
everyone
welcome
to
the
wasmcloud
community
meeting
for
Wednesday
April
12th.
We
have
got
a
little
bit
of
a
short
agenda
for
today,
but
still
pretty
exciting.
Let
me
go
ahead
and
share
that
so
taking
a
look
at
our
agenda
for
today,
Taylor
and
I
are
going
to
do
a
little
bit
of
an
update
on
the
wadham
progress
report,
just
a
general
check-in,
as
we
are
rapidly
adding
a
bunch
of
features
to
the
version
4
of
wadham,
which
is
something
is
coming
along.
A
Really
really
quick
and
I
have
actually
gotten
to
start
working
on
it,
which
is
pretty
fun
and
I'll
talk
about
kind
of
what
I've
been
working
on
too
and
then
we're
going
to
talk
about
something
that
happened.
I
think
it
was
yesterday.
Let
me
check
the
time.
No,
that
was
when
it
was
created.
It
was
closed.
A
I
think
yesterday,
but
golang
officially
merged
Wazi
preview,
1
support
into
the
main
branch
of
the
language
repository
which
is
really
exciting,
so
I'll
hold
off
on
any
any
more
discussion
on
that
until
later,
let's
start
out
with
the
wadham
progress
report,
so
Taylor,
do
you
want
to
give
kind
of
a
brief
overview?
You've
been
doing
a
lot
of
work
in
here,
I'm,
actually
halfway
through
reviewing
your
PR,
but
of
some
of
the
things
that
have
gone
over
on
gone
in
over
the
past
week
or
so.
B
Yeah
so
I
mean
I
can
demo
this.
If
people
really
want
to
see
it
I
know
some
people
really
like
getting
excited
about
it,
but
we
can
see
it
down
the
line
we'll
we'll
just
go
through
the
the
quick
overview
we're
currently
on
track
to
get
essentially
the
like
0.4.0
Alpha
out
by
the
end
of
the
week
we
still
before.
We
fully
call
it
off
and
like
ready
to
go.
B
We're
gonna
do
some
work
over
the
next
week
or
two
after
kubeconics
we're
gonna
be
busy
during
the
kukan
week
next
week
of
tying
up
some
docs
making
sure
it's
integrated
into
wash
all
those
things
before
we
Market
a
fold
0.4
so
just
but
like
you're,
going
to
be
able
to
like
try
this
out,
get
it
and
get
it
used
and
you'll
see.
We've
we've
done
a
whole
bunch
of
stuff
around
like
making
sure
we
store
manifests.
We
notify
things
we
automatically
observe
lattices.
B
B
If
you're
running
everything
on
the
same
Nats
cluster
with
the
same
set
of
types
of
credentials,
you
can
run
multiple
lattices
and
it'll
automatically
pick
them
up
and
also
has
multi-tenant
support
if
you're
running
something
even
more
complex
and
then
in
the
open,
PRS
you'll
see
that
Brooks
is
currently
working
on
the
actual,
like
Logic
for
scaling
actors,
so
I'll
be
doing
it
for
providers
and
Link
desks
next
and
I'm
actually
going
through
a
re-review
of
this
PR
as
well.
B
Right
now
and
like
right
before
this
meeting,
that's
what
I
was
doing
of
being
able
to
to
actually
do
the
scaling
logic
and
then
I'm
doing
the
last
little
bit
of
glue
and
we're
going
to
have
it
all
out,
hopefully
by
this
right
and
then
also
big,
shout
out
to
Stephen
who
graciously
took
on
some
of
the
grunt
work
and
is
working
on
the
pipeline
so
that
we
have
build
pipelines
ready
to
go
so
there's
it's
been
really
exciting
to
see
people
from
the
community
getting
involved.
C
B
Yeah,
that's
where
we're
at
right
now
just
wanted
to
give
the
update
next
week.
I
probably
won't
be
in
this
call,
because
we're
going
to
be
at
kubecon,
but
the
week
after
I
will
demo
this
in
its
full
functional
Glory,
though
you'll
probably
get
a
demo.
If
you're
in
the
wasm
cloud,
slack
you'll
get
a
demo
in
there
recorded
video
demo
once
we
get
this
working
because
Brooks
and
I
are
excited
to
get
it
done
and
honestly
once
we
get
this
done.
B
B
But
once
we've
gotten
this
out-
and
this
has
merged
into
main
we're
into
the
state
where
anyone
who
wants
to
improve
things,
add
new
types
of
like
fixes
to
the
scaling
algorithm
talking
about
like
doing
the
different
things
for
scaling
or
maybe
even
creating
a
new
one.
B
C
B
Also
means
in
case
you
weren't
here
when
we
first
talked
about
how
we
were
going
to
architect.
This
everything
is
a
library
so
right
now
we're
working
off
of
a
fork
of
the
control
client.
So
I
could
use
my
a
new
version
of
nats,
but
once
that's
that's
gone
and
we're
using
all
normal
published
crates
we're
going
to
be
publishing
Witham
as
a
crate
as
well.
B
So
all
of
these
parameters
we
used
you're
not
like
required
to
use
wadam
to
do
any
type
of
scheduling
or
other
things
for
for
Watson
Cloud.
All
of
these
Primitives.
You
can
actually
take
and
use
to
write
your
own
things
if
you,
if
you
have
the
desire
so
every
basically
all
the
all
the
components
we're
building
this
out
of
not
want
some
components
to
be
clear.
B
B
Excited
to
get
it
out
and
show
it
to
people
coming
up
here
soon.
A
Yeah
happy
to
happy
to
talk
about
the
you
know,
some
of
the
specific
parts
of
the
library.
If
anybody
is
interested
I
think
Taylor
hit
the
nail
on
the
head.
I
had
a
PR
that
went
in
I
think
it
was
like
four
days
ago
that
defined
this
like
nice,
looking
trait
for
creating
scalars
and
then
now
this
new
PR
that
I'm
putting
in
is
completely
breaking
that
whole
contract.
A
So
it's
it's
so
much
nicer
to
just
iterate
really
quickly
on
this,
while
we're
teasing
out
what
it's
actually
going
to
look
like
I
did
want
to
mention
just
briefly
that
as
Taylor
and
I
and
everybody
else
is
going
through
this
iteration
process
work
kind
of
and
when
I
say
we,
it
looks
like
it's
all
pretty
much
Taylor,
but
we're
kind
of
thinking
of
things
that
we
may
want
to
improve
in,
like
the
next
version
of
wadham,
but
or
or
things
that
might
need
to
be
extended,
as
we
continue
to
implement
like
other
scalers
or
or
things
like
that.
A
Try
to
think,
let
me
see
if
I
can
pull
one
of
these
I
think
we've
actually
been
resolving
them
pretty.
Well
like
this,
one
was
one
that
I
filed,
but
was
actually
actually
not
quite
right,
but
I
just
wanted
to
communicate
that
at
least
if
you're
looking
for
a
place
to
contribute
after
we
launch
the
version
version
0.4,
the
the
issues
will
be
a
great
place
to
look
we're
kind
of
documenting
things
that
were
not
quite
getting
done
in
this
version
of
the
the
refactor.
A
Have
any
questions
about
about
wadham
or
the
work?
That's
going
on
here
happy
to
happy
to
talk
more
about
it.
A
Sweet
well
keep
an
eye
out
for
for
more
stuff.
There,
we'll
get
a
nice
demo
to
you
and
just
wanted
to
note
also
that
you
can
see
an
issue
for
this
is
currently
in
the
the
wadham
repository,
but
the
essentially
the
goal
for
getting
this
project
to
wasmcloud
developers
is
to
take
it
and
embed
it
as
a
part
of
wash
so
that
when
you
run
wash
up
you
get
bottom,
you
can
start
managing
declarative
applications
right
away.
C
C
A
B
B
Down
the
binary
to
be
specific
there
for
this,
for
this
task
we're
going
to
probably
pull
down
the
binary,
because
it'll
just
be
easier
and
then
it's
around
to
reuse
but
yeah.
You
could
technically
embed
it
entirely
into
wash.
If
we
wanted
to.
C
A
A
You
should
have
the
flexibility
of
being
able
to
deploy
it
on
your
own,
but
shouldn't
have
to
shouldn't,
have
to
so
we'll
probably
add
an
additional
flag,
something
like
that.
Don't
start
Autumn
or
something
like
that,
but
it'll
probably
come
in
by
default.
A
Cool
cool
well,
then,
I
think
we'll
move
on
to
our
next
agenda
item
this
one
at
least
I
got
notified
about
it
this
morning,
but
the
issue
has
kind
of
been
like
a
mega
issue
in
the
golang
repository
for
adding
go
OS,
Wazi
preview
1
and
go
archuasm
as
a
compilation.
Target
just
closed.
It
was
a
proposal
and
then
you
know
I
guess
got
accepted
and
then,
if
you
go
and
you
look
through
the
repository,
there's
been
a
lot
of
comments,
a
bunch
of
different
individual
components
of
go
like
crypto
net
HTTP.
A
All
those
things
that
are
being
that
were
were
added
and
referenced
this
issue,
and
it
just
finally
just
finally
closed.
A
A
What
we've
done,
for
a
long
time
in
lieu
of
having
webassembly
like
robust
webassembly
support
without
compiling
in
the
garbage
collector
or
assuming
that
you're
running
in
the
browser
is
we've
used,
tiny,
go
and
and
tinygo
if
you
haven't
played
with
it,
is
essentially
the
it's
kind
of
like
a
kind
of
like
a
subset
of
go,
but
it
uses
all
the
same
standard
libraries
and
is
really
meant
for
compiling
to
smaller
embedded
targets,
not
just
webassembly
things
like
running
on,
depending
on
risk
or
running
on
esp32s,
like
microcontroller
type
things,
it's
super
useful
and
it
had,
and
it
has
a
pretty
good
web
assembly
support
as
it
is
today.
A
The
reason
why
I
wanted
to
bring
this
up,
I
guess
first
off
to
give
hats
off
to
everybody
on
the
go
team
who
worked
on
this,
because
this
is
this
is
super
exciting.
A
It
is
also
to
talk
kind
of
about
wasm
cloud
and
get
the
conversation
started
about
what
we're
going
to
support
talking
to
a
lot
of
people
at
conferences.
People
have
asked
if
we
have
go
support
and
what
we
have
always
said
is
well.
A
We
have
tiny
go
support
and
sometimes
when
people
hear
that
they
think
that
there's
not
really
go
support
and
it's
it's
all
kind
of
a
little
bit
of
a
complicated
Matrix
of
of
language
support,
so
I
I
know
we
have
Jordan
here
our
resident
go
Enthusiast
who
refuses
to
touch
rust.
We
were
kind
of
talking
about
a
couple
of
things
in
the
Gophers
select
this
morning
like
talking
to
some
of
the
talking
to
some
of
the
go
maintainers.
A
Some
of
the
tiny
go
creators
and
maintainers
and
I'm
just
gonna
propose
I
feel
like
what
is
going
to
happen
is,
would
love
to
start
experimenting
with
go
Wazi
support.
There
seem
to
be
a
couple
of
things
that
prevent
us
from
doing
the
wasm
Cloud
protocol,
exactly
as
we
do
today
and
since
wasm
components
are
coming
in
Wazi
Preview
2
that
won't
quite
work
with
the
with
with
Wazi
preview
one,
but
it
seems
like
it's
close
this
actual
this
actual
functionality
is
getting
released
in
go
1.21.
A
The
newest
version
it's
out
right
now
is
1.20.3.
So
when
I
was
playing
with
it
this
morning,
I
just
compiled
from
Maine,
but
by
go
1.22,
they
are
looking
to
standardize
the
way
that
they
deal
with
webassembly
functions.
The
same
between
go
and
Tiny,
go
so
I
think
by
go
1.22
us
saying
that
we
have
go
support
or
tiny
go
support
is
basically
they're.
The
same
thing
I
tried
to
summarize
the
learnings
from
the
slack
and
experimentation
Jordan.
Does
that
sound
about
right
and
match
up
with
what
you're
thinking.
D
D
So
from
what
I
understand
right,
if
going
back
through
that
long
thread,
the
in
the
short
to
medium
term,
they're
going
to
stick
with
Wazi
preview
one
and
we're
going
to
be
relying
on
the
poly
fill
when
it
comes
to
Preview,
2
and
components,
I
I!
Think
that's
because
the
main
folks
working
on
it
didn't
know
how
far
out
or
how
not
far
out
was
the
preview.
2
really
was
Bailey
comes
on
video,
maybe
she's
talked
to
them.
I.
D
E
Yeah,
actually,
the
folks
working
on
Preview
2
were
like
hey.
We
really
think
it
would
be
easier
if
you
go
ahead
and
get
on
preview
one,
because
we've
written
this
adapter
that'll
take
a
preview
one
and
turn
it
into
a
component
so
like
we
can
all
move
faster
and
get
things
working
and
have
stability.
If
you
target
preview
one
first,
so
it
was
actually
the
folks
working
on
Preview
2
that
were
like
yeah.
No,
we
we
advise
you
to
pick
preview
one
right
now.
D
Perfect
awesome
well
now,
I
have
more
backstory
on
that.
So
there's
that
fact
and
and
then
the
other
thing
is
they-
they
did
mention
a
little
bit
of
skew
between
what
tiny
goes
like
wasm
import.
D
The
build
tag
is
going
to
do
and
what
goes
is
going
to
do.
I've
actually
played
with
it
this
morning,
so
tiny
goes.
Obviously
awazi
import
works.
Fine,
it
seems
that
goes
only
allows
you
to
use
wasm
Imports
in
either
the
syscall.js
originating
from
the
sysjog
JS
Levy
or
the
reflect
or
the
runtime
Library.
So
the
fact
that
we
need
to
use
it
in
our
custom
Library.
It
does
not
like
it
now
I
I.
This
is
so
new
I.
D
Don't
really
have
an
answer
on
if
that's
just
a
temporary
thing
or
well.
Obviously
it
has
to
be
a
temporary
thing,
or
you
know
when
that's
going
to
be
fixed
and
I
I.
Think
Brooks
if
I
deciphered
what
they
said
this
morning,
122
is
when
they
should
meet.
Tiny
goes
at
least
current
set
of
features,
so
I
mean
was
that
another
six
month
release
Cadence
I,
think
so,
like
eight
to
ten
months,
ish.
A
D
You
see
that
that
that
I
don't
know
honestly
I,
think
one
interesting
conversation
would
be
with
the
tinaga.
Folks
is
now
that
go
is
getting.
There
are
y'all
going
to
now
refocus
on
embedded
and
content,
or
are
you
going
to
continue
supporting
webassembly
I?
Don't
know
why
I
I
don't
know
the
pros
or
cons
of
like
duplicating
the
work,
so
I
mean
I'd,
be
interested
in
knowing
that.
A
Yeah
my
my
little
issue
that
I
put
in
or
not
issue
just
the
comment
in
the
go
for
slack,
which,
if
anybody's
interested
in
this
conversation,
it's
it's
not
a
it's,
not
a
closed
slack.
It's
just
the
open
source
go
first
slack,
and
this
is
in
the
tiny
go
and
the
webassembly
channel.
You
know
I
asked
if
we
like
how
tinygo
is
gonna
proceed,
I'm
kind
of
catching
up
exactly.
A
You
know
some
of
the
things
that
they
mentioned
or
Damien
mentioned,
which
is
one
of
the
awesome
people
there
is
that
tinygo
has
a
different
set
of
code
generation
like
doesn't
support
panic
and
recover
on
Wazi,
so
their
binaries
are
a
little
bit
faster.
At
that
cost.
Upstream
go.
Has
a
hybrid
Port
of
32-bit
and
64-bit
and
Tiny
go
binaries
on
Wazi
are
generally
a
lot
smaller,
but
not
always
smaller
than
the
go
binaries.
It's
it's
interesting.
A
A
So-
and
this
is
always
a
pretty
fun
thing
to
come
up
with
in
a
community
meeting
where
we're
kind
of
teasing
out
new
ideas,
because
this
is
so
so
new,
but
I
know
that
the
demand
for
just
writing
pure
go
and
compiling
to
webassembly,
especially
using
it
with
was
on
Cloud
for
the
people
here.
Is
it's
really
high
in
demand?
That's
a
really
exciting
thing
to
move
across
so
I'm
gonna
keep
watching
that
issue,
I'm
sure
that
Jordan
is
too
Jordan.
You
wanna
say
some
more.
D
Yeah
no
I
just
want
to
say,
because
we
really
haven't
talked
about
it.
Now
that
the
tiny
guy
wasn't
wasie
Target
is
functioning
and
I've
tested
it
quite
a
bit.
It
actually
opens
the
door
to
feel
a
lot
like
mainstream
go.
D
A
That's
pretty
sweet
I
think
we
should
adjust
our
if
we
can
adjust
some
of
our
documentation
to
indicate
that
it's
a
little
closer
to
you
know
a
normal
go
experience
or
out
of
the
box
experience.
I
guess
I
should
say
so.
Jordan
I
know
that
you
published
a
couple
updates
to
like
the
actor
tiny
go
SDK.
We
should
probably
update
some
of
our
project
templates
like
when
you
do
wash
new
actor.
We
should
make
that
come
with
the
latest
stuff
and
compile
the
Wazi
instead
yeah.
So.
D
It
actually,
it
is
like
quite
it
needs
an
update
to
tiny,
go
actor,
tiny,
go
message:
packet
and
Tiny
go
Seaboard,
they're,
all
very
dated,
so
I
will
say
if
you
do
a
wash
new
actor
or
tiny
goat.
Just
do
the
go,
get
update,
okay,
pull
it
all
down!
It
all
works.
Okay,.
A
Do
you
have
like
a
mega
issue
or
anything
where
you're
tracking
some
of
this
stuff
would
love
to?
In
my
head,
yeah,
okay,.
D
No,
no
I
haven't
started
tracking
any
of
the
wazzy
stuff.
I
actually
started
playing
with
it.
This
week,.
A
Okay,
yeah
I
would
love
to
and
you're
using
like
version
62
of
the
host,
like
our
latest.
A
62.1
yeah,
okay,
yeah
I,
would
just
love
to
try
to
think
of
opportunities
that
we
could
get
people
to
help
contribute
or
to
see
what's
going
on,
especially
with
the
future
plan
to
have
wash
well.
I
know
that
we
were
I
was
kind
of
waiting
to
play
with
tiny
go
a
lot
until
I
had
something
in
wash.
That
would
tell
me
if
I
imported
a
package
that
used
something
from
the
browser
and
I
think
using
Wazi,
it
sounds
like
would
be
a
lot
more,
a
lot
more
streamlined
than
than
needing
that.
E
A
few
Community
calls
back
Jordan
you
demoed,
a
pretty
sick
demo
with
was
Euro,
where
you
kind
of
had
everything
combined.
Have
you
played
around
with
that
at
all
recently.
E
Have
the
link
to
it?
I
looked
at
it,
but
yeah.
No
other
people
are
interested
in
it.
It
seems
like
somebody
just
posted
about
it
over
in
the
cosmotic
Discord
kind
of
looking
at
wasm3
and
I
was
like
Jordan's
got
a
thing
with
zero.
E
C
E
That
kind
of
stuff
I
I'm
curious.
If,
like
that's
the
thing
that
we
need
to
understand,
when
we're
looking
at
tiny,
go
versus
like
go
proper,
you
know
what
are
the
trade-offs
and
and
do
we
need
to
support
both
basically,
which
sounds
like
it's
easy
and
it
won't
be
too
much
issue
since
they're
gonna
align
the
apis.
So
you
know
that
was
just
a
thought.
Yeah.
D
E
B
Yeah
we
ran
into
I'm
forgetting
his
name
at
wasmail
who's,
one
of
the
main
tinyo
people,
and
he
was
like
oh
yeah,
we're
almost
done
rewriting
The
Reflex
stuff.
So
I
was
that's
good
to
hear
that
it's
actually
there
now.
E
Yeah
I
was
following
that
PR
for
months
and
I
guess
I
kind
of
gave
up
on
it,
but
I
should
never
have
given
up
I
knew
they
were
working
and
they
kept
making
changes.
E
I
see
Stephen
asked
another
question
about:
like
are
other
languages
coming
along
with
wasm
and
Wazi,
and
the
answer
is
heck.
Yes,
so
I,
you
know
I
I'm
on
the
technical
steering
committee,
so
I
pay
attention
to
all
these
things
that
happen
in
the
governance
side
of
things
and
the
bytecode
alliance,
and
one
thing
that's
going
on
there
that
we
just
approved
is
a.
Let
me
get.
The
link
is
typescript
compilation,
a
special
interest
group
within
the
by
code
Alliance.
E
So
actually
it
we
didn't
just
have
one
solution:
there
were
three
people
came
up
and
they
were
like
I
have
three
different
ways
that
we
can
get
webassembly
working
with
compiling
to
wasm
and
Wazi,
and
so
we
want
to
come
up
with
you
know:
how
do
we
have
an
ecosystem
built
around
it?
What's
the
right
things,
and
so
we
iterated
with
them
a
bunch
and
I
just
posted
that
pull
request
so
that
Sig
just
started.
E
If
that's
something
you're
really
into
types
typescript
specifically
and
having
typescript
compiled
to
wasm
and
and
to
be
clear,
we
also
have
JavaScript
compiling
to
wasm
there's
this
tool
called
componentize.js
and
so
conventionally,
what
we
always
kind
of
expected,
because
we're
like
wow
that's
hard
right,
because
you
need
basically
a
nominal
type
system
to
be
able
to
statically
analyze
the
typescript
and
turn
that
into
a
was
a
module
like
that.
That
feels
like
a
hard
process.
E
What
definitely
we
could
do
is
compile
your
jobs
typescript
to
JavaScript,
like
you
normally
do
for
the
browser,
and
then,
if
you
have
a
wazza
module
that
embeds
a
JavaScript,
basically
engine
you
get,
you
get
a
bigger
plasma
module.
That's
definitely
the
downside
there,
but
it
would
work
and
it
would
work
with
just
about
all
different
types
of
typescript
and
JavaScript.
E
It
wouldn't
be
just
the
subset,
but
the
folks
over
at
Intel
are
like
really
interested
in
finding
a
way
to
get
it
as
Slim
as
humanly
possible
and
the
best
way
to
do
that
is
right
to
start
with
typescript
and
not
have
to
embed
any
type
of
engine.
So
anyways,
that's
the
that's!
The
motivation
for
that
one
and
it
feels
like
every
day
different
languages
are
popping
up
typescript's.
Just
one
of
them.
E
A
Hey
I
was
just
happy
to
to
hear
you
on
on
the
language
sub
box
Bailey.
All
the
developments
on
language
are
so
exciting
that
they're
happening
so
fast.
It's
like
hard
to
keep
track
of
honestly.
What
has
added
webassembly
support
and
you
can
compile
binaries
too
and
all
that
stuff.
It's
really
fun.
A
I'm
excited
for
this
upcoming
wasm
day,
just
to
see
what
people
are
doing,
what
people
are
doing
with
with
components
I
think
there's
you
know,
especially
with
JavaScript
components,
webassembly
components
all
around
it's
going
to
be
pretty
cool,
Jordan.
D
Just
as
I
soft
tangent,
maybe
on
the
topic
of
different
languages,
I,
you
know,
I
was
able
to
take
Bailey's
whole
component
thing
use.
Is
it
masaka
his
whole
with
binding
for
go
and
more
or
less
almost
not
all
the
way
there,
but
close
got
a
got
the
echo
components
working
with
HTTP.
So
it
takes
a
whole
lot
of
guessing
for
me,
but
it's
very
exciting
because
it
feels
like
maybe
this
maybe
like
three
weeks
ago.
It
felt
like
we'd
never
get
there
and
all
of
a
sudden.
E
The
the
really
exciting
thing
is
that
we
were
like
hey
now.
We
can
stop
using
grass
for
everything.
I
just
want
to
say
that,
like
with
the
components
now,
you
can
write
in
any
language,
you
want
that
compiles
to
a
component,
but
like
pretty
soon
it's
gonna
be
like
all
of
them
right,
so
all
of
the
different
languages,
and
then
we
could
be
writing
stuff
in
Rust,
and
it
doesn't
matter
to
you.
E
You
can
write
your
thing
and
go
and
link
to
that
component
and
just
get
it
right,
and
so
this
whole
like
language
Wars
that
we've
had
for
I,
don't
know
20
years
or
more
that
just
completely
melts
away
so
I'm
pumped
Loki's
pumped
so
yeah.
A
Well,
we
are
getting
some
some
inflicting
language
things
in
the
in
the
chat.
Just
gonna
go
ahead
and
go
ahead
and
leave
those
alone.
A
I
I
think
it's
probably
worth
Taylor
I
think
it's
probably
worth
mentioning
that
next
week.
I
think
you
know,
Taylor
said
it
briefly
at
the
beginning
of
the
call,
but
a
majority
of
the
waslam
cloud
maintainers
and
some
of
us
you
know
coming
from
cosmonic,
are
going
to
be
at
kubecon
in
Amsterdam,
so
starting
actually,
this
Saturday
with
Cloud
native,
rejects,
Taylor
and
I
are
doing
a
talk
there.
A
Bailey
do
you
have
a
talk
at
rejects,
I
feel
like
I
thought
you
might,
but
well
hopefully,
I
didn't
remind
you,
okay,
we're
we're
going
to
be
presenting
on
Monday
at
Cloud
native
Rejects,
and
then
we
have
a
couple
of
talks
spread
across
Cloud
native
wasm
day
and
then
culminating
with
Kevin
Kevin
Hoffman.
You
all
know
Kevin
presenting
on
Friday
at
the
main
conference
about
his
event,
sourcing
work
that
he's
going
to
be
that
he's
been
working
on
and
demoing
over
the
past
couple.
A
Community
meetings
Bailey
is
going
to
be
doing
the
keynote
at
Cloud
native
wasm
day,
which
will
be
really
exciting.
I,
don't
think
that
that
event
is
being
streamed,
but
cosmonic
sponsored
this
session
recordings
for
the
event.
So
they'll
all
be
on
YouTube
within
I.
Don't
know
they
do
it
pretty
quick
it'll
be
within
a
week
or
two
of
the
event
ending,
so
lots
of
exciting
stuff.
Looking
forward,
we
will
likely
do
a
really
abbreviated
community
meeting
next
week.
Here,
Taylor
is
pulling
up
some
some
talk,
things
I'll
go
and
share
them.
A
We
will
likely
do
a
pretty
abbreviated
community
meeting
next
week
and
the
whole.
The
whole
reason
for
that
is
that
we'll
likely
be
either
at
the
wasm
cloud,
Booth
or
walking
on
the
floor
or
going
to
talks
and
things
so
we'll
try
to
tune
in
from
there.
Maybe
we
can
catch
some
of
you
folks
if
anybody
is
coming
in
from
from
Europe
and
actually
going
to
the
event,
but
just
a
heads
up
that
it'll
probably
be
pretty
light
next
week.
A
Try
to
do
a
couple
updates
from
from
what's
going
on
and
then
go
from
there,
so,
okay,
so
Taylor
and
I
both
is
it
the
same
thing?
Nope
I
just
saw
a
webassembly
twice.
Taylor
is
doing
his
talk
on
on
Monday,
the
the
solo
talk
and
then
me
and
Taylor
are
doing
a
talk
together,
which
will
will
be
fun.
It's
always
fun
is
rejects,
being
screamed,
actually,
I,
don't
know
the
answer
to
that.
B
I
think
it
does
get
live
streamed.
Let
me
double
check
nice.
A
B
I
know
it's
recorded
for
sure,
so,
even
if
it's
not
I'm
trying
to
find
out
they're
going
to
stream
that
or
not
but
I,
don't
see
anything
initially
here
on
their
page,
so
yeah,
but
they
do
record
and
put
them
up
on.
Youtube
rejects
talks
if
you've
never
been
or
watched
rejects
talks.
It's
still
one
of
my
favorite,
like
kubecon
adjacent
conferences.
B
There
are
there's
just
a
lot
of
talks
that
like
get
more
down
into
really
interesting
details
that
sometimes
just
don't
get
accepted
at
kubecon,
given
the
large
crowd
and
the
different
like
business
things
that
need
to
get
done
there
too,
and
so,
like
you,
have
like
some
real
interesting
talk,
things
that
go
on
and
and
so
it's
very
worth
watching
not
just
for
our
talks
but
for
the
whole
thing
there's
they
just
really
have
some
good
I
mean
yeah,
like
he's
looking
like
doing
VMS
and
containers
and
firecracker
comparisons,
you
know
and
like,
and
it's
people
who,
like
you,
might
recognize
some
people
who
don't
know
haven't
been
on
the
speaking
circuit
before
it's
really
a
great
conference,
so
just
gonna
I'm,
gonna
rep
it
for
a
little
bit.
B
There,
like
it's
very
worth,
going
to
and
and
watching
if
you're,
if
you're,
not
in
Europe,.
A
It's
a
lot
of
fun
and
then
last
kind
of
call
out,
Bailey
reminded
me:
Bailey
and
I
actually
went
and
streamed
our
talks
from
devops
Days
Nashville
that
we
did
last
week.
Oh
hey,
that's
good
face
we'll
just
go
back
to
the
beginning.
We
we
live
streamed
our
talks
because
we
noticed
that
the
event
wasn't
being
wasn't
being
recorded
or
or
live
streamed.
So
we
wanted
to
try
and
bring
that
to
the
masses.
Bailey
had
a
really
awesome
ignite
talk,
not
ignite
ignite.
What's
it
got
lightning?
A
Yes,
it's
an
ignite
talk,
not
a
lightning
talk,
so
it
was
Auto
advancing
15.
Second
slides,
which
was
kind
of
a
crazy
hectic
format
for
for
was
a
more
wind,
so
I
definitely
recommend
you.
You
go
and
check
this
one
out.
Oh,
you
can
send
a
link
in
the
awesome
Cloud
slack,
maybe
after
this,
but
just
wanted
to.
A
Let
everybody
know
that
we
had
a
couple
more
a
couple,
more
talks
that
we
streamed
I
think
I
saw
Steven
there
following
along,
which
was
fun
glad
to
have
you
in
the
audience,
but
I
think
that's
it.
Lots
of
lots
of
exciting
events
and
things
coming
out
if
anybody
has
anything
else
that
I
like
to
announce
at
this
point
feel
free
to
raise
your
hand.
Otherwise
I
think
we
can
just
move
on
to
free
discussion
time.
If
anybody
has
anything
that
they'd
like
to
talk
about.
A
Alrighty,
well,
then,
I
think
we'll
probably
probably
call
it
here
thanks
everybody
for
for
coming
today,
really
great
kind
of
brief
but
exciting
things
talking
about
in
this
community
meeting
just
to
harp
on
it
again,
it'll
probably
be
pretty
light,
but
we
will
be
here
next
week
when
we're
in
Amsterdam
and
looking
forward
to
seeing
y'all,
either
at
the
conference
or
after
the
conference
and
and
all
that
stuff.
So
thanks
everyone
see
you
next
week.