►
From YouTube: Panel Discussion: Rust in the Cloud - W. Morgan, A. Williams, O. Gould, C. Lerche, P. Howard
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Panel Discussion: Rust in the Cloud - Moderated by William Morgan, Buoyant; Ashely Williams, Rust Foundation; Oliver Gould, Buoyant; Carl Lerche, Amazon; Paul Howard, Arm
Speakers: Paul Howard, Ashley Williams, Oliver Gould, Carl Lerche
In this discussion, panelists from several areas in the intersection of the Rust and Cloud Native communities will discuss what's next for the Rust in the cloud. Questions will cover both social and community aspects (e.g. the parallels between cloud native and Rust community ethos), the technical (e.g. the introduction of async/await), and the subjective (e.g. is there anything else Rust needs in order to be successful in the cloud space?).
B
Nice,
I
think
that
means
I'm
first.
My
name
is
ashley
williams,
I'm
currently
the
interim
executive
director
at
the
rust
foundation,
I'm
also
a
member
of
the
russ
core
team
and
have
participated
in
almost
it
feels
like
all
the
rust
teams
at
some
point,
but
for
I
guess
the
purposes
of
this
panel,
I
I
used
to
work
at
cloudflare
and
I'm
very
interested
in
web
assembly
and
serverless.
B
C
D
It's
fine,
I'm
oliver
gould,
I'm
the
cto
at
a
company
called
buoyant
where
we
work,
mostly
where
I
work
mostly
on
linkedin.
It's
a
cncf
project
that
we
created
about
five
years
ago
now
and
this
this
version
of
it
linker
d2,
is
heavily
built
on
a
rust
proxy,
and
so
we've
been
really
focused
on
the
rust
tokyo
ecosystem
heavily
over
the
past
three
to
five
years.
E
Sure
yeah,
I'm
paul
howard
principal
system,
solutions
architect
with
arm.
I
work
in
the
arm
architecture
and
technology
group.
I
lead
a
small
engineering
team
here
at
arm
where
we
are
contributing
into
the
parsec
project
and
parsec
is
a
rust-based
security
focus
project
that
is
now
part
of
the
cncf.
It's
been
a
cncf
sandbox
project
since
last
year,
so
yeah.
That's
me.
A
A
A
A
B
Yeah
sure,
so
what
I
am
actively
working
on
is
probably
slightly
different
than
you
might
mean
by
this
question,
but
I'll
get
to
that.
So
I
guess
the
very
first
time
that
I
got
rust
into
the
cloud
in
production
was
when
I
was
working
at
npm
several
years
ago
and
my
favorite
quote
from
the
cto
at
the
time.
B
Cj
silverio
is
I
like
rust,
because
rust
is
boring
and
ultimately
that
just
means
I
we
were
getting
woken
up
by
pagerduty
a
lot
less
thanks
or
rust
services,
and
that
was
really
delightful
and
it
kind
of
goes
against
the
the
general
vibe
of
picking
up
technologies,
because
they're,
exciting
and
and
so
the
boring
quality
has
always
been
really
fantastic.
The
thing
that
I'll
say
I've
learned
is
that
convincing
folks
to
transition
services
to
rust,
regardless
of
whether
they're
in
the
cloud
or
not
requires
this
transition
of
understanding.
B
When
you
invest
time
that,
on
the
face,
might
sound
very
simple,
but
it's
actually
kind
of
like
a
big
culture
shift,
which
is
when
you're
writing
things
in
rust.
You
end
up
needing
to
invest
a
lot
more
time
up
front.
Instead
of
you
know,
you
know
I'm
working
on
a
service
and
then
I
put
it
into
production,
and
then
it
screams
at
me
with
rust.
All
that
screaming
happens
at
the
beginning
and
getting
used
to
that
investment
up
front
instead
of
coming
later
can
be
really
tricky.
E
E
So
so
it's
really
about
building
a
cloud
native
and
portable
dev
experience
for
security
more
and
more
in
the
world
of
edge,
rather
than
necessarily
in
the
cloud,
and
I
think
actually
workloads
roaming
from
cloud
to
edge
is,
is
one
of
the
really
interesting
areas
for
rust
as
well.
Now
I
have
to
say,
I
chose
rust
for
plastic.
E
I
kind
of
was
was
in
the
chair
to
make
that
call,
and-
and
this
was
without
ever
having
written
a
line
of
rust
code
right.
This
was
a
couple
of
years
ago.
I
just
felt
really
from
what
I
knew
about
the
language.
What
I'd
read
about
the
language
and
what
I'd
heard
other
people
saying
it
it.
It
felt
like
the
way
to
intercept
the
future
right.
E
E
E
These
criticisms
aren't
entirely
unfounded,
but
the
language
can
be
a
beautiful
language
as
a
very
expressive.
Its
abstractions
are
concise,
syntactically,
as
well
as
as
being
low,
runtime
costs
as
well.
Now
I
I
still
haven't,
become
an
expert
rust
developer.
As
yet
right
like
I'm
still
working
on
that,
I
can't
lay
claim
to
that.
E
But
what
I
have
seen
so
far
is
that
you
can
write
code
that
is
as
elegant
as
like
a
pure
functional
language,
for
instance,
with
things
like
pattern,
matching
lots
of
expressive
power,
and
yet
you
know
all
along
that
you're
writing
code.
That's
going
to
give
you!
You
know
performance
parity
with
clc
plus
plus,
but
without
the
memory
faults
and
the
data
races
and
so
forth.
So
you
know
it's
really
the
the
best
of
all
worlds
in
in
that
regard.
C
What
what
have
I
been
up
to
yeah
I
mentioned
earlier?
I
work
on
tokyo,
the
an
asynchronous
runtime
for
rus,
so
specifically
it
tokyo
lets.
You
write
network
applications
for
rust
and
it
turns
out
when
you're
in
the
cloud.
There
are
networks
that
you
have
to
factor
in
there's.
You
know
shuffle
bytes
between
one
node
server
or
whatever,
whatever
they're
containing
call
these
these
containers
lambda
function
functions
or
whatever
they.
C
Whatever
people
do
these
days,
I
tend
to
stay
lower
in
the
stack,
so
I'm
trying
to
keep
up,
but
before
you
riding
ross
before
I
really
got
into
rust.
I
spent
most
of
my
time
in
the
jvm,
which
is
a
great
piece
of
technology.
You
know
lots
of
really
solid.
Software
is
written
with
java
and
other
jvm
languages
in
the
cloud
too.
C
Your
requests
respond
faster,
more
controlled,
more
reliable
and
that's
really
attractive
to
a
lot
of
people
building.
You
know
products
software
in
the
cloud
so,
like
I
think,
paul
hinted
at
that
learning
curve.
I
think
part
of
that
I
mean
there's
the
language
aspect
and
it's
you
know
it's
improving.
All
the
time,
but
there's
also
the
aspect
of
like
rust,
really
is
still
a
new
language
and
the
ecosystem
is
young
compared
to
you
know,
platforms
like
java
or
go
that
have
matured
a
lot
over
the
years.
C
So
what
I'm
trying
to
do
these
days
is
improve,
like
the
tooling,
especially
around
debugging,
and
like
build
up
more
of
that
higher
level
like
tangential
infrastructure
around
building
services.
So
I
think,
and
I'm
on
a
team
at
amazon
rust
platform
team
that
were
like
nico
matsakis
and
felix
and
a
few
other
rust
developers
that
work
out
in
the
open
are
on
this
team
and
we're
working
kind
of
on
the
open
source
infrastructure.
C
So
nico
started
with
the
async
vision
dock,
which
you
can
probably
google
on
the
it's
on
the
rock
rust
blog
but
kind
of
solicitating
experience
from
people
building
services
with
rust
to
kind
of
see
to
learn
what
is
missing.
So
we're
doing
that
and
then
step
two,
hopefully
we'll
be
fixing
some
of
that.
D
Composable
primitives
rust
was
really
really
hit
that
sweet
spot,
and
so,
as
we've
moved
into
this,
I
think
the
things
that
carl
are
talking
about,
of
having
kind
of
the
operational
tooling,
where
that
ecosystem
isn't
quite
as
mature
as
it
is
going
to
need
to
be,
but
really
seeing
the
trajectory
of
the
ecosystem
going.
So
when
we
started
there
there
were,
you
know
we
had
hyper,
but
there
was
no
hdb2.
D
There
were
little
on
hdb3
or
anything
kind
of
fancy
like
that
and
really
seeing
the
set
of
primitives
in
the
ecosystem
blossom
over
the
past
three
years.
So
things
like
tonic
and
tower
really
really
make
me
think
that,
like
it's
time
for
us
in
a
much
more
serious
way-
and
I
think
that'll
be
the
theme
of
what
we're
going
to
talk
about
today.
A
A
You
know
whether
it's
a
language
or
the
ecosystem,
or
the
community
or
or
any
aspect
of
rust,
something
that
makes
it
a
particularly
good
fit
for
the
constraints
of
the
cloud
you
know,
which
is
this
very
particular
environment.
You
know
that
that
is
quite
different
from
other
kind
of
execution
environments
out
there.
D
Let
me
just
insert
my
my
one
take
on
this
first,
since
I'm
already
talking
the.
I
really
think
the
union
of
like
cloud
is
necessarily
network
right.
It's
about
a
dynamic
system
where
things
are
going
to
communicate
over
a
network
and
to
do
network
software
in
any
reasonable
way.
You
need
safety
guarantees,
especially.
D
E
D
C
I
I
think
you
can,
I
mean
I'm
going
to
go
off
and
tangent,
but
it
is
possible
to
write
safe
c
like
correct
c.
It
just
takes
like
an
amount
of
resources
and
energy
that
most
organizations
won't
even
be
able
to
afford
to
put
in,
like
I
mean
like
s2n
like
amazon's
tls,
implementation
is
c,
but
the
amount
of
like
they
go
in
and
formally
prove
it.
They
you
like,
they
use
their
improvers.
C
They
go
like
audits,
they
fuzzers
they
like
very
limit
and
like
very
well
constrained
like
code,
it's
just,
but
that
is
a
lot
of
effort
that
most
would
not
even
do-
and
I
don't
even
even
on
amazon
we'd
rather
not
put
in
that
effort,
if
we
don't
have
to,
which
is
why
we're
using
rust
heavily,
and
it's
also
why,
before
us
people,
people
would
use
the
jb
like
jvm
based
language.
So
what
makes
it
a
good
fit
for
the
cloud?
C
It's
well
not
having
to
worry
about
that
safety
side
of
things.
So
that's
a
mental
burden.
You
can
take
off
of
your
head,
but
then
run
leaner
right,
less
memory,
less
cpu,
it'll
cost
less
it'll
be
better
for
the
environment.
You
know
when
you're,
if
you're
talking
about
huge
scale
that
will
have
a
impact,
less
carbon
emission,
I'm
just
going
to
throw
that
in,
but
and
and
as
as
the
ecosystem
improves.
It's
going
to
be
a
good
experience.
I
think
it's
not
there
yet,
but
we're
going
to
get
there
like
it's
there.
C
E
Yeah
I
mean
I,
I
think
know
this.
This
is
a
really
interesting
question
that
what
about
rust
makes
it
particularly
good
fit
for
the
cloud
parsec
is
more
of
an
edge
compute
project,
but
I,
I
think
what
I'd
say
in
response
to
this
question
is
well.
Maybe
two
things.
The
first
thing
I'd
say
is
what
makes
it
good
for
the
cloud
is
the
same
as
what
makes
it
good
for
anything
else
right.
E
I
mean
when,
when
would
you
not
want
that
whether
you're
you're
in
the
cloud
or
indeed
anywhere
else,
but
I
think
it's
particular
opportunities
to
shine
in
the
cloud
come
in,
like
the
software
defined
infrastructure
pieces
right
the
pieces
of
your
cloud
orchestration
that
you
need
to
just
stay
out
of
the
way,
but
do
everything
perfectly
you
know
rust,
compiles
down
to
very,
very
small
low
footprint
binaries?
It's
absolutely
perfect
for
your
software-defined
networking
for
your
service
mesh
layers
for
your
for
your
tenant
separation.
E
Primitives.
You
know
the
the
the
frame,
the
skeletal
frameworks
in
your
deployment
that
keep
workloads
isolated
from
each
other.
I
mean
look.
What
link
linker
do
you
write
is
a
great
example.
Look
at
look
at
like
micro,
vm
technologies
right
think
things
like
firecracker
aws
firecracker
is
is
a
hypervisor
written
in
rust.
I
I
think
that
that
kind
of
thing
where
you
want
you,
you
want
software-defined
infrastructure
that
shrinks
out
of
the
way
of
the
the
workloads
that
you're
running.
E
That's
not
to
say
your
workloads
might
not
be
rust
as
well
right,
but
I
think,
but
I
think
for
that
soft,
that
those
software
defined
infrastructure
pieces,
those
thin
pieces
that
just
need
to
slide
in,
and
you
know,
separating
the
workloads
from
the
hardware
separating
the
workloads
from
each
other.
I
think
that
that's
that's
an
area
where
rust
really
has
the
opportunity
to
shine,
because
security
is
just
so
so
critical
in
those
areas
right
and
in
rust,
rust.
E
E
C
Yeah,
like
I
hear
some
from
some
users
of
tokyo
they're
like
they,
don't
necessarily
need
the
raw
performance
but
they're
able
to
not
worry
about
it
like
so
it's
they're
like
they're,
stuck
like.
Why
would
you
want
to
spend
all
that
time
up
front?
It's
it's
when
you
get
like
you
over
time,
it
gets
less
time,
but
also
like
a
startup
doesn't
have
to
worry
about
performance.
B
Well
yeah,
I
was
about
to
say,
like
we've,
been
getting
extremely
close
to
saying
the
w
word,
but
I
I
do
think
like
when
we
say:
is
there
something
about
russ
that
makes
it
particularly
a
good
fit
for
the
cloud
like
I.
I
really
do
agree
with
john
that,
like
I
think,
rust
is
a
good
fit
for
the
cloud
like
the
same
way.
It's
a
good
fit
for
a
lot
of
different
problems
like
the
cloud.
B
Perhaps
this
is
blasphemous
to
say,
but
I
don't
necessarily
think
that
the
the
needs
the
cloud
has
are
particularly
unique
to
many
software
projects
and
so
like
the
reliability
and
the
efficiency.
But
I
think
talking
about
why
rust
is
well
suited
to
web
assembly.
A
lot
of
people
talked
about
webassembly,
like
particularly
when
it
first
showed
up
as
like.
Oh
it's
like
our
multi-language
future,
and
then
inevitably,
people
very
quickly
realized
that
compiling
any
language
to
webassembly
was
not
really
going
to
be
a
great
great
situation.
B
As
somebody
who
has
worked
on
many
projects
of
compiling
all
sorts
of
different
languages
to
webassembly
it's,
it's
it's
a
much
harder
problem
and
the
efficiency
gains
that
you
might
get
from
something
like
it
can
disappear.
Sometimes,
if
you're
particularly
trying
to
take
a
gc
language
and
put
it
into
webassembly,
but
rust
benefits
from
its
very
very
low
run.
B
Just
they
don't
have
as
friendly
of
tooling
as
rust
has,
and
that
makes
for
us
particularly
well
suited
for
that
space,
and
I
mean
with
web
assembly
it's
like
low-level
system
plus
containers.
I
don't
think
we've
seen
the
future
of
webassembly
yet,
but
my
favorite
thing
about
it
is
that
in
theory
it
was
developed
to
like
replace
flash
and
browsers,
but
it
is
becoming
a
tool
of
the
cloud
probably
exclusively
before
it
ends
up
actually
showing
up
in
anybody's
client.
A
Yeah,
so
that's
a
great
segue
into
the
next
question
because
he
used
the
word
future,
so
we've
talked
you
know
so
far
about
kind
of
the
state
of
where
rust
is
today
and
developer,
experience
versus
tooling
and
so
on.
If
we
fast
forward
for
I
picked
a
limited
horizon
just
five
years
from
now,
you
know:
how
will
we
see
rust
used
in
cloud
environments,
especially
ashley?
It
seems
like
this
question
is.
B
Oh,
my
goodness,
five
years
is
a
really
really
long
time,
and
I
see
no
reason
to
believe
that
the
epic
amount
of
progress
that
was
made
in
the
last
five
years
will
not
be
the
type
I
mean.
We're
gonna
see
that,
if
not
more,
I
think,
particularly
in
cloud
application
space
for
rust
and-
and
I
think
what
I
would
say
just
kind
of
probably
to
tee
it
off,
for
everybody
else
is
so.
We
recently
announced
the
rust
foundation-
or
I
guess
in
february,
which
feels
like
it
was
yesterday.
B
C
Well,
the
flip
side
is,
I
hope
I
think
russ
has
has
had
five
years
of
like
extremely
fast,
like
evolution
and
growth
and
churn
and
figuring
out
what
it's
all
about,
and
I
think
the
next
five
years
are
going
to
be
a
lot
more
stable.
So
it
will
be
less
evolution
like
of
rust
and
more
growth
like
I
guess,
russ
is
probably
in
his
teenage
years
like
it's
going
to.
Finally,
like
you
know,
start
fitting
they
go
kind
of
like
the
tooling
will
start
getting
more
refined.
C
There
right
there,
the
foundation
is
there
all
right,
let's
see,
but
so
there
is
going
to
be
change,
but
I
hope
it's
not
going
to
be
like
groundbreaking
change.
I
think
I
think
we'll
see
more.
Of
the
same,
I
mean
if
they're
like
wasn't,
I
think
wasm
is
probably
going
to
be
where
there's
the
most
discovery,
because
I
mean
the
whole
ecosystem
still
figuring
out
what
it
is
about
and
where
the
applications
are.
It's
not
my
area
of
expertise,
so
I
will
ashley
it's.
C
But
besides
like
in
the
networking
space
and
the
cloud
like,
I
think
it's
just
going
to
be
more
like
we'll
see
more
application
of
it,
as
as
that
learning
curve
and
as
more
people
learn
it
and
as
we
polish
off
that
beginning
like
getting
started,
experience
that,
like
debugging
experience
that,
like
tooling
experience,
I
think
more,
we'll
we'll
see
more
rust
use
in
places.
You
know
in
places
we
might
not
initially
expect
it,
but
not
necessarily
new
groundbreaking
areas.
More
just
some
new
field,
new
experience,
news
development
and
existing
spaces.
D
Something
that
I've
noticed
about
my
interactions
with
the
russ
community
is
that
the
community
really
skews
young
right,
or
I
see
a
lot
of
folks,
either
in
college
or
coming
out
of
college
and
like
when
I
was
in
college.
If
you
wanted
to
be
a
systems
programmer,
you
were
going
to
learn
c
or
c
plus,
plus
and
like
that
was
you
know,
not
a
very
welcoming
job
opportunity
or
career
path.
D
There
and-
and
I
see
now
lots
of
younger
people
who
are
coming
into
the
industry
really
enthused
about
rust
and
kind
of
really
engaged
at
the
systems
level
in
a
way
that
was
just
not
there
10
plus
years
ago.
From
my
perspective
at
least,
and
so
I
I
do
think
that
there's
going
to
be-
and
I
don't
want
to
say
the
word
army,
but
a
big
kind
of
contingent
of
of
rus
developers
coming
into
the
industry
in
the
next
couple
years.
C
I
mean
you
touched
on
something
that
I
don't
think
we
mentioned
much,
but
russ
makes
systems
level,
programming,
approachable,
like
the
fact
that
you
can
go
and
write
at
that
level
and
not
worry
about
the
sharp
edges
of
c
or
c
plus
plus
is
very
empowering,
and
it's
going
to
be
like
it's
going
to
be
interesting
to
see
as
more
developers
get
to
that
level.
What
are
we
going
to
build
like
it's?
Just
like
you
know
all
the
advantages
of
having
more
mines
on
it
right
so.
E
What
one
obvious
way,
I
think,
is
to
just
go:
seek
out
the
growing
number
of
rust-based
open
source
projects
that
are
out
there.
You
know,
but
both
both
in
cncf
and
and
elsewhere.
I'm
biased.
Of
course
parsec
is
one
example
you
can.
You
can
go
and
learn
about
that
if
you're
interested
in
in
platform,
agnostic
security
but
but
the
num,
the
number
of
projects
is
growing
and
you
know
rust
is.
E
These
projects
are
crying
out
for
people
to
come
and
learn
the
language
and
and
get
involved
because
the
number
of
rust
developers
out
there-
you
know
it's
it's
growing,
but
it's
not
big
enough.
Yet
we'd
like
it
to
be
bigger,
so
so
yeah,
I
think
just
just
go
and
go
and
see.
What's
out,
there
would
be
one
of
my
calls
to
action
and
it
sort
of
goes
back
to
the
previous
question
as
well,
because
I
you
know,
I
think
usage
is
definitely
going
to
grow.
Ashley
already
mentioned
the
rust
foundation.
E
I
think
the
rust
foundation
is
a
is
a
great
step
forward.
You
know,
there's
this
independent
stewardship
stewardship
of
the
language,
not
to
mention
the
the
adoption
by
the
the
major
sort
of
the
major
hyperscale
cloud
players
as
well,
so
so
so
yeah,
I
don't
know
if
I
have
anything
better
to
say
other
than
to
just
go,
go,
find
the
go,
find
the
open
source
projects
that
are
out
there
and
and
find
a
way
to
get
stuck
in.
A
D
Yeah
I
mean
where
we've
seen
successes.
I
know
if
you're,
a
student
summer
of
code
is
a
great
or
or
some
of
these
kind
of
paid
internships
are
great
ways
to
get
involved
in
open
source,
and
I
I
think
definitely
my
strong
advice
is
to
go
through
the
open
source.
Trying
to
you
know,
there's
where
you
can
read
the
most
code
and
learn
the
most
and
there's
usually
like.
D
If
you
go
to
the
tokyo
discord,
for
instance,
it's
like
packed
full
of
people
talking
about
30,
different
projects
and
there's
you
know
if
you're
interested
there,
you
can
just
soak
up
a
lot
of
information
just
by
watching
yeah.
I
I
think
the
cloud
native
computing
foundation
hosts
now,
I
think
three
or
four
rus
projects,
if
not
more
and
so
there's
entries
there,
they
do
some
code
projects
every
year.
There's
things
like
crosslit,
which
is
if
you're
interested
in
kubernetes,
is
a
way
to
use.
D
D
Yeah
I
mean
like
I
I
I
mean
I
don't
know.
The
way
I
got
into
any
of
this
stuff
is
like
find
the
thing
that
you
want
to
spend
time
on
and
if
you
find
it
a
project
that
you
actually
want
to
spend
time
on,
you'll
get
good
and
you'll
get
involved
in
it,
and
you
know
that
usually
will
lead
to
something
good.
Hopefully,.
A
C
Well,
yeah
to
get
re
just
get
your
feet
wet
like
in
the
tokyo
github.
We
have
mini
redis,
which
is
a
kind
of
educational
project.
That's
trying
to
have
a
larger
real,
some
like
piece
of
software
that
you
can
read.
It's
well
commented
and
it's
also
the
foundation
the
tokyo
guide.
So
one
like,
if
it's
just
to
get
your
feet
wet,
you
can
go
and
like
try
to
add
a
new
implement,
a
new
redis
command
because
there's
a
redis
command
for
everything,
which
is
one
reason
why
I
was
like.
C
B
D
D
C
And
yeah
and
yeah-
and
I
think
the
biggest
like
air
missing
gap
again
for
me,
it's
tooling
and
like
little
like
just
writing
a
little
tool
to
do
a
little
small
thing
that
can
help
like
the
the
build
debugging
or
the
like
experience
around
building
things
like
you're,
probably
gonna.
Try
it
out
hit
friction,
build
a
little
tool
to
help
it
make
it
better,
and
that
will
like
there's
a
big
need
for
that
too.
B
I
would
also
just
shout
out
very
quickly
that,
while
they
are
by
no
means
perfect,
if
you're
interested
in
learning
rust,
we
have
the
rust
book
and
then
when
we
did
the
2018
edition
back
in
2018,
we
had
kicked
off
what
we
called
these
domain
working
groups
and
they
were
able
to
write
these
kind
of
intermediate
level
books.
So
it's
like,
oh
you,
know
rust,
but
now
you
like
want
to
do
something
with
russ
like.
Where
do
I
go
after
that
book
and
there's
a
book?
B
I
we
call
the
async
book.
That's
about
networking,
there's
also
a
webassembly
one,
so
I
it
can
often
be
the
trap
and
I'm
a
huge
fan
of
this
that
like
in
order
to
get
involved
with
open
source.
You
end
up
having
to
contribute
to
open
source,
but
that
can
be
a
super
heavy
lift
for
folks.
You
can
also
just
build
a
wacky
project
like
the
the
web
assembly
book.
For
example,
has
you
build
conway's
game
of
life,
which
honestly
continues
to
be
one
of
my
favorite
little
projects?
B
I
don't
know
you
can
do
we've
seen
really
cool
like
artsy
variants
on
it
that
are
just
super
awesome,
but
yeah.
You
can
also
just
feel
free
like
when
I
wrote
the
original
rust
bridge
curriculum.
We,
we
wrote
a
program,
that's
like
a
simple
website
that
will
randomly
give
you
a
compliment
every
time
you
refresh
it
so
just
coming
up
with
like
a
project,
that's
fun,
I
think,
is
really
the
best.
Don't
feel
like
you
have
to.
B
D
B
C
And
even
like
get
like
the
easy,
sometimes
the
easiest
way
to
involve
is
submit
apr
that
just
fixes
a
typo
like
we
love
like
I,
we
love
those
and
like
oftentimes,
we'll
see
people
come
like
I
don't
know
it's
just
a
typos
like
no
just
like
a
one
character.
Pr
is
great
just
first
to
get
involved.
Just
open
line
of
communication
start
talking
with
people.
D
D
A
Up
on
time,
so
we're
going
to
wrap
it
up
with
our.
You
know
final
open-ended
question
from
each
of
you,
which
is
if
you
could
have
embed
one
take-home
message
in
the
brains
of
our
audience
members.
What
would
that
be?
And
then
let's
do,
let's
do
the
opposite
order
from
what
we
did
in
the
first
question.
So
we'll
start
with
you,
oliver.
D
So,
every
time
I've
talked
about
lincoln's
proxy
over
the
past
few
kubecons,
and
things
like
that.
I
asked
people
to
raise
their
hands
if
they
tried
rust
and
like
a
couple
hands
go
up,
and
I
say
like
well
wait:
two
years
all
your
hands
will
be
up
and
then
last
year,
there's
like
a
little
bit
more,
but
I
really
think
that
now
is
the
time
to
start
playing
with
rust.
It's
ready
for
you
and
there's
a
lot
of
opportunities
to
still
get
involved
and
build
cool
things.
D
A
C
C
C
Easier
to
use
it's
gonna
like
it's
there's,
still
improvements
to
be
made,
but
every
you
know
month
we're
pushing
out
fixes
and
improvements
and
give
it
a
shot.
Now,
if
it's
seeing,
if
you
hit
off
off
something
like,
let
us
know,
because
we
can't
fix
things
that
we
don't
know
but
yeah
like
now,
now's
the
best
time,
it's
ever
been
to
try
rust.
E
Yeah,
I
think
I
well
for
start.
I
agree
with
with
all
of
that.
The
other
thing
I'd
say
I
guess,
is
I
I'd
echo
what
I
said
right
at
the
start.
Don't
don't
think
of
the
the
learning
curve
into
rust
as
as
pure
overhead
right?
It's
exactly
as
ashley
was
saying.
Is
it's
it's
investment
in
the
right
place?
You
know,
don't
don't
worry
about
fighting
the
you.
B
E
Should
celebrate
fighting
the
borrow
check
and
not
don't
be
put
off
by
fighting
the
borrower
checker?
It's!
You
know:
you're
you're
you're,
going
through
the
pain
at
the
right
time
and
and
saving
yourself
a
lot
in
the
long
run,
and
it's
a
beautiful
language
as
well.
I
have
to
keep
plugging
for
that
because
it
does
that
that
message
does
get
lost
in
amongst
all
of
the
all
of
the
other
messaging
around
last
rust.
E
B
Yeah
so
it
says,
what's
my
take
home
message,
but
I
might
reach
for
some
words
from
from
julia
evans,
also
known
as
bork
online.
She
does
a
lot
of
great
scenes,
particularly
around
systems
programming,
and
she
did
one
about
rust
and
what
she
said
about
rust
is
that
rust
makes
improbable
programs
possible,
and
then
she
also
says
that
rust
makes
her
think
hey.
Maybe
I
could
write
that
program
and
I
think,
there's
two
kind
of
messages
of
like
hope
and
empowerment
in
there.
B
One
is,
you
know
in
the
future
we're
going
to
see
more
systems
programmers.
So
if
you're,
someone
who
never
thought
like
you
could
be
a
systems
programmer
for
any
number
of
reasons
like
rust
exists
to
try
to
convince
you,
otherwise
that
it
can
help
you
do
that
and
that,
in
addition,
types
of
programs
that
we
would
otherwise
think
were
not
really
possible.