►
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
A
A
I
work
at
iog
on
ascal.nic,
so
I
historics
is
not
really
linked
with
my
company
I
opinion
on
my
own
everything,
and
there
is
a
little
URL
here.
If
you
go
on
it,
you
will
be
an
SSH
link
and
if
you,
until
it's
this
link
in
in
your
fancy
terminal,
you
will
have
exactly
the
same
thing
that
on
my
screen,
so
you
can
copy
call
copy,
paste
everything
so
and
sorry
for
my
French
English
accent
and
what's
behind
this
really
fancy
and
delivery.
A
Vague
title
of
I
want
to
talk
about
my
personal
quest
of
interoperability
and
a
technical
challenge.
I
I
take
really
seriously
since
a
long
time
and
I
I
still
realized.
That's
a
lot
of
commercial
developer
around
me.
Don't
already
are
not
really
comfortable
with
this
problem,
because
We
have
basically
one
supporters
that
run
into
one
runtime.
For
example,
let's
say
rest
another
one
which
is
in
another
runtime,
let's
say
C
or
python
or
ascare
or
whatever
you
want,
or
it
could
be,
for
example,
two
rest
version,
two
different
version
or
two
pieces
of
software.
A
A
I,
don't
want
to
use
the
library
inside
this
project
and
the
library
is
not
written
in
the
same
language
or
I
mean
in
big
companies
or
is
a
lot
of
Legacy
code
and
it's
not
reasonable
to
rewrite
it
from
scratch,
because,
usually
that's
the
kind
of
things
that's
it's
hard
to
to
mix
validate
so
I,
rather
want
to
write
rewrite
piece
of
my
software.
So
in.
B
A
Of
this
case,
I
have
this
painful
issue
of
interoperability
between
Advanced
pieces
of
software,
and
so
when
we
have
a
lot
of
solution
for
problem,
we
usually
want
to
to
rate
all
this
solution
and
in
rest
we
often
see
this
diagram
for
sharing
for
sponsoring,
commercialized
language
or
rest
say
it
live
with
little
Rainbow.
It's
also
safe,
safe
and
fast
together
and
I'll.
Try
to
talk
about
different
interoperability.
A
Solution
on
this
diagram
and
our
soil
visualize
realize
that
from
the
rest
Forks
around
me,
there
is
maybe
half
of
the
persons
that
come
from
a
really
system.
Programming
background
with
fast
programming.
Language
fast
is
big,
ambiguous
as
a
term
for
speaking
about
the
programming
language,
but
with
a
small
runtime
and
such
looks
for
safety
coming
to
arrest,
and
there
is
the
other
side
of
developers
that's
coming
from
script,
language,
web
mobile
or
other
parts
where
computers
everywhere
language
are
usually
safe.
A
So
if
most
of
you
coming
from
system
programming,
what
I
will
talk
about
in
the
first
part
of
my
talk
will
be
really
trivial,
so
I
don't
know
if
I
can
make
a
quick
pull
around
you
or
who
are
really
comfortable
in
system
programming
and
know.
What's
I,
don't
know
package
config
and
are
not
confused
with
the
object,
introspection.
I,
don't
know
this
kind
of
stuff.
I
just
was
working
things
I,
don't
know
or
who,
if
so,
one
we
in
the
room
will
feel
comfortable
with
stem
programming
and
resonant
just
to
take
the
temperature
of.
A
Are
you?
Are
you
feeling
yeah,
okay,
alfalf,
okay,
nice
and
so
there's
a
lot
of
interoperability
solution?
I
will
not
give
all
the
name.
We
see
ECP
and
error
process.
Communication.
Epc.
Sorry
in
the
previous
talks,
there
is
a
lot
of
things.
I
put
this
word,
for
example,
Google
protocol
buffers,
that's
severalized
things
you
can
put
it
in
a
file,
and
so
that
is
it
outside
in
another
runtime.
You
could
have
Micro
services
that
sends
I,
don't
know
websocket.
We
can.
A
We
have
a
lot
of
different
solution
and
to
ask
yourself
it's
it's
fast.
It
will.
Will
it
be
a
performance
bottleneck
in
terms
of
runtime
cost?
You
can
ask
if
your
way
of
communicating
use,
OS
capabilities,
that
the
for
example,
that
did
rely
on
input
output
did
we
rely
on
asking
something
from
the
OS,
because
if
it
does
that,
basically,
your
operating
system
has
the
right
to
put
your
program
in
post
during
so
time
it
gets
the
answer
to
this
question
to
OS
capabilities
to
Cisco.
A
So
so
that
means
that
in
the
grand
scheduler
of
your
opposite
writing
system
is
a
reasonable
to
neck.
Every
time
you
do
an
IO.
If
you
could
not
do
it,
you
it's
better,
not
do
it
and
there
is
also
always
a
cost.
In
runtime
standardization
deserialization,
there
is
cool
serialization
formats
that
use
binaries,
which
is
really
efficient
in
space.
A
There
is
fast
to
deserial
ISO,
but
if
you
can
prevent
to
do
this
step,
this
extra
step,
you,
you
save
a
rest
time
cost
so
we'll
talk
about
the
most
basic,
primitive
technique
to
share
data
between
runtimes,
which
is
ffi.
That's
does
not
rely
on
any
OS
file
or
socket
address
or
and
does
not
require
extra.
This
realization
a
bit
a
bit
kind
of
a
bit
of
typecasting,
but
not
so
much,
and
so
here
we
go
I
I
switched
to
to
demo
mode.
A
A
Yeah,
this
main
use
next
term
keyword,
that's
the
magical
keyboard
to
say
to
rest.
Go
fetch
a
function
from
the
outside
of
your
program.
I
will
try
to
make
two
rest
program,
communicate
to
separate
rest
program
without
using
cargo
without
using
a
standard
way
of
putting
rest
piece
of
code
together
and
yeah.
Extend.
Allow
me
to
not
have
to
have
a
function
without
the
body,
and
this
is
of
course,
unsafe.
A
I
should,
according
the
function
in
an
SF
block,
everything,
cool
and
I,
have
libraries
that
live
in
I,
think
greetings
repository
and
that
basically
does
nothing.
I
need
Alex
little
extra
thing.
I
need
no
mangle,
because
I
want
to
prevent
a
default
things
that
does
resonance.
That
does
simplest
plus
2,
which
is
mangling
symbols
you
know,
function
will
become
symbols
in
binary
and
symbols
are
usually
random.
Things
created
by
the
compiler
and
here
I
want
to
not
change.
A
You
know,
I
want
to
keep
it
because
I
want
to
be
able
to
call
it
from
the
outside,
as
I
thought
it
was.
The
external
keyword
do
is
that's.
You
have
to
tell
an
extra
thing
to
the
compiler
to
do
that
and
I
I.
Think
if
I
do,
that,
I
have
I
need
two
more
thing:
I
need
to
a
build.rs
customization,
to
tell
let's
see
Linker
where
to
find
the
library,
and
what's
the
name
of
the
library
and
I
undily
already
compiled
the
library
and
she
live
in
greetings,
Target,
debug
and
she's
dot
is
Source.
A
It's
a
Dynamic
Library.
If
I,
if
I
can
recompile
it
to
show
you
it
works.
So
you
can
trust
me.
I
have
a
warning
but
I
don't
care,
I,
I,
just
work
and
and
yeah
it's
compiled
I,
it's
it
compiled.
It
just
told
me:
it's
the
running,
I
fit
I,
run
it
compiled
to
and
in
Trend
and
I
have
no
issue
at
all,
and
everything
is
fine.
Since
I
I
will
still
look
at
the
warning.
A
Warren
took
me
about
C
types
and
things,
and
why
why
why
and
the
thing
is
I
I
do
not
know,
but
external
in
fact
is
an
alias
and
Alias
II
external
C.
You
you
same
since
that
word.
Is
that
because
it
use
the
C
call
conventions,
it's
a
way
to
you
to
call
function
in
C
to
to
allocate
this
type
to
put
the
function
of
the
stack
to
three
things
after
and
the
way
to
to
usually
to
to
write
the
the
format,
the
protocol
to
put
different
argument
and
return
value
in
C
I.
A
A
I
want
to
say
rest
here
too,
but
you
know
external
rest.
In
fact,
it's
it's
not
needed,
because
all
the
functions,
use,
rescue
conversion
or
the
function
need
are
external.
By
default,
the
only
things
you
need,
in
fact
it's
not
your
external
keyword,
it's
a
nomangle!
That's
the
things
we
care.
So
this
works.
We
just
don't
touch
the
symbol.
We
do
not
need
the
external
keyword
and,
if
I
I
build
that
it
will
Works
without
warning,
so
I'm
really
happy
and
if
I
go
back
to
the
main
folder
and
I
run
it.
A
A
Why
why
you
displayed
yeah?
You
have
a
part
of
my
screens,
yeah
see
you
see
it,
it
works
sorry,
I,
don't
care
and
I'm
really
happy
everything
works
and
so
stalking
is
is
good
and-
and
maybe
you
know
it's
it's
if
I
try
to
recap,
our
function
are
externals
by
default
externally.
Find
curve
convention
used
it's
not
about
visibility
like
a
pubic
reward,
a
superbk
world
if
I
used
only
external,
it's
syntax,
extregar
to
extern
C
and
I
I.
A
If
I
put
the
next
envelope,
I
could
Define
intuit
function
without
body,
and
the
mangle
is
a
thing
that
I
need
to
do.
Link
linking
in
fact,
because
it's
so
things
that
preserve
symbol
is
there
it's
a
real
thing,
and
the
thing
is
I
should
not
at
all
do
that,
because
I
have
an
issue
which
is
everything
work
and
everything
works,
because
I
I
I
akin
to
to
mixing
works
and
I
finally
find
a
way
and
everything
work.
A
I
have
no
warranty
of
what
is
this
or
it
will
I
don't
know,
and
so
I
should
not
use
the
rest
on
convention.
I
should
use
the
C1,
which
is
why
that's
the
default
behavior
of
the
external
keyword,
because
this
one
is
specified
and
try
to
make
the
differences,
because
between
things
that
are
specified
internally
and
specified
publicly,
because
first
category
is
a
knack
and
the
second
one
you
can
build
stuff
on
top
of
it
without
fears
that
will
break
at
any
moment.
A
A
lot
of
things
in
rest
are
not
specified
publicly
the
early
format,
the
default
format
where
all
the
library
are
easily
built,
not
like
the
the
thing
we
did
that
aren't
specified
all
the
intermediate
languages
are
unspecified,
so
either
you
generate
less
code
that
will
still
compile
it.
You
know
it
either.
You
generate
something
really
low
level
like
llvm,
but
ashiramir.
This
is
a
higher
the
Intermediate
Language
or
not.
A
lot
of
things
are
on
specifying
rust
default
memory
layout
for
stroke
different.
So
you
you
should
not
rely
on
it.
A
So
the
only
things
you
could
rely
on
it.
If
it
works,
sorry
I
lose
the
focus
on
my
terminal.
It's
a
crbi
because
the
CBI
have
a
lot
of
Quirk,
but
at
least
it's
stable
I
mean
if
I
bring
something
relying
on
cibi,
it
will
still
work
because
it
it
will
not
change
and
that's
really
a
great
feature
of
what
we
we
do
here
and
I
have
another
example.
Quick
example
I
think
with
python.
So
here
I
show
you
how
I
should
write
my
previous
code.
A
The
less
cut
possible,
because
it's
really
easy
to
have
seems
like
I,
think
it's
safe,
rapid
into
an
unsafe
block,
but
in
fact,
which
is
unsafe
and
there's
a
good
practice
for
unsafe
blockage
to
make
it
the
smallest
possible
always
and
because
rest
everything
is
an
expression.
It's
easy
to
do
that,
so
unsafe
should
be
used
in
a
way
where
there's
a
few
gun
retention
and
I
have
main
python
files.
That's
not
my
library
and
I
think
that's
work
that
should
work.
A
If
I
cargo
build
my
thing
yeah,
it's
already
built
that
anyway
and
no
yeah
everything
works,
so
I
logged
python
code
into
Rest
by
using
C
string
call
convention,
so
everything
cool
and
I'm
I'm
really
happy
with
that
and
now
for
the
safe
part.
No,
that's
it's
really
hard
to
write
ffi
by
end
and
when
you
do
it,
usually
you
you
fail
it
because
you're
in
a
space
between
two
run
time,
whereas
there
is
no
type
checking
and
no
mechanism
to
check
that's
what
you
did.
A
Work
just
function
pointer
at
the
end.
So
if
you
forget
an
argument,
if
you
forget
a
field
in
a
script,
if
you,
if
you
interface,
don't
exactly
match,
you
will
not
know
it
at
compile
time.
Most
of
the
time
you
will
know
it
at
the
worst
time
at
runtime,
so
you
always
prefer
to
do
binding
generation,
and
there
is
a
lot
of
solution
for
that.
You
can
generate
binding
from
a
C
file,
a
needle
file
to
rest
as
all
the
credits.
That's
our
suffixes.
A
When
you
install
Google
research
by
engine,
there
is
life
coding,
video
by
John,
Johnson
I,
don't
know.
What's
this
name
is
pronounced
the
rotor
of
resveration
on
YouTube,
which
is
pretty
cool
where
it
gender
binding
for
lip,
sodium,
I
I.
Think
there's
a
lot
of
stuff
to
embed
rest
into
other
language,
sir,
wasn't
backwards
and
bindings.
A
There
is
in
Python
so
say
by
Gen
4
C,
and
there
is
a
little
thing
I
did
for
askal,
which
is
the
point
of
this
talk
to
to
advertise
little
things
that
he
did
and
there
is
really
cool
things
that
do
both
sets
offer
binding
in
both
sides
and
six,
six
great
by
David,
Turner's.
Really
cool
answer
is
no
and
recent
initiative
in
okamel
with
occaman
interrupt
we've
got
a
lot
of
funding.
We
got
funding,
I,
don't
know
if
it's
a
lot
of
that.
B
A
Is
I
have
a
demo
a
scale
yeah
where
I
have
two
things:
don't
care
about
the
next
file,
but
I
have
greetings
and
test
folder
and
a
cabal
project.
Cabal
project
is
just
a
cargo
workspacing.
Where
say:
I
have
two
package
and
at
the
end
I
want
to
do
a
cabal
run
test.
I
I
will
fail
to
do
it
right
now
and
the
greetings
is
my
my
really
useful
Rest
Library
I
already
write
three
times
where
you
can
see
the
code.
It's
here
and
now
I
use
this
little
yeah.
A
It
failed
because
it's
I
don't
know
why
I
don't
care.
Rest.
Analyzer
I
have
this
little
Port
macro
decorator
on
my
function,
so
my
function,
look
like
a
rest
function
and
I'm
really
happy
with
that.
But
what
happened
is
if
I
do
cargo
expand,
which
is
a
really
cool
tool
by
David
turnney
again
yeah
I
can
see.
My
macro
is
expand
to
some
wrapper
of
my
functions.
A
That
does
the
really
dirty
things
of
wrapping
my
team
into
C
type,
and
this
macro
does
another
cool
thing:
oh
yeah,
sorry,
which
is
if
I
can
go
build.
It
also
generate
yeah.
Sorry,
there's
a
binding,
so
SQL
binding
yeah
here,
which
is
I,
have
the
right
type
and
everything
which
is
a
scale
C
type
is
not
perfectly
ergonomic
right
now,
and
so
so
now,
if
I,
just
those
cabal
run
test
yeah
cheating,
it
will
I.
A
Also
yeah
does
Full
Compilation
and
of
everything
and
at
the
end,
work
and
I
have
a
rest
dependency
into
an
SQL
project.
I,
don't
don't
feel
like
I
have
a
rest
dependency
and
that's
work,
because
I
have
already
the
cabal
file
notice.
It
a
bit
earlier
here
generated
how
you
don't
you
don't
see
it
when
I
I
have
already
the
cable
file
generated
and
that's
because
I
have
a
little
handy
tool.
So
those
mine
is
a
generation
of
the
of
the
project.
A
Those
file
unionism
project
and
so
I
think
I
talk
a
lot,
and
that
was
the
end
of
what
I
want
to
show
you,
and
there
is
a
little
Report
with
what
I
do
and
that's
really
early
prototype
and
I
rewrite
it
entirely
in
the
train.
Coming
to
here,
because
you
know
writing
procedural
macro
is
really
painful
because
you
have
to
work
on
the
a
rest
is
still
directly
so
it's
a
thing
you
have
between
the
end
is
not
really
rusty.
A
It's
token
and
so
I
wonder
how
if,
for
example,
you
Alias,
you
create
your
own
string
type,
my
proc
macro.
We
don't
know
that
your
own
string
type
and
will
say:
okay,
it's
look
like
a
string
and
so
I
change
it
in
a
way
where
he
reuse
trade
to
actually
see
if
it's
a
type.
Where
else
there
is
an
implementation,
where
I
could
do
the
second
generation
with
it,
which
is
I,
think
less
dirty
and
and
that's
it
and
I
can
talk
about
everything
later
and
last
things
you
know.
A
The
rest
example
I
forget
to
say
that
the
rest
example
where
there
is
a
rest
code
that
include
the
rest
code
with
Dynamic
Library,
which
is
using
the
rest
convention,
which
is
bad
this
code,
if
you
try
to
include
it
with
static
Library
will
not
work
and
I
know
if
you
know
why,
but
I
could
give
answer
later,
it
will
not
compile
them.
For
any
reason,
yeah,
and
thank
you
very
much
for
for
your
attention.
C
Hi
thanks
for
the
talk,
it's
actually
very
interesting
to
see
a
bit
of
ffi
I
I
know
how
it
works
more
or
less
I
never
use
it
myself.
So
my
question
is:
if
you
you,
let's
say
if
you
use
ffi
to
let
two
rust
processes
communicate
with
each
other.
Have
you
noticed
any
performance
hit
in
in
that,
like
in
you
know,
using
a
common
C
ABI
to
communicate
data
between
the
two
processes
or
have
you
noticed
any
kind
of
performance
degradation.
A
I
think
there's
two
unstruct
to
this
question,
which
is
always
the
rhetoric
theoretical
one
and
the
real
life
one
and
the
second
one
I
think
it's
Benchmark
is
the
only
trustable
things
for
performance
measurement,
but
in
the
conceptual
way
of
seeing
it
casting
to
C
type
is
always
a
bit
costly
because
it's
typecasting.
So
there
is
a
few
operation
involving
into
it
and
also
static.
Library
is
against
the
one
big
binary.
So
you
don't
really
realize
that
you
call
a
function
from
outside,
but
Dynamic
Library.
A
It's
really
like
you're
loading
and
another
executable
that
you
will
be
able
to
do
a
curling
to
it
later.
So
that's
a
bit
of
extra
runtime
cost
uploading,
but
I
think
it's
mostly
it's
it's.
It's
not
a
lot
of
cost.
Comparing
a
lot
of
other
interoperability
solution.
Web
series,
a
big
communication,
runtime
cost,
so
I,
don't
know
if
it's
answerable
question.
B
B
A
Yeah
the
thing
is,
the
thing
is:
when
you
write
a
program,
can
I?
Okay?
No,
it's
complicated.
When
you
write
about
macro,
you
basically
operate
on
top
of
an
AST,
so
it's
just
a
bunch
of
tokens.
So
it's
basically
a
fancy
constraint,
which
is
not
a
string,
but
it's
really
close
to
a
string
which
contain
Your
Word
program.
So
it's
like
it's
rest,
but
it's
not
interpreted
as
rest.
You,
you
have
token.
You
have
chunk
of
string
typed
like
parsing
those,
but
not
like
a
these,
have
no
semantic
meanings.
A
A
It's
a
string,
you
you
don't
have
the
meaning
of.
What's
the
type
is
so
you
prefer
to
not
match
on
token
because
matching
and
took
it
is
just
matching
on
a
string
which
is
Aki,
for
example,
if
I,
if
I
have
a
custom
defined,
type
and
I
prefer
to
Define
traits
and
trade,
just
say
if
a
type
implemented
this
trade
I
know,
what's
the
Primitive
to
cast
it
to
something
which
is
a
good
C
type
and
I
I
get
the
information
of
what
would
be
the
generated
SQL
bindings
on
the
other
side.
A
So
that's
the
strategy,
but
the
strategy
I
want
to
explore
right
now
is
the
object
introspection,
because
this
problem
is
well
known
about
non-community
and
there
is
an
implementation
in
Haskell.
That's
pretty
cool
such
would.
Allow
me
to
have
more
complex
type,
and
that's
my
guess,
any
the
object
introspection
is
just
you
have
like
a
magic
metadata.
You
put
site
to
your
type,
so
you
can
say
it
looks
like
that.
The
memory
I
run,
so
you
you,
you
have
a
way
to
to
know.