►
From YouTube: Lightning Talks: Rust In Space — myrrlyn
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I'm
Merlin
pronounced
like
the
wizard
I,
am
officially
a
satellite
software
engineer.
I
work
at
a
subsidiary
of
Utah,
State,
University
and
I
have
used
Russ
since
mid-2016.
The
first
draw
spell
trust
was
my
first
conference,
so
I
build
program,
tests
and
operate
satellites
I
have
nothing
to
do
with
Q
boss.
They
do
a
cool
stuff,
but
I
have
never
used
it
or
looked
at
it.
I
also
showed
it
into
do
two
of
those
things,
but
we're
a
small
company
and
I
was
the
only
person
willing
to
show
up
at
midnight
and
do
bad
things.
A
So
there
I
was
so
yeah
I
work
on.
You
know
satellites
like
this
very
nice
piece
of
iridium.
There
are
77
iridium,
satellites
and
they're
coming
out
of
the
sky.
So
if
you
want
to
see
flares-
and
now
is
the
time
just
kidding,
I
don't
touch
those.
Those
are
expensive
and
my
company
is
too
small.
I
make
cube
size
there.
In
the
palm
of
your
hand,
please
don't
hold
them
I
shouldn't
even
do
that.
I
definitely
have
it's
bad.
A
So
once
upon
a
time,
I
was
subcontracting
for
a
subcontractor
for
NASA
long
story,
but
if
there's
NASA
in
there,
so
you
know
it's
cool
and
I.
Have
some
memory
testing
to
do
so.
I
thought:
there's
a
very
important
tool.
I
have
available
to
make
sure
that
the
weird
components
down
in
that
box
are
working
correctly,
so
I
reached
from
my
favorite
language
Swift.
A
So
some
of
you
might
be
thinking
Swift,
that's
a
really
heavy
language.
That
also
runs
only
on
Apple
devices.
Are
you
flying
an
iPhone
and
yes,
people
have
literally
done
that
I
wish
I
was
joking
god,
I
wish.
That
was
a
joke,
they're
very
powerful
computers,
they're
armed
ships,
the
red
heart
and
you
can't
fly
them
I'm
kidding.
Of
course,
though
this
is
a
Ross
conference.
I
didn't
use
that
Swift
I
used
this
one,
that's
also
not
a
joke.
Follow
me
on
Twitter,
so
I
don't
write
was
rust
at
work.
I'm.
A
Very
sorry
to
tell
you
all
that
I
write
things
like
C++,
Python,
Ruby
and
C.
The
bad
C
I
wish
I
didn't,
but
I
target
a
very
old
version
of
an
operating
system
called
vxworks
and
the
compiler.
We
have
only
likes
C,
89
I
wish
this
was
a
flashlight,
so
you
can
see
the
afore
that
you
should
be
feeling
right.
Now.
A
We
use
Ruby
and
Python
for
the
groundwork,
I'm
a
very
talented
and
Multi
faster
than
individual.
We
don't
fly
those
they're,
very
slow,
so
I,
don't
write,
write
rust
at
work,
but
I
want
to
so
rust
has
helped
me
out
in
a
supporting
way
for
a
lot
of
my
work
so
far,
I've
not
even
two
years
old
at
this
company.
So
the
fact
that
I've
been
on
like
four
projects,
is
kind
of
weird
but
I
wrote
a
kernel
module
in
C
89.
A
It
was
hard.
It
was
a
networking
middleware
that
took
messages
from
a
different
computer
on
the
same
bus
held
them
in
the
kernel
and
then
pretend
that
there
were
16
different
device
files
and
that's
more
or
less
how
everything
in
/dev
works
on
Linux,
which
is
to
say
badly,
so
I
rewrote
it
in
rust
at
home.
On
my
own
time
and
I
found
well
I'm
bad
at
writing,
C,
which
is
a
sentence.
A
Everyone
who
compiles
C
should
say
so:
I
rewrote
it
in
rust
and
then
I
found
all
my
bugs
and
then
I
rewrote
it
in
C
still
89,
because
good
things
don't
happen
to
me
and
this
time
it
worked
very
well.
I
also
wrote
and
network
multiplex
are
in
rust.
So
this
was
a
thing
that
handled
all
the
data
coming
down
from
our
satellites
looked
for
a
very
specific
type
of
packet,
filtered
that
specific
packet
out
rebuilt
the
messages
from
it
it
took
about
a
day.
A
It
was
very
fast
because
I
didn't
have
to
do
all
the
weird
things
like
finding
a
needle
in
a
haystack
of
a
binary
stream
or
whatever
else,
I
use,
because
I
just
search
at
I/o
for
binary
search,
I,
think
I,
don't
know
the
criterion,
but
I
found
a
thing.
I
put
it
in
it
worked
great.
This
was
C.
I'd
have
had
a
bad
time,
we're
implementing
it
myself.
So
that
was
a
success
and
then
this
happened.
So
this
number
means
a
lot
to
people
in
my
field
and
probably
nothing
to
you
guys.
A
This
is
how
many
cube
SATs
we
launched
from
the
planet
that
never
talked
for
one
reason
or
another:
the
rocket
kills
them.
They
don't
launch,
they
don't
turn
on
once
they
launched,
we
don't
know
they
never
talked
to
us.
We
don't
know
why
they
died,
but
my
mission,
which
I
can't
tell
you
what
it
was
called
or
for
whom
it
was,
was
one
of
those
22%.
A
So
for
the
next
about
six
to
ten
months,
there
is
a
piece
of
aluminum
about
the
size
of
a
loaf
of
bread,
whizzing
around
the
earth,
slowly
falling
at
the
atmosphere
and
then
one
day
it
will
die.
So
my
network
multiplexer
never
got
off
the
shelf.
So
that's
what
I've
done
so
far
at
work.
Rust
has
helped
both
of
those
in
the
auxiliary
manner
and
it's
time
to
collapse
on
the
hurry
up.
A
cosmonaut
is
a
cool
project
that
I've
been
working
on.
This
is
all
in
present
tense.
That's
all
a
lie.
A
It
does
this,
and
this
and
those
don't
exist
yet
I'm
still
working
on
them.
It
barely
exists.
It's
a
learning
project.
Rust
has
a
lot
of
resources
that
have
been
really
really
cool
for
me
to
learn
how
to
program
and
domains
that
I
didn't
know
before
didn't
happen.
School
is
required
to
be
open-source,
but
because
I
worked
for
the
military-industrial
complex,
it
is
probably
read
only
because
ITAR
exists
and
I,
don't
like
it.
So
in
conclusion,
I
haven't
flown
rust.
A
Sorry,
it's
usually
empowered
to
see
that
I
have
delivered
and
that
it
found
all
the
bugs
that
I
didn't.
It
made
me
a
better
programmer
and,
most
importantly,
space
loves
love's,
love's
safety.
We
take
that
very
seriously
and
everything
we
do
software
hardware
process,
all
of
it,
so
my
company's
very
psyched
about
where
rust
is
going
in
the
future.
We
want
to
start
using
it.
It's
just.
We
have
weird
targets
and
not
even
our
LLVM
hits
them
so
we're
kind
of
stuck.
Thank
you.