►
Description
wasmCloud is a platform for writing portable business logic that can run anywhere from the edge to the cloud, that boasts a secure-by-default, boilerplate-free developer experience with rapid feedback loop.
Release Party: https://app.livestorm.co/cosmonic/wasmcloud-dot-5-0-release-event
A
A
A
I
would
just
do
a
quick
call
out
that
a
documentation
at
watsoncloud.dev
it
has
been
up
to
date.
I
really
appreciate
all
the
bug,
fixes
and
submissions
here
to
make
sure
that
this
experience
is
smooth
coming
in,
and
you
know
all
the
packaging
should
be
I'm
out
there
for
was
the
wasn't
cloud
you
know
host
to
get
through
those.
I
know
we
still
have
a
few
additional
things
to
build
out
on
that
side
and
we're
meeting
the
next
couple
days
to
talk
a
little
bit
about
road
map
and
architecture.
C
C
A
A
B
Right
yeah,
I
started
playing
around
with
the
lattice
controller
to
get
it
working,
and
I
guess
I
made
some
comments
in
the
channel.
I
did
get
building
and
working
and
I'm
playing
around
with
it.
I
have
not
integrated
it
with
the
operator
at
this
time
and
I
haven't
really
tried
to
steal
the
demo
from
patient
david
either.
So
I
think
at
some
point
in
time
they
won't
do
a
demo
whenever
they're
actually
feeling
comfortable.
D
D
A
E
C
It's
it's.
I
don't
have
an
answer
for
that.
We
need
to
prioritize
based
on
interest,
and
so
non-rest
is
not
specific
enough
to
prioritize.
So
we
really
need
to
know
the
kind
of
languages
people
are
interested
in.
I've,
seen
requests
on
slack
for
c
or
c
plus
plus,
and
that's
about
all
I've
seen
so
far.
So
that's
where
your
input
is
really
is
really
helpful
and
that
you,
the
larger
you
input,
is
really
helpful
in
giving
us
feedback
as
to
what
people
really
need
and
want
to
use.
A
That'd
be
fun
on
the
back
side.
I
actually
love
that
idea.
Jordan.
If
you
want
to
just
drop
kick
one
off,
you
know
curate
a
list
of
languages
and
you
know
maybe
check
it
by
steve
yeah
before
you
drop,
it
would
be
awesome,
but
the
we
are
experimenting
with
some.
You
know
some
professional
roadmap
tools
like
product
board
on
the
back
side.
A
What
I
like
about
it
is
is
that,
as
we
kind
of
collect
evidence
for
what
people
are
doing,
we
can
try
to
have
a
you
know
really
user
run
roadmap
here,
steve
just
speak
to
your
point.
Around
real
prioritization
alex,
I
think,
that's
a
great
question.
What
languages
are
easier
to
implement?
I
remember
someone
talking
about
challenges
with
tiny
ghost
efforts
in
the
past.
C
D
I
mean
there
are
some
hard
limitations
like
there
are.
There
are
specific
workarounds
that
need
to
be
put
into
tiny
go
in
order
to
make
it
work,
but
that's
not
it's
not
all
that
big
a
deal.
We've
we've
made
that
same
work
around
before
other
languages,
lack
data,
serialization
stuff
so
like
when
we
did
typescript
before
or
assembly
script
assembly
script
required
writing
a
message.
Pack
encoder
decoder,
so
those
types
of
details
are
are
important
but,
like
steve
said,
what
really
matters
is
the
language
that
the
community
wants.
The
most.
C
D
Actually,
I
would
say
we
should
probably
not
try
elixir
on
the
capability
provider
side
there
are.
There
are
a
number
of
issues
with
with
the
way
elixir
distributions
work.
Mostly
it's
just
that
elixir
doesn't
lend
itself
well
to
building
self-contained
executables,
which
is
pretty
much
a
requirement
for
capability
providers.
C
D
A
A
Road
map
will
continue
as
we
get
more
fidelity
to
pull
things
into
an
rfc
process
where
we're
publishing
rfcs
on
github
and
then
we'll
sort
of
coordinate
across
the
individual
repos,
with
clear
definitions
of
done
in
github
tickets
and
we'll
use
zenhub
to
sort
of
like
manage
across
the
various
repos.
Here
those
are
sort
of
information
systems
with
product
board.
A
I
think
we
have
the
ability
to
public
publicize
a
roadmap,
but
we're
still
new
to
the
software
and
trying
to
figure
out
if
it's
a
good
fit
for
this
particular
use
case
and
as
I
have
some
time
to
experiment
with
that,
you
know
we'll
see
what
we
can
link
in
publicly
to
the
community
as
we
sort
of
like
agree
on
hey.
We
think
this
is
what
the
roadmap
looks
like
for
the
next
few
months
and
maybe
even
some
rough
mappings
to
feature
releases
and
stuff
like
that.
A
A
I
love
the
the
hustle
on
you
know,
trying
to
pick
up
the
lattice
controller
and
see
where
it's
at
and
just
get
familiar
with
it,
and
you
know-
and
I
love
the
passion
that
you
and
the
and
the
also
the
sort
of
strategy
you've
brought
to
the
kubernetes
operator
in
you
know,
selecting
the
framework
that
gave
us
the
best
starting
point,
and
you
know
the
kubernetes
operator
stuff
up
really
appreciate
that.
That's
great
anything
else
on
the
roadmap.
We'd
want
to
discuss.
A
The
only
item
I
would
love
to
get
up
towards
the
top
of
it
would
be
and
we'll
discuss
this
tomorrow
as
well
that
we
haven't
talked
about
you
know
from
additional
language
support.
Kubernetes
operator
would
be
taking
another
pass
at
the
training,
materials
and
redoing
those
those
you
know.
When
we
look
at
the
usage,
we
just
had
really
sustained
continual
engagement
with
both
katakota
or
with
katakota.
A
At
least
I
it's
don't,
have
stats
on
the
linux
foundation
stuff,
but
with
codakoda,
and
I
want
to
make
sure
that
we
now
that
we
have
these
new
demos
that
we
maybe
think
about
how
we
might
incorporate
them
into
a
more
expansive
onboarding
to
show
distributed
topology-
and
you
know
those
other
kind
of
like
really
big
wins.
That
wasn't
cloud
gets
you
on
day.
One.
B
B
Suggest
kiali:
it's
like
a
mesh
view
for
hdl,
which
is
the
service
mesh
and
that's
kind
of
still,
my
mental
map,
of
what
the
lattice
controller
is
which
working
on
it
will
probably
change,
but
an
otp
it's
more
like,
so
it
works
pretty
well
for
inspection,
or
I
mean
yeah.
It
just
works
kind
of
well
for
showing
what
traffic
is
going
on,
how
the
whole
thing
just
hangs
together
in
terms
of
what
the
mesh
looks
like.
A
Washboard,
I
feel
like
there's
some
big
opportunity
here.
We
were
looking
at
a
washboard
earlier
today
on
rehearsing
the
demo,
and
I
found
myself
thinking
through
you
know
a
bunch
of
common.
You
know
views
that
I
think
would
make
sense
if
we
had.
You
know
like
a
host
view
that
organized
with
the
host
as
the
anchor
and
then
you
know,
distribute
it
out
from
there
an
actor
view
where
you
know
the
the
drop-downs
would
be.
A
You
know
what
capabilities
am
I
attached
to
and
then
maybe
a
capability
view
that
would
show
you
know
some
things
from
there.
So
I
think
there's
lots
of
lots
of
opportunity
on
the
visualization
there
for
the
lattice
controller
and
or
really
any
component,
but
I
think,
certainly
if
you
can
link
it
in
the
chat,
janet
I'd
love
to
take
a
look
at
it
and
and
just
see.