►
Description
En el sótano de nuestras compus vive mucho software que se escribió en los 1980s y 90s, con prácticas de ese entonces. Pero la cosa ya cambió. ¿Cómo podemos arreglarlo con Rust?
https://rustfest.global/session/59-podemos-tener-cosas-bonitas
English: https://www.youtube.com/watch?v=CYeg8dB_68o
A
A
Quintero
He
is
one
of
the
founders
of
the
Chinese
project,,
which
is
a
graphical
environment,
widely
used
in
free
operating
systems.
Before
filling,.
He
was
in
charge
of
the
__
]
project,,
which
is
convenient,.
It
is
a
free
software
project
for
some
time,
and
in
the
early
days
of
Jinán,,
he
was
responsible
for
part
from
the
original
documentation
code
of
the
libraries
of
the
graphical
environment,
games
and
also
applications,.
A
He
was
working
on
the
network,
in
advance
of
seeing
the
messages
in
the
first
versions
of
the
desktop,
and
after
working
on
the
evolution,
Federico
specialized
in
the
core
of
the
desktop,,
the
gtk
libraries,
platform.
Libraries
at
the
end
and
the
native
file
manager
today
is
working
on
its
being
in
the
foothills
in
schools.
In
the
distributions
open,
sos
and
suse
linux
enterprise
text
and
from
there
it
also
maintains
sbg
library
and
other
libraries,
so
federico
buena
I
think
he
is
an
expert
on
the
world
of
free
software,,
very
happy,.
A
B
B
B
This
photo
is
from
a
part
of
the
center
of
mexico
city,
also
a
very
old
city
with
a
lot
of
history
and
well,
we
take
the
holes
on
the
left.
Side
is
the
church
of
san
bernardo,
which
is
a
building
from
the
17th
century,.
Six
hundred
and
something
and
to
the
right
is
a
department
store
called
the
iron
palace
and
it's
a
building
from
the
early
20th
century.
So
I
don't
know
if
it's
art
or
something
like
that,
but
hey
both
buildings
are
old
infrastructure
that
the
city
continues
to
be
used.
A
B
Them
they
did
not
simply
adapt
little
by
little
to
put
things
like
that
with
the
fundamental
things
I
needed:
electricity,
drinking
water,,
drainage,
etc.,
and
the
software,
or
something
similar
happens,.
Although
it
is
difficult
to
change
the
old
software
due
to
all
the
inertia
it
has,
but
well,,
those
facades
of
the
beautiful
buildings
of
the
departmental
church
that
we
see-
and
that
is
what
that
we
use
when
we
interact
with
what
is
in
those
buildings.
B
B
I
work
in
the
part
that
paints
the
windows
on
the
screen,
paints
the
buttons
and
all.
the
engine
that
paints
the
text
of
everything
that
is
displayed
on
the
screen,.
Everything
is
infrastructure,
because
the
only
thing
we
see
is
not
seen
in
the
pixels
that
paint
in
the
audio
that
is
output
from
the
speakers,.
B
But
all
this
is
essential,.
Someone
has
to
develop
this
and
This
talk
is
my
little
way
of
saying,
come
and
realize
that
we
are
here,
and
you
are
welcome
and
welcome
to
help
us
all.
This
part
of
the
infrastructure
has
been
called
systems
programming
and
that
it
is
a
kind
of
grandiloquent
way,
well,,
all
the
infrastructure
of
the
The
system
that
you
run
with
the
one
that
you
interact,
with,,
which
is
system
programming,,
exactly
what
is
close
to
the
operating
kernel.
B
It
is
in
charge
of
sharing
the
hardware
among
the
rest
of
the
software,,
and
let's
say
that
system
programming
is
not
used
by
the
entire
initialization
system.
When
you
learn
how
to
block
activates
network
connection
to
hcp
requests
to
set
ip
address
to
your
computer.
All
services
like
bus,
ssh,
all
ls
command
line
utilities
can
find
les
more
all
are
the
fundamental
libraries,
the
crypto
libraries,
the
graphic
tourists
to
paint
little
buttons
on.
B
B
But
well,
all
of
us
is
written,
not
what
because
we
would
have
to
worry
about
the
programs.
Well,
everything
has
changed
a
lot
in
the
last
20
years
since
the
triple
part
I
am
going
to
talk
to
you
and
I
know.
It
can
improve
a
lot
because
programming
practices
have
also
changed
a
lot
in
the
last
few
cleanings.
B
We
are
going
to
see
a
summary
of
the
last
forty-fifty
years
of
software,
and
well,.
What
interests
us
here
is
when
iunics
started
in
the
seventies,,
not
those
shaggy
up
there,.
They
are
this
one.
Let's
go
to
dennis
ritchie.
They
are
one
of
the
authors
of
the
unics
dennis
ritchie
creator
of
the
c
language
and
well
they
are
legends
who
already
already
did
what
they
had
to
do.
I
knicks
start
it
in
pvp
7
machines.
B
There
is
a
photo
of
a
spinning
top
that
were
very
machines,
large,
very
old,
nutritious,
and
although
they
are
the
size,
it
does
not
reflect
a
refrigerator.
They
are
very
slow
machines.
It
is
not
with
very
little
capacity
this
a
few
kilobytes
of
bone
kb
memory
with
rihanna
less
than
a
mega
hertz
of
speed.
There
were
no
microprocessors,
everything
is
built
from
circuits,
fundamental
and
big.
You
could
this
solder
by
hand
all
this?
There
was
no
internet.
B
There
was
really
no
need
to
worry
about
security,
not
back
then,
and
you
would
feed
garbage
to
a
program
or
a
file
with
an
incorrect
format,
and
the
program
would
create
possession
well,
just
It
is
recorded
if
you
do
not
have
recorded.
It
is
not
acceptable
for
your
program
to
crash
because
you
do
not
put
garbage
in
the
eighties
home
micro.
Computers
began
to
become
popular.
A
B
B
Companies
like
candles
like
the
telephone
and
even
in
home
computing
environments
or
the
companies,
this
obvious
to
assume
that
the
computers
were
not
on
the
network
and
liked
by
the
people
there
and
they
had
better,
be
reliable.
There
was
no,
there
was
no
electronic
espionage
or
things
and
by
network
personnel
there
was
no
way
to
easily
transfer
data
to.
A
B
Way,
the
only
way
to
transfer
data
in
the
field
was
with
one
of
their
big
ones.
There
were
360
kilobytes,
so
you
couldn't
extract
much
information
in
the
80s
and
90s.
This
is
what
iunics
looked
like.
This
is
an
environment
of
the
x
windows,
environment,
the
x
11
protocol
and
well
this
all
looked
horrible.
B
No,
no!
All
this
was
software
made
by
programmers
for
programmers.
We
didn't
have
the
slightest
sense
of
graphic
design
and
well.
The
technical
limitations
were
also
very
important.
No,
if
you
were
lucky,
your
machine
could
display
16,
simultaneous
colors
low
resolution
on
the
drivers.
Everything
was
onion
and
old.
B
But
hey
They
didn't
do
much
damage
and
at
that
time
I
followed
the
philosophy
of
garbage
inter
buyout
a
bit,.
It's
simply
a
corrupt
file
or
garbage
to
a
program
in
figures,
you're
done
if
it's
good,
it
crashed,
I
restarted
it
and
it's
not
in
the
nineties
anymore.
When
this
linux
starts
in
91
and
it's
huge
and
it's
in
96
and
it's
published
in
97.
B
B
B
Is
a
screenshot
of
a
little
later,?
We
already
have
more
resolution
available,,
so
more
interesting
screens
can
be
made.
We
already
have
here
on
the
left
running
the
nautilus
file
manager
that
is
still
alive
today.
That
which
is
on
the
right
red
carpet
no
longer
exists
in
the
system,
the
installation
of
the
software
and
the
spreadsheet
that
is
down.
There
seems
to
me
to
be
a
little
number
and
they
are
already
very
little.
It
was
one
of
the
spreadsheets
that
you
see
available
for
what
name,
but
hey
we
are
in
2020.
B
It
is
all
the
way
train
or
supercomputer
in
the
pocket.
Most
of
the
personal
machines
are
single
user.
It
is
very
rare
that
you
share
one
computers
with
other
people
or
nobody
bothers
people
who
use
camps,
use
windows
at
home
and
the
rich
make
marks
this
very
few.
People
configure
them
as
multi-user
and
computers
are
highly
shared
in
data
centers.
There
is
no
if
they
are
plagued
with
virtual
machines
and
containers.
So
many
resources
are
shared.
B
B
Which
is
different
from
the
70s,,
not
in
the
70s,,
the
kernel
and
the
system
and
all
the
players
in
the
system
were
written
in.
If
you
had
a
cpu
less
than
ATMs
less
than
1
mb
ram,
everyone
in
your
office
was
reliable
with
their
ace
comps.
They
become
difficult
to
use
scratch
recording
in
2022
the
kernel
and
the
later
of
the
system
are
still
written
itself,
and
it
is
the
only
thing
that
it
has
changed
me
because
your
phone
is
good.
B
My
phone
is
6
correct
because
it
is
old,
modern
phones
and
our
colors
and
8
gigabytes
of
ram.
What
is
more,
memory
than
a
supercomputer
from
the
80s
had
the
gpu
of
my
daughter
laptop
is
faster
than
a
reality.
Engine
say
with
graphics
from
1998.
The
machines
cost
thousands
of
dollars
back.
Then
no,
your
computer
has
basically
infinite
storage
capacity
except
right.
Now
it's
hard
to
find
a
hard
drive
of
less
than
one
terabytes.
B
The
whole
internet
is
hostile,
everyone
wants
computers
and
telephones
are
very
stable
and
carbayín
arrives,
well,
you
better
be
safe
because
it
is
a
malware
or
it
is
a
government
exploit
if
you
are
a
reporter
people
who
are
dedicated
to
human
rights,
pretern
and
systems
continue
to
be
wanted
because
It
hasn't
changed
to
that
and
they
are
already
the
beautiful
things
that
I
wanted
to
talk
to
you,
about.
Well,
many
people
showed
only
python
and
not
javascript,
and
only
you
would
say
these
very
beautiful
languages,
with
very
beautiful
tools,.
B
And
buying
the
one
with
a
note
and
the
ior
of
the
old
ones,
with
the
traditional
decree.
This
makes
it
serious
when
it
accepts
your
code.
It
enters
the
entire
directory,
punto
hits
and
it's
kind
of
awkward,
no,.
That's
why
the
people
who
used
them,
knowing
it,,
have
delayed
with
theories
like
heretic
king,,
it's
written
on
his
face
that
he's
looking
for
a
throne,
source
code
tree,,
it's
possible
that
there's
a
git
dot
over
there
that
shouldn't
be
getting
in
there,
because
that
doesn't
display
anything
useful
no,.
A
B
And
as
it
says,
to
use
ame
and
down
there,
We
already
think
that
the
ugly
code
is
because
the
programmers
wrote
it
badly,
but
not
because
they
had
limitations
or
circumstances
very
different
from
the
ones
we
are
with
now,.
It
will
tell
us
a
horror
story
from
when
we
were
writing
evolution
around
the
year.
2000
evolve
the
software
to
read,
but
a
microsoft
outlook
auto
clone.
We
didn't
want
to
write
an
integrated
software
for
and
declare
it.
B
Mail
have
calendars
and
have
is
cool
with
a
list
of
contacts
just
like
another,
the
subtle
and
individual
days
to
write
those
started
from
98
a
little
after
we
started
when
I
named
it,
but
they
were
rewritten
in
2000
to
build
a
version.
Look
and
well.
This
function
that
comes
out
and
written
in
that
is
one
of
my
first
patches
for
evolution
is
totally
wrong
because,
since
I'm
creating
a
buffer,
it
should
be
and
then
returned
a
pointer
to
that
buffer
on
the
stack.
B
That's
automatically
memory,
corruption,
don't
be
this
bug,
they
fixed
it
two
committees
later,
but
you
had
a
language
that
didn't
prevent
you
from
doing
that
kind
of
wrong
thing.
You
didn't
have
and
all
the
time
all
the
time
you
have
to
be
alert
so
that
this
kind
of
thing
doesn't
happen
to
you.
We
didn't
have
an
automatic
compilation
system.
The
computers
were
slow,
so
nobody
thought
of
using
them.
B
They
are
compiling
everything
all
the
time
to
see
if
they
actually
worked
and
each
programmer
is
responsible
for
installing
all
the
development
utilities,
all
the
libraries
of
the
dependencies
in
their
field
to
be
able
to
compile
the
software
and
that's
why
we
wasted
a
lot
of
time.
No,
there
weren't
any
automatic
dependency
installation
systems
yet
or
anything
like
that,.
B
A
B
It's
a
horrible
thing
that
almost
no
one
uses
anymore
except
openbsd
and
gcc.
Just
a
couple
of
years
ago,
I
switched
directly
from
cbs
to
aus
kitz
and
did
the
cbs
conversion
git
for
the
compiler
that
there
is
no
such
thing
as
an
odyssey.
No
in
come
or
less.
We
switched
to
using
sbn
subversion
for
the
one
of
the
two
thousand
and
you
started
using
it
until
much
later.
B
The
bug
monitoring
system
that
we
know
how
to
train
myself,
we
put
it
I-
do
n't
know
in
98
99
it
was
a
mozilla
visionada
box
thing
and
the
one
that
is
an
old
system
for
monitoring
you
not
at
least
it
released
the
source
code
of
mozilla
of
minds
that
we
threw
in
98.
They
also
released
their
monitors
from
box
press
box
and
they
released
it.
An
automatic
compilation
system
triggered
interbox.
B
He
wrote
dará
hernández
inside
mozilla,
but
hernández
basically
invented
the
concept
of
continuous
integration
for
continuous
compilation,
because
the
problem
they
had
in
skype
was
they
had
to
support
windows,
16
bits,
windows,
32
bits,
sorry,
windows
and
windows.
16
bit
windows
bits
the
old
framework
before
they
received
it
as
mac
os
x
and
eight
versions
of
joe
knicks
8
different
unix
systems,
not
back,
then
there
were
still
solaris
x,
php
x,
linux,
all
those
no
and
they
said
no
well.
B
We
have
to
keep
the
code
in
the
compiler
on
all
these
platforms,
because
we
are
going
to
write
something
automated
and
that
was
timbre
box,
a
verb
that
we
tried
to
install
for
renown
and
for
symbian
in
evolution,
and
we
could
not
get
it
to
work
acceptably.
It
did
not
require
many
computers
compiling
all
the
time
we
did
not
have
money
to
install
servers
that
we
were
compiling
compiling
product
of
the
day.
We
did
not
have
a
suite
or
a
framework
to
do
automated
tests.
B
The
legal
code
of
evolution
does
not
have
tests
the
old
code
that
we
did
not
have
tests
because
they
had
a
framework
to
write
them.
No,.
It's
not
like
a
big
voice
that
we
put
kitten
test
on
it
and
well,.
The
buyer
is
already
a
burden
to
execute
on
his
own.
Those
are
those
functions,
like
destructive,
tests.
B
It's,
the
Hellip
framework
to
do
unit
tests,,
but
that
appeared
until
2007,
I
mean,
we
spent
ten
years
without
to
have
a
way
like
they
are
to
rewrite
tests
and
at
the
beginning
of
the
21st
century
it
was
very
primitive.
It
appeared
in
2005
in
called
we
started
using
it
until
2008.
It
was
a
big
battle
to
convince
all
the
people
to
switch
from
using
their
version
to
kit,
because
people
from
ubuntu
and
from
canonical
that
we
started
to
pass
but
well
to
them
to
pass.
B
B
We
spent
21
years
without
having
an
automatic
configuration
system
integrated
with
our
source
code.
Not
the
linux
containers
started
in
2015,
basically
the
inventors
and
for
6
when
I
was
working
everywhere
and
it
took
a
year
for
us
to
have
containers
that
you
didn't
need
to
be
road
to
run
and
before
that
installing
environments
automatically
was
very
difficult.
B
So
they
will
create
reproducible
winds.
They
will
develop
very,
very
difficult
because
well,
the
typical
state
of
a
project
is
then
it
was
that
they
did
not
have
automatic
tests
because
there
was
no
france.
It
did
not
have
continuous
integration
because
there
was
no
continuous
compilation
system.
I
did
not
have
reproducible
environments
because
no
containers.
B
And
well,
I
am
the
company
in
charge
of
releasing
that
origin,
which
is
the
library
the
system
that
would
break
the
unknowns
with
a
vector
format
is
heretic
and
it
would
yield
pixels
so
still
against
the
automatic
testing
version.
The
recommendation
fights
not
for
request
containers
no
well
and
well
little
by
little.
It
has
been
fixed
to
those.
No,
we
already
have
the
screaming
user
interface
horrible,
but
it
is
a
very
reliable,
better
code
system,
but
there
are
a
thousand
tools
to
make
it
prettier.
B
B
We
already
have
frameworks
to
do
unit
tests
and
tests
automatic
in
any
language,,
which
makes
it
easier
to
evaluate
people's
patches
because
if
they
break
cross
tests
that
fixes
it
by
shining
the
eye,,
your
patch
is
redone
and
in
continuous
compilation
we
already
have.
The
hardware
is
fast
enough
to
be
compiling
the
software
all
the
time.
We
already
have
an
exercise
to
do
more
and
quest
for
taxes
in
a
friendly
way
of
saving
half
the
block.
The
development
discussion
makes
it
easier
for
people
to
send
their
patches
to
a
centralized
place.
B
We
already
have
virtual
machines
and
containers
the
2.
We
can
create
reproducible
environments
this
and
for
the
first
time
we
have
a
low
level
language
that
can
be
integrated
with
six
more
more
and
they
have
all
this
nice
automated
testing,
this
memory,
security
e-
and
this
has
resulted
in
the
spirit
of
rewrites.
It
enfaced
check
out
this
blog
Then
I,
show
you
my
presentation
so
that
you
can
see
the
links
are
rewriting
all
the
correctives
with
the
basic
theories
in
the
node
of
the
command
line,
no
katz
ep.
They
are
soft
touch.
A
B
We
are
writing
all
of
this
in
face.
It
is
not
absolutely
necessary
to
rewrite
the
face
because
that's
it,
but
if
we
want
to
move
little
by
little
out
of
the
scheme
that
everything
is
written
in
a
language
without
web
insurance
to
the
best,
it
is
important
not
in
hotels.
Very
pretty
little
boy
offers
use
of
clean
space
that
analyzes
a
whole
challenge
in
the
history
of
development,
from
a
youtube
repository,
and
it
makes
you
graphs
like
this,.
B
Each
color
in
the
graph
is
the
code
that
was
added
in
a
certain
year,
and
if
you
see
that
code
there,,
if
they
already
received
it,,
what
happens
in
a
typical
project
is
that
they
add
girls,
add
code
and
little
by
little.
It
stays
here.
No,
and
but
this
is
what
happened
with
investments
already
from
the
project
that
we
ported
from
that
rice
completely,
not
there
in
2016,
we
began
to
rewrite
it
redraw
it,
and
you
can
see
that
the
color
bands
of
the
left
they
get
very
small
to
the
right.
They
almost
disappear.
B
And
this
is
a
graph
of
0%.
You
are
working,
100
is
up
and
the
percentage
of
lines
of
code
that
had
each
author.
We
are
seeing
how
how
the
people
who
contributed
to
the
book
change
resurfaced
years
ago
before
2006.
They
no
longer
do
so.
Moyano
contributing
is
good
their
how
to
rewrite
the
code.
Their
contributions
sounds
reducing
to
zero.
B
The
contributions
of
new
people
who
came
to
destroy
by
the
red
is
reflected
on
the
right
then,
and
we
can
also
have
a
history
of
who
has
been
putting
code
and
contributions.
We
have
already
learned
in
the
last
20
years.
Well,
it
is
no
longer
acceptable
to
say,
but
it
works
on
my
computer.
You
don't
need
a
reproducible
tone
where
to
compile
and
run
your
tests,
you
need
to
understand
code
coverage
to
know
which
parts
don't
don't
have
tests
that
discuss
us.
This
is
complete
without
automated,
etc,
etc,
etc.
B
And
what
about
continuous
integration?
It's
been
really
hard
to
integrate
this
into
different
parts
of
which
I
don't
know
why
I
don't
until
a
few
years
ago,
we
had
more
than
two
or
is
money
to
write
and
applications
that
live
in
containers
are
distributed
in
little
packages
that
can
be
installed
without
affecting
the
rest
of
the
system
and
all
continuous
integration
compilation
is
now
done
through
'
flashbacks'.
B
B
And
why?
Why
is
that?
Because?
Well,
let's
see,
we
have
a
64-bit
input
which
is
8
bytes
and
2
joules
of
one
byte
each
with
should
be
10
bytes,
but
the
structure
measures
24.
That
is
because
each
field
in
se
has
to
be
aligned
according
to
its
data
type,
not
the
joules
of
a
so
that
they
can
be
in
any
valley
in
memory,
but
64
bit
integers
have
to
be
aligned,
64
bits
to
8
bits,
so
after
the
first,
william
or
after
7
bytes
of
unused
whitespace
already
then
comes
the
8
bit
field
b.
B
Immediately
after
there
is
the
field
to
be,
and
after
being,
there
are
another
seven
bytes
to
be
able
to
make
the
size
turtle
structuring
a
multiple
of
8,
which
is
the
size
of
its
largest
field,
no
ros
and
water.
If
we
paint
the
dean
memory
addresses
of
these
fields,
we
can
see
it.
So
the
field
is
at
address
0,
they
are
multiple
98.
The
next
field
is
ver
is
another
multiple
of
8.
The
next
field
is
ours.
B
B
If
we
want
to
cut
this
function,
paint
want
face,
we
have
to
declare
an
identical
structure
in
roses.
With
the
re
coming
import,
this
function,
let's
see
how
our
structure
is
done
in
our
claw,
define
the
function
and
let
the
code
continue
calling
it
in
the
same
way
that
we
are
going
to
see
each
other.
B
B
B
Convert
it
from
pointer
to
a
reference
of
roses
using
a
little
piece
of
a
6
and
below
we
call
slow
front,
is
the
same
as
our
function
did
in
instead
of
using
amos
projects
and
painting
the
fields
and
then
going
back
to
our
code
in
ce,
we
remove
the
definition
of
the
function
and
put
an
external
declaration.
That
means
that,
with
that,
we
tell
the
compiler
that
this
function
is
no
longer
defined
there.
It
is
defined
outside.
Then
we
are.
A
B
B
B
We
link
the
code
and
it
works,
and
the
strategy
is
the
strategy
we
follow
in
liberation
axis
is
exactly
that:
porting
function
by
function
of
that
rice
and
replacing
at
each
point
to
see
that
the
code
continues
to
work,
and
since
it
is
the
short
of
a
couple
of
functions,
you
can
start
to
update
and
make
your
code
in
rosh
more
beautiful,
because
if
we
see
the
order
that
we
had
here,
then
a
bit
ugly.
This
is
usually
in
rose.
We
do
not
want
that.
B
They
send
us
a
product
or
before
we
want
them
to
send
us
references.
So
we
begin
to
update
this
code
so
that
it
takes
a
reference
instead
of
a
pointer
and
well.
We
authorize
this
duplicate
code
of
isola
point.
There
is
a
point
ce
to
call
another
appointment
function
that
is
done
little
by
little
and
walls
of
collecting
a
library
of
30,000
and
lines
of
code.
B
I
am
going
to
do
a
little
before
the
justification.
We
see
here
that
about
30
mine
code
itself,
without
problems
and
when
we
started
to
contribute
rock,
the
number
of
codes
began
to
rise,
remarkably
until
that
it
almost
doubled
and
the
reason
why
the
number
of
lines
of
code
almost
doubled,
all
the
extra
code
are
tests.
No,
this
almost
all
the
functions
test
has
a
question
with
a
little
plate
perez
in
pink,
so
well.
The
number
of
4
grows,
I,
say
but
It's
a
much
more
reliable,
code,
no,.
B
B
We
forced
Santo
Domingo,
and
we
arrived
at
the
mountain
and
beautiful
and
well,.
That's
how
it
is,
we
behave
with
a
little
as
I
say,
you
want
a
face.
It
seems
to
me
that
time
is
up,,
so
well,
I
want
to
thank
you
for
coming
and
I
hope
that
this
It
inspires
a
little
to
continue
maintaining
the
old
infrastructure
that
we
had,,
but
modernizing
it,.
You
don't
have
to
put
everything
on
it,
tests,
automatic
compilation,
reproducible,
environments,,
porting
them
from
insecure
languages,
to
safe
languages.
B
A
Thank
you
very
much
Federico.
You
made
us
remember
too
many
things
through
the
entire
history
of
the
code
and
well.
Unfortunately,
we
are
a
little
bit
over
time.
If.
You
have
any
questions
for
Federico,.
Remember
that
you
can
be
in
the
event
chat
or
you
can
also
count
it,
as
at
Federico,
Mena,
I
feel
on
twitter,
there.
You
can
also
send
your
questions
and
thank
you
very
much
for
taking
the
time
and
giving
this
great
talk,
so
right
now,
let's
continue
now
with
ramón.
It
seems
to
me
and
pilar
in
the
other.