►
From YouTube: RustConf 2020 - Opening Keynote
Description
Opening Keynote
A
Welcome
to
the
russ
conf
2020
core
team
keynote,
I'm
manish
from
the
russ
core
team
and
I'll
be
giving
a
quick
forward.
First.
A
brief
note.
This
talk
was
recorded
before
any
of
the
recent
events
relating
to
mozilla.
Since
then,
we've
put
out
this
initial
response
on
twitter
as
well
as
a
post,
you
can
visit
on
the
main
rus
blog
at
blog.ruslang.org.
A
A
He
studies
computer
science
as
an
undergraduate
at
georgia.
Tech
aiden
is
co-lead
of
the
infrastructure
team
and
works
with
rusted.
Hadian
ashley
has
been
involved
in
the
crates.io
community
and
infrastructure
teams.
She
works
at
apollo,
graphql,
building,
rust
and
webassembly.
Tooling.
Nick
is
a
rust
engineer
at
pingcap
and
has
been
involved
in
the
compiler
language
and
death
tools.
Teams.
B
So
hello,
this
marks
the
fifth
birthday
of
rust.
That
is
this
year.
2020
marks
the
fifth
birthday
bust,
and
what
do
I
mean
by
the
fifth
birthday?
I
mean
that
five
years
ago
we
announced
rust
1.0
for
the
world
right.
We
basically
said
rust
is
open
for
business,
ready
for
use
and
we're
not
going
to
break
your
software
anymore.
If
you
were
using
rust
before
1.0,
you
know
that
we
broke
your
software
a
lot.
B
We
don't
speak
of
those
days.
Actually,
that's
not
true.
We
talk
about
those
days
all
the
time.
At
least
I
do,
but
anyway,
the
point
is
1.0
release
five
years
ago
very
exciting,
and
in
the
time
since
we've
seen
a
lot
of
people
using
rust,
more
and
more
people,
it
seems
like
using
rust
for
more
and
more
things
kind
of
more
things
than
I
ever
imagined.
B
B
Let
me
explain,
because
I
think
we've
come
to
understand
those
words
even
better
over
time
right
initially,
we
did
think
about
empowering,
because
we
thought
about
empowering
c
plus
plus
programmers.
We
knew
that
we
had
existing
systems,
programming
experts
like
the
ones
who
are
working
in
mozilla.
They
were
maintaining
million-line
code
bases
and
they
were
struggling.
B
It
was
just
more
than
we
could
muster,
but
if
we
could
find
a
new
language
that
would
solve
automatically
a
lot
of
those
problems
and
let
us
focus
on
the
things
we
actually
wanted
to
do.
Then
we
could
do
it
and
that's
what
rust
was
all
about
right
and,
of
course
you
do
see
a
lot
of
usage
across
in
firefox
today
and
more
every
year
and
that's
super
exciting.
A
B
Was
hey,
rust
is
a
new
language.
A
lot
of
you
have
problems
that
were
well
suited
to
systems
programming,
and
you
need
to
make
this
bit
of
code
more
efficient
and
before
it
may
not
have
made
sense
to
use
a
c
or
z
plus
plus
extension,
because
the
maintenance
hassle
wasn't
worth
it,
but
rust
changes
the
calculus
and
opens
the
door.
B
It
makes
a
lot
more
accessible,
and
so
that
began
this
really
cool
blend
that
I
think,
we've
seen
to
this
day
of
programmers
from
a
bunch
of
different
backgrounds
coming
together
to
work
in
the
same
language
and
in
the
same
community
and
bringing
these
different
experiences,
and
I
think
that
has
been
really
great
for
rust
and
one
of
the
key
things
that
you
can
see
even
in
this
first
example,
is
that
while
we
often
think
of
programming
communities
as
different,
we
think
of
like
cbos,
plus
programmers
and
ruby
programmers.
That's
already
a
bit.
B
Love
to
use
more
than
one
language,
it's
we're
not
like
distinct
things,
but
also
that
the
problems
and
the
experiences
from
one
community
can
really
help
the
other
they're
not
separated
at
all,
and
we
saw
that
with
rust
right
the
goal.
Here
we
were
targeting
the
problems
of
systems,
programmers
it
turned
out.
We
were
opening
doors
and
solving
problems
for
other
communities
too.
These
are
some
slides
from
julia
evans,
2016
keynote,
which
I
love,
and
you
know
we
were
by
making
improbable
programs
possible.
B
B
Let
me
give
you
a
few
examples.
First,
one
is
going
to
be
cargo
and
crates
io,
so
I
have
a
confession.
When
I
first
started
working
on
rust,
around
2011
or
so
people
were
talking
about,
you
know
adding
a
build
system
to
wrap
the
rust
compiler
and
I
kind
of
thought
I
don't
know.
If
we
should
try
to
do
this.
It
seems
too
hard
we're,
probably
just
going
to
end
up
recreating
make
files
but
worse,
it
seems
like
not
a
good
use
of
our
time
now.
B
That,
well,
you
know
I
thought
makefiles
were
good
enough,
but
I
hadn't
used
systems
like
rubygems
and
I
hadn't
used
npm.
I
didn't
really
know
what
software
reuse
could
really
feel
like.
Luckily,
there
were
a
lot
of
people
who
had
and
who
did,
and
luckily
we
did
build
cargo
and
we
also
built
crates
io
right.
This
repository
that
now
lets
you
upload
your
packages
and
download
and
reuse,
and
now
I
totally
get
it
it's.
B
You
know
it's
great
that
we
did,
because
if
you
look
at
messages
about
what
people
love
about
rust
or
about
their
first
experience
with
rust
or
something
like
that,
what
you're
going
to
notice
is
time
after
time
again
fargo
comes
up
every
time,
maybe
not
every
time
most
times.
It's
really
cool
and
I
mean
look.
There's
some
quotes,
I
scraped
off
of
reddit
and
so
forth,
but
this
person
they
hate
everything
about
rust.
B
They
hate
the
moduluses.
However,
both
sitters.
They
think
it's
ugly.
They
wish
they
were
javascript,
they
were
reciprocals,
I
don't
know,
but
they
love
cargo
right.
I
think
that
kind
of
tells
you
everything
you
need
to
know.
Another
page
I
thought
was
interesting.
Was
this
one
this
talks
about
if
you're
coming
to
us
from
different
backgrounds?
B
What
to
expect-
and
it
says
when
you're
coming
from
c
plus
plus
it
may
take
you
some
time
to
get
used
to
the
type
system
to
get
used
to
lifetimes,
but
in
the
meantime
you
can
enjoy
using
cargo
right
and
you'll
get
hooked
on
that,
and
then
you'll
figure
out
the
rest,
and
I
think
that
kind
of
tells
you
what
you
need
to
know
that
a
lot
of
times
you
might
be
thinking
like
there's
existing
systems,
programmers
they're
the
experienced
folks.
They
should
be
the
ones
leading
the
way.
B
That's
not
always
true,
sometimes
there's
people
from
other
communities
who
have
solved
this
problem,
and
it's
often
those
experienced
people
who
are
kind
of
trying
to
tell
you.
That's
not
a
problem,
we're
solving
that
benefit
the
most
from
the
solution,
and
I
can
say
personally
that
I
have
benefited
right
hacking
on
rust.
We
used
to
have
this
make
file
to
build
rust.
It
was.
B
B
We've
replaced
this
since
with
cargo,
it's
a
much
better
experience,
and
you
know
crazy
and
cargo
and
crates
are
great
tools,
they're
one
tool
of
a
large
family
of
tools,
and
I
think
that's
a
key
part
of
the
rust
experience
too,
that
we
really
tried
to
keep
our
tooling
and
our
accessible
and
fill
the
needs
that
people
have
to
be
productive
and
enjoy
using
west.
Let's.
B
Error
messages
so
rust
error
messages
around
the
1.0
time
period.
They
were
functional
right,
they
told
you,
they
usually
told
you
the
line
of
code
that
caused
your
problem
and
they
tried
to
tell
you
why,
but
they
didn't
necessarily
do
a
very
good
job.
I
think
most
of
us,
since
you've
got
experience
with
russ.
You
learn
not
to
read
the
error
message
and
just
to
jump
to
the
lineup
code
and
like
look
around
and
figure
out
what
was
going
on
now
that
all
changed
around
2016.
B
Was
that
we
want
to
well,
this
was
part
of,
I
should
say,
a
bigger
push
to
improve
new
users.
Experience
with
rust,
right
and
one
of
the
key
things
that
new
users
like
to
do
when
they
want
to
learn.
Rest
is
run
the
compiler
on
some
code
and
they're
going
to
get
errors,
and
so,
if
we
can
make
those
errors
better
and
help
them
understand
the
problem,
they're
more
likely
to
stick
with
rust.
That
was
the
idea
and
that's
what
led
us
to
these
awesome
error
messages
we
have
today.
B
It's
also
kind
of
what
you
know.
We
were
taking
some
inspiration
from
elm
and
from
some
other
packages
in
elma,
so
I
don't
know
about
different
dif.
There's
now
like
some
of
this
friendly
competition,
where
people
are
really
fighting
to
have
the
best
error,
messages
and
copying
ideas
from
one
another,
and
I
think
that's
awesome
right.
A
B
Can
we
make
it
that
you
don't
even
need
the
rest
book
just
get
all
the
information?
You
need
right
from
the
error
message.
I
don't
know
if
we'll
ever
get
there,
but
I
think
we're
getting
closer
and
closer
right.
It's
really
cool
esteban,
also
is
talking
later
in
muscov
check
that
out
now
all
of
this
stuff
was
focused
on
helping
new
users,
learn
rust,
improving
the
experience
when
people
first
start
with
rust,
but
is
it
only
new
users
that
benefit
from
good
error
messages?
No,
everybody
benefits
right.
B
B
D
B
Last
example
is
the
code
of
conduct,
I
think
most
of
you
know
it
should
come
as
no
surprise
that
the
internet
can
be
a
hostile
place.
There
are
a
bunch
of
jerks,
they
like
to
say
things
they're,
not
often
that
constructive
and
that
kind
of
gave
rise
to
a
movement
amongst
software
packages
and
open
source
communities
and
just
communities
in
general
to
establish
codes
of
conduct.
Right
and
rust
is
one
of
those
projects.
B
Part
of
it
is
to
make
the
language
a
more
inclusive
space
to
help
get
more
people
in,
and
you
might
think
then
that
that's
really
what
the
audience
is
for
people
who
aren't
currently
part
of
the
community
trying
to
make
their
experience
more
pleasant
when
they
first
join.
That's
true,
but,
interestingly,
if
you
look
at
what
motivated
graydon
he's
a
founder
of
rust
initial
person
who
started
the
project
and
who
insisted
on
the
code
of
conduct
at
that
time,
why
did
he
do
it?
B
It's
not
that
it
wasn't
for
other
people,
but
it
was
also
for
himself
right
because
he
had
been
a
part
of
many
different
open
source
projects
in
the
past
and
language
projects,
and
he
found
that
you
know
if
he
was
going
to
work
in
this
space.
He
wanted
to
work
with
people
who
are
respecting
these
precepts,
and
so
I
think
it's
a
good
case
of
focusing
on
the
needs
of
sort
of
newcomers
to
the
community,
who
might
be
turned
off
by
the
kind
of
style.
B
So
I
do
say
when
we
talk
about
code
of
conduct.
Another
key
part
of
having
a
code
of
conduct
is
having
an
enforcement
mechanism,
which
implies
moderation,
and
we
all
have
a
big
thank
you
for
the
moderation
team
that
does
a
very
difficult
job.
If
you'd
like
to
appreciate
how
difficult
it
is,
I
can't
recommend
enough
this
comment
by
burnt
sushi
the
urls
there.
B
B
It
goes
from
the
language
design.
You
have
things
like
the
ergonomics
initiative
to
the
way
that
we
run
our
project
right,
focusing
on
efforts
like
the
rusty
dev
guide
or
having
rfcs
and
teams
to
the
tools
that
we
use
to
run
the
project
like
github
and
so
forth,
they're
all
oriented
at
empowering
people
to
participate,
empowering
people
to
use
rust
and
to
learn.
So
I
think
it's
really
this
this
central
story
of
rust
itself,
but
I'd
like
to
hand
it
over
now
to
mark
who's
going
to
give
us
another.
C
The
key
element
in
making
us
the
language-
it
is
the
people
who
participate
in
our
community.
The
rust
team
also
tries
to
automate
what
we
can
to
keep
our
human
population
happy,
but
we
currently
have
305
team
members.
There
are
many
more
people
discussing
and
contributing
to
us
on
github
and
our
forums.
C
C
C
C
E
E
In
fact,
evolution
can
be
a
good
thing,
so
it
means
the
project
is
adapting
to
growth
and
changes
and,
as
an
example
of
this,
the
teams
within
rust
didn't
exist.
When
the
project
first
started,
it
was
as
a
response
to
the
growth
and
the
emerging
responsibilities
and
rfcs
are
another
example
of
an
evolution
in
rust.
E
E
E
So
one
of
the
core
promises
around
rust,
which
nico
touched
on
earlier,
was
around
making
it
feasible
to
write
applications
of
a
particular
kind,
and
part
of
this
is
about
reliability,
one
of
the
key
promises
of
rust.
It
just
eliminates
certain
classes
of
bugs
at
compile
time.
You
don't
have
to
think
about
them.
E
Another
example
of
this
is
the
module
system,
and
this
is
something
that
the
rust
project
iterated
on
so
the
language
team
as
part
of
a
project
to
identify
the
things
that
people
found
difficult
to
understand
or
work
with
observed.
The
module
system
that
was
released
in
russ
1.0
was
confusing
and
so
actually
created
a
set
of
rfcs
to
discuss
and
design
a
solution
for
this,
which
was
eventually
landed
and
is
now
the
is
now
available
in
russ
2018.
So
if
you.
E
So
one
example
is
errors
which
was
covered
earlier
on
by
nico,
which
has
had
a
lot
of
effort
put
into
it,
and
this
user
has,
in
years
of
using
rust,
encountered
an
unhelpful
error
message
for
the
first
time
and
as
it
happens,
this
was
improved
shortly
afterwards
and
it
kind
of
demonstrates
the.
It
demonstrates
the
success
of
errors
that
this
is
the
first
one
in
those
years.
E
E
Finally,
the
team
structure,
the
creation
of
teams,
is
something
that
gives
people
power
within
the
project
to
have
their
say
to
contribute,
and
this
is
something
that
is-
we've
been
talking
about
for
a
while.
So
this
is
a
slide
from
the
2018
ruscom
court
team
keynote
and
talks
about
making
a
space
for
people
to
step
into
to
help
out
in
the
project.
F
Thanks
aiden,
so
we've
just
heard
that
you
know
great
technology
is
built
both
for
and
by
people,
and
that
is
a
critical
value
involved
in
building
great
technology.
But
I
do
think
that
the
term
great
technology
can
be
somewhat
kind
of
ambiguous,
or
at
least
vague,
maybe
to
the
point
of
meaninglessness,
and
so
I'd
really
like
to
bring
definition
to
that
term
by
centering
it
around
this
concept
of
impact,
and
so
I
think
one
can
say
that
great
technology
is
technology.
F
That
has
impact,
and
I
think
that
begs
the
question
then
of
what
does
it
mean
for
a
programming
language
to
have
impact,
and
this
can
feel
like
a
very
philosophical
question
which
may
be
coming
from
me
is
unsurprising
to
many.
But
I
actually
think
this
is
a
question
that
rust
has
been
asking
itself
since
very
very
early
on,
and
I
think
it
has.
F
So
what
do
we
mean
when
we
say
empowering
and
empowering
everyone?
So
russ
wants
to
be
empowering.
I
think
this
is
really
central
to
a
lot
of
the
reasons
why
people
like
working
on
rust.
I
also
think
that
the
concept
of
empowerment
is
central
to
a
lot
of
rus
ability
to
be
incredibly
successful,
but
I
think
the
term
empowering
hides
within
it
a
lot
of
interesting
and
like
really
poignant
complexity.
F
So
it's
not
a
talk
right.
If
we
don't
like
look
something
up
in
the
dictionary
and
we're
gonna
do
that
for
a
while
in
this
section,
but
the
term
in
power
here
is
a
verb,
meaning
to
give
someone
the
authority
or
power
to
do
something,
and
I
don't
think
that
that
should
blow
anyone's
mind,
but
something
that
I
think
is
really
critical
in
here
is
that
at
the
center
of
the
word,
empowering
is
the
word
power
and
power
is
a
really
really
interesting
and
really
important
concept.
F
So
here
what
I've
done
is
kind
of
an
inverse
lookup,
but
I've
looked
up
the
term
politics
which
now
people
might
be
going
ashley.
What
are
you
doing?
This
is
a
talk
about
programming,
languages
and
now
you're
bringing
politics
in
it
don't
be
that
person.
But
what
I
want
to
say
is
by
bringing
up
our
slogan
that
we
seek
to
empower
everyone.
I've
actually
already
we've
already
brought
politics
into
it,
because
what
is
politics
so?
F
The
first
half
of
this
definition
says
activities
associated
with
governance
of
a
country,
and
so
that's
probably
what
most
people
think
of
the
term
politics
when
they
originally
think
of
it.
But
I
think
this
second
portion
is
the
part
that
is
significantly
more
interesting.
So
here
it
says,
especially
the
debate
or
conflict
among
individuals
or
parties
having
or
hoping
to
achieve
power.
F
And
if
you
recall,
we
have
this
key
word
empowering
inside
of
our
slogan.
So
the
idea
of
politics,
which
I
would
just
define
as
systems
of
power
right,
because
rust
seeks
to
be
empowering.
We
are
already
seeking
to
be
political
right.
Rust
wants
to
be
political,
and
this
may
be
a
controversial
thing
to
say.
F
I
could
imagine
that
there
are
people
who
are
frustrated
by
this,
but
at
the
end
of
the
day,
I
think
it
is
by
far
one
of
the
most
core
and
foundational
concepts
in
rust
to
the
point
where
it's
not
just
that
we
want
to
be
political,
it's
that
we
always
have
been
political
and
that's
something
that
we
think
is
really
important.
Now.
This
also
isn't
terribly
surprising
right.
F
It's
true
that
ex
rust
is
trying
to
be
explicitly
political,
but
all
technology
is
political,
because
technology
fundamentally
gives
certain
sets
of
people
power
and
the
ability
to
achieve
all
sorts
of
things.
The
way
we've
seen
software
completely
changing
our
society
and
our
world
right,
so
technology
is
political.
F
Whether
it
wants
to
be
or
not-
and
I
think
it's
great-
that
rust
really
wants
to
explicitly
be
political
howard,
zinn,
and
I
think
many
other
people
have
said
something
to
this
effect
have
kind
of
said.
You
know
you
can't
stand
still
on
a
moving
train
right.
Technology
is
political,
so
we
can,
we
can
choose
to
say:
oh
russ,
it's
just
a
programming
language,
it
can't
be
political
or
we
can
embrace
that
and
and
try
and
do
our
best
to
be
as
deliberate
and
focused
on
our
political
aspects
as
we
possibly
can.
F
So
what
I
think
what
I
think
about
our
slogan
of
russ,
wanting
to
empower
everyone
to
empower
people
is
that
our
fundamental
relation
to
power
is
that
we're
really
interested
in
redistributing
it,
which
is
an
incredibly
you
know,
powerful
idea,
no
pun
intended
right.
So
what
does
this
mean?
So
we've
talked
about
how
the
rust
project
focuses
its
values
on
people,
and
I
don't
think
that
many
people
would
think
that
that
is
terribly
controversial.
F
But
I
think
it
starts
getting
really
interesting
when
we
acknowledge
that.
Well,
we
want
to
help
everyone,
and
we
want
to
empower
everyone
at
some
point
when
we
think
about
things,
we
need
to
choose
certain
people,
and
so,
while
in
our
previous
conversations,
we've
referenced,
the
idea
that
there's
false
dichotomies,
that,
like
a
seepless
plus
developer
and
a
ruby
developer,
still
aren't
really
all
that
different,
and
I
genuinely
believe
that
to
be
true.
F
So,
in
the
rest,
2018
keynote,
I
made
this
captain
power.
Captain
planet
captain
planet
slide
where
I
talked
about
all
the
different
audiences
that
we
see
in
the
rust
community.
You
know
we
have
like
the
rust
rust
die,
hards
that
have
always
been
rust,
always
forever.
We've
got
folks
from
academia.
We've
got
folks
coming
from
lower
level
languages
like
c
people's
plus
assembly.
We've
got
some
higher
level.
F
Scripting
language,
people,
javascript
python,
ruby,
we've
got
people
who
have
never
programmed
before
who
come
to
rust,
wanting
to
be
programmers
so
brand
new
folks-
and
this
is
part
of
the
like-
really
vibrant
diversity.
That
I
think,
makes
rust,
really
really
amazing,
but
we
cannot
all
these
different
audiences
have
very
different
needs.
F
Y'all
should
check
it
out
because
it's
not
nearly
maybe
what
I
think
the
rust
ideology
has
kind
of
adopted
this
slogan
to
mean,
but
in
here
there's
like
a
hidden
judgment
right,
I
think,
and
the
judgment
is,
is
something
that
I
think
we
can
all
agree
on,
which
is
so
we
say
a
rising
tide
lifts
all
ships.
The
judgment
here
is
that
a
rising
tide
should
lift
all
ships
and
that's
something
that
we'd
really
want
to
be
the
case.
F
F
Our
focus
and
our
attention
is
by
far
our
greatest
resource,
and
it's
certainly
the
resource
from
which
we
can
derive
the
absolute
most
value,
and
so
the
real
question
here
is,
as
we
focus
ourselves
on
people
as
a
project
that
values
like
the
humanity
of
technology,
like
what
should
we
focus
on?
Where
should
our
focus
be,
and
so
what
we've
settled
on?
Is
we
really
genuinely
believe
that
we
should
center
on
people
who
have
the
most
need?
F
So
as
we
look
at
this
slogan,
a
language
empowering
everyone
to
build
reliable
and
efficient
software,
I
don't
want
you
to
think
that
we've
thrown
this
everyone
out.
However,
I
think
that
this
is
true,
but
there's
a
core
of
it.
That
is
truer
which
is.
We
are
a
language
empowering
everyone,
but
especially
folks
who
didn't
think
that
systems
programming
was
for
them.
There
was
a
big
argument
about
whether
or
not
we
should
include
the
term
systems
programming
in
our
slogan,
and
we
ended
up
taking
it
out.
F
Largely
because
it's
been
such
a
gatekeeping
term,
it's
kept
people
away
because
so
many
people
self-identify
as
someone
who
could
never
be
a
systems
programmer
and
while
it's
not
in
our
slogan,
because
that
sentiment
around
the
gatekeeper-ness
of
the
idea
of
systems
programming
is
a
hundred
percent.
True
at
the
core.
F
We
still
want
to
take
that
concept
of
systems,
programming
and
break
it
free
from
that
sense,
because
we
want
it
to
become
something
that
is
accessible
to
everyone
and
in
that
sense
we're
trying
to
redistribute
the
power
of
systems
programming
and
that
redistribution
is
our
impact
and
it
is
fundamentally
political
whether
or
not
you
find
that
distasteful,
and
it's
something
that
I
think
the
rust
project
is
incredibly
excited
about,
and
so
we've
done
a
lot
of
really
interesting
things.
There's
things
where
we've
been
able
to
see
this
today.
So
this
is
rebecca.
F
Rebecca
is
one
of
his
speakers
today
here
at
ruskoff
and
she
had
tweeted
that
it
kind
of
owns
that
more
than
50
of
the
ruscom
speakers
are
trans
this
year
and
I
gotta
say
like
that
is
so
freaking
cool.
I
have
never
been
to
a
conference
where
that
is
true,
and
I
am
really
proud
that
that
conference
that
I
get
to
experience
that
at
is
rustcoff,
and
I
I
also
don't
think
it's
a
coincidence.
F
F
If
we
really
want
to
achieve
that
ambition
of
redistributing
the
power
of
systems
programming,
we
we've
got
a
lot
of
work
to
do
right
and
if
there's
anything
you
hear
from
me
today,
it's
that
rust
has
some
pretty
amazing
ambitions,
and
these
ambitions
are
what
motivate
me
to
work
on
rust
and
that's
awesome.
But
but
our
ambitions
right
now
are
currently
greater
than
our
capacity.
F
We
we've
got
dreams
of
doing
some
pretty
big
things,
but
we
want
to
do
them
right
and
doing
them
right
means
that
we
need
to
create
more
capacity
for
ourselves
to
be
able
to
achieve
those
goals.
I
was
talking
with
my
friend
jenn
schiffer
recently,
and
we
were
talking
about
these
concepts
of
accountability
and
aspiration.
F
But
what
we
really
need
now
is
accountability,
and
I
think
that
we
know
what
we
want
to
do
and
we
now
need
to
build
the
organization
that's
going
to
get
us
there
and
to
do
that.
We're
going
to
need
all
of
your
help.
So
it's
time
for
us
to
grow
and
everybody
who's
in
this
audience
today,
who's
watching
this
at
home.
We,
we
really
need
you
to
get
involved,
and
so,
if
these
ambitions
and
these
aspirations
that
I've
shared
about
haven't
scared,
you
have
excited
you
describe
a
future
that
you
want.
D
So
we've
got
to
grow
to
achieve
the
things
we
want
to
achieve,
but
we've
got
to
grow
sustainably.
You've,
probably
all
seen
that
rust
for
the
fifth
year
running,
was
the
most
loved
programming
language.
According
to
the
stack
overflow
survey,
I
want
to
look
back
in
another
five
years
and
see
us
getting
that
spot.
You
know
for
the
10th
year
running
and
I
want
to
look
back
and
see
rust
getting
better
and
better.
D
D
D
If
you
look
at
rfc
2966
and
the
way
that
lays
out
how
we'd
like
to
to
run
the
2021
edition,
the
idea
is
that
we're
going
to
have
additions
on
a
regular
cadence,
much
like
our
six
weekly
releases
that
that
ride
their
trains.
The
addition
are
going
to
ride
their
own
trends.
It's
just
going
to
take
three
years
to
come.
D
So
that
means
that
there
should
be
no
high
pressure
deadlines
to
get
stuff
finished.
For
for
the
addition,
and
hopefully
that
will
make
it
a
much
less
stressful
experience,
we
are
intending
to
continue
to
improve
our
governance
and
organizational
structures
and
now's
a
good
time.
We'd
like
to
say
thank
you
to
the
governance
working
group
they've
been
active
for
the
last
year,
roughly
and
they've
done
some
really
great
work.
D
Looking
into
the
the
various
governance
structures
that
we
have
and
ways
that
we
could
make
them
better,
we're
also
gonna
we're
also
actively
exploring
starting
a
rust
foundation.
The
primary
motivation
for
that
is
financial
and
that's
an
important
part
of
looking
after
each
other
in
the
capitalist
societies
in
which
we
live.
We
we
talked
about
rfc
as
earlier
in
this
talk,
and
rfc
is
a
really
important
way
that
we
we
keep
the
the
evolution
of
rust
open,
but
they
can
also
be
hard
work.
D
D
Now,
some
of
the
work
that
we
do
necessarily
has
to
remain
private,
but
a
lot
of
it
doesn't,
and
we
have
a
large
part
of
our
weekly
meetings
of
public
pietro,
announced
back
in
july
that
we're
experimenting
other
way
to
open
up
the
the
public
part
of
the
core
team
agenda.
For
so
that
everyone
can
follow.
D
I
also
want
to
go
over
some
of
the
concrete
ways
we
hope
to
continue
to
empower
our
users
on
the
language
side
of
things,
we're
going
to
continue
to
focus
on
ergonomics
and
on
usability,
and
I
think
the
development
of
async
await
is
a
great
example
of
that.
Async
programming
is
difficult,
but
async
and
weight
certainly
makes
that
much
easier
and
as
we
go
forward,
hopefully
we're
going
to
have
to
make
it
easier
still
and
to
have
a
more
complete
solution.
D
D
D
D
The
infra
team
have
also
done
great
work
to
make
our
infrastructure
easier,
to
contribute
to
it's
hard
to
think
of
anything,
more
important
for
building
a
sustainable
community
than
safe,
inclusive
spaces,
and
I'd
like
to
say
thank
you
to
the
mod
team
at
this
point
because
they're
a
big
part
of
that
and
they
do
a
really
difficult
job.
So
thank
you.
D
D
We
believe
that
having
a
diverse
community
is
really
important
and,
to
be
honest,
this
is
somewhere
where
we
haven't
done
as
well
as
we
would
have
liked.
There
have
been
some
good
bits.
Some
highlights
rustbridge
increasing
reach
just
to
name
a
couple,
but
overall
this
is
not
somewhere.
I
think
that
we've
excelled.
We
need
to
do
better
and
we
will,
over
the
the
coming
year
and
into
the
future,
we're
gonna
make
building
a
diverse
community
one
of
the
highest
priorities
for
the
rust
project,
so
that
all
reflects
our
strategy.
D
D
D
Don't
let
yourself
get
burnt
out
that
added
stress
is
makes
burning
out
so
much
easier.
If,
if
it's
helpful
for
you
to
do
less
work,
please
do
do
less
work
be
kind
to
yourself.
We,
we
don't
kind
of
need
heroes
to
to
be
a
sustainable
project,
but
we
do
need
people
who
are
going
to
be
around
for
the
long
term
and
please
look
after
each
other
again
in
when
times
are
tough.
D
It's
really
essential
work
to
to
do
if
we're
going
to
have
a
sustainable
project
and
a
sustainable
community,
and
I
think
rust
really
does
have
one
of
the
best
tech
communities
around,
but
we
can
always
do
better
and
as
it
grows,
we've
got
to
keep
doing
this
work
in
order
to
to
keep
it
good
and
to
keep
it
getting
better.
I
just
want
to
shout
out
to
the
awesome
rust
mentors
website,
which
was
put
together
by
jane
lusby.
D
D
Empathy
is
how
you
understand
the
needs
of
another
group
and
being
empathic
to
our
users,
is
how
we've
developed
the
language
into
being
a
good
language
frankly
and
being
empathic
towards
each
other
is
really
important
for
having
productive
and
enjoyable
discussion
rather
than
horrible.
Stressful
arguments
online.
D
That's
all
from
us.
I
hope
you
recognize
the
community
you're
you're
part
of
in
this
talk,
and
hopefully
it's
something
to
to
think
about
about
how
we
can
keep
it
awesome
as
we
grow
and
as
the
language
matures
we'd
like
to
finish
by
saying
some
thank
yous
we'd
like
to
thank
the
ruskconf
organizers,
leia
and
skylight
have
basically
made
everything
work,
including
the
transition
to
a
online
conference.