►
From YouTube: JavaScript Will Let Your Site Work Without JavaScript - Sarah Saltrick Meyer, Rent the Runway
Description
JavaScript Will Let Your Site Work Without JavaScript - Sarah Saltrick Meyer, Rent the Runway
What does your site look like without JavaScript turned off? Are your users waiting for all your JavaScript to be delivered and rendered before they see anything interesting on your pages? Is your site heavy and slow, especially on mobile devices? Isomorphic JavaScript with Node can help. No matter what server-side language you currently use, you can render your HTML with JavaScript on the server before sending it down to your client. We will discuss how to seamlessly build serverside-rendered content into stacks using popular frameworks like React and Ember and the performance, stability, and UX benefits that come with it.
A
Okay,
hi
everyone-
and
I
guess
welcome
to
this
talk.
Basically,
this
is
a
kind
of
a
counterintuitive
talk
to
give
to
a
group
of
web
developers
we're
here
to
talk
about
node.js,
which
is
obviously
javascript
and
most
of
us
in
our
day-to-day
lives.
One
of
the
biggest
tools
that
we
have
is
javascript
as
a
web
developer.
But
today,
I'm
here
to
ask
you
what
happens
to
your
site
when
you
turn
the
javascript
off.
Have
you
guys
ever
done
this?
Let's
do
it
it's
fun!
A
A
A
A
A
A
No
all
right,
so
it
for
the
the
formatting
of
that
original
destination.
Right
javascript
is
required,
probably
to
enter
a
proper
input
value:
okay,
one
more
brave,
brave
soul.
Two,
yes
back
there
fusionpassenger.com,
okay,
okay,
ph,
instead
of
f
all
right,
so
the
names
of
our
companies
are
just
as
hard
here
as
anything
else.
Okay,
good.
To
know
that
google
works
fine
without
javascript
nice.
I
have
a.
I
have
a
sense
that
I
might
be
missing
something
here,
but
it's
a
it's
a
nice
looking
website.
A
A
There
are
some
very
large
sort
of
american
companies
that
have
this
problem
where
their
sites
don't
work
without
javascript
at
all,
squarespace
right,
none
of
their
client
sites
work
without
javascript
in
the
least.
So
why
is
this
bad
like
that
stuff
that
I
just
did
about
turning
off
the
javascript?
Whoever
is
going
to
do
that?
Well,
let
me
tell
you
why
I
found
it
very
useful
in
my
life
as
a
professional
developer,
to
turn
the
javascript
off.
So
I
oh
star,
wars
is
also
the
theme
of
this
talk.
A
A
A
So
there's
a
there's,
an
interesting
technological
gap.
There
that's
happening
and
the
message,
though,
of
star
wars,
is
very
powerful.
I
would
say
that
that
message
is
always
that
you
have
some
sort
of
power.
You
have
some
sort
of
influence
in
the
world
and
you
should
use
those
powers
for
good
instead
of
for
evil,
and
you
guys
as
web
developers,
you
do
have
power
and
you
can
choose
to
use
that
power
for
good
rather
than
for
evil.
A
That
was
one
of
the
first
things
that
smartphones
started
doing
right
with
with
the
iphone
and
very
few
people
actually
go
to
the
trouble
of
turning
off
javascript
in
their
browsers,
but
by
planning
for
the
worst
case
scenario,
we
often
find
that
we
will
have
better
results
in
even
the
best
case
scenario,
so
my
job
at
rent
the
runway
was
to
work.
On
pages
like
this,
if
you've
ever
worked
for
an
e-commerce
site,
this
perhaps
looks
pretty
familiar.
A
We
had
to
test
it
right
with
a
lot
of
acceptance
tests
we
had
to
have
it
work
very
fast
on
mobile
devices,
because,
like
everyone
else,
we
have
a
growing
number
of
our
users
from
mobile
devices
and
what
we
were
finding
was
that
the
old
version
of
this
site
was
not
working
very
well.
I
had
two
co-workers
to
whom
I
owe
a
lot
of
the
work
that
was
done
here.
They
helped
me
a
lot
with
this,
which
is
why
I
want
to
give
them
credit.
A
Their
names
are
john
holden
and
will
summers-
and
we,
you
know
in
the
the
great
death
star
that
was
our
company.
Actually,
it's
more
of
a
star
destroyer.
The
death
star
is
sort
of
google,
probably
in
terms
of
ranking
of
companies.
We
are
not.
We
are
not.
You
know,
darth
vader,
up
striding
across.
We
are
just
little
technicians
trying
to
make
sure
that
everything
is
working
as
well
as
possible.
While
we,
you
know,
stride
across
the
universe,
hunting
down
business
and
rebels.
A
So
have
you
ever
seen
something
like
this?
On
a
page?
Do
you
see
this
custom
scroll
bar
that
somebody
went
to
probably
quite
a
lot
of
trouble
of
implementing
in
this
case
this
is
a
custom
scroll
bar
that
somebody
implemented
solely
to
get
a
slightly
different.
Look
on
that
scroll
bar
now.
Scrolling
has
so
many
things
that
work
very
well
already.
That
features
that
browsers
have
implemented
for
scrolling
that
are
great.
You
can
use
the
space
bar
to
scroll
down.
You
can
use
arrow
keys.
A
If
you,
you
know,
you
don't
have
to
re-implement
anything
on
mobile,
delegating
to
javascript
to
the
javascript
that
your
team
has
written
functionality,
that
browser
makers
have
already
been
devoting
fantastic
amounts
of
resources
too.
It's
just
not
going
to
work,
it's
a
it's
a
recipe
for
self-destruction,
and
I
want
you
guys
to
stay
whole
and
healthy
insane.
So
ignoring
accessibility
is
a
sure
path
to
the
dark
side
of
the
force.
A
So
here's
the
thing
that
I
see
more
and
more
key
parts
of
sites
that
only
exist
in
modals
that
pop
up,
you
know
a
login
form
that
only
exists
in
a
modal,
or
you
know
the
key
key
functionality
that
can
only
be
accessed
by
having
a
fully
functioning
javascript
instance
come
up.
So
if
you
this
was
something
from
our
site
that
used
to
work.
This
was
the
notion
was
that
we
were
going
to
let
people
create
short
lists
of
our
content,
functionality
that
we
want
to
push.
A
We
want
everyone
to
do
this
right,
because
the
more
people
create
these
shortlists,
the
more
engaged
they'll
be
with
our
product
and
then
we'll
have
happy
business
people,
which
means
more
money.
For
us
engineers
right
sounds
great.
Well,
this
only
existed
in
a
little
show
hide
with
a
with
a
you
know.
A
cool
sliding
effect
there
was
no
way
to
access
this
page.
It
didn't
have
a
url.
A
A
If
you
in
the
future,
you
decide
to
deprecate
your
current
web,
app,
which
you
know
you
guys
know
that
you
have
deprecated
your
entire
set
of
code
in
your
lives
started
all
over
again.
You
know
you
switch
from
ember
to
react.
You
switch
from
backbone
to
angular,
and
suddenly
you
can't
call
you
you
don't
want
to
go
through
the
trouble
of
instantiating.
All
of
the
things
all
the
javascript
objects
that
you
need
to
throw
up
that
functionality
anymore.
A
A
A
A
Have
your
server-side
monitoring
set
up
very
well
very,
better
well,
better
than
your
your
client
side,
error,
monitoring
if
you've
already
had
a
javascript
error
on
that
page,
can
you
count
it
to
be
catching
all
of
those
errors,
including
inventors
and
stuff
like
that
and
reporting
it
correctly
to
you,
probably
not,
and
please
join
me
for
a
short
medley
of
every
time.
Somebody
said
I've
got
a
bad
feeling
about
this
in
star
wars.
A
B
A
Have
you
ever
had
a
bad
feeling
when
you
were
writing
a
website,
bad
feeling
about
this
yeah?
Let's
avoid
bad
feelings.
Let's,
let's
do
things
that
we
feel
good
about,
and
you
know
if
you,
basically,
if
you
have
stuff
that
only
works
with
you
know
your
javascript,
your
your
site
being
fully
spun
up
and
working.
You
are
going
to
get
cast
into
the
sarlacc
pit
and
digest
it
for
1
000
years.
A
So
here
is
another
you,
you
probably
think
of
yourself
as
a
user,
all
the
time
you
know
you're
the
person
who
navigates
through
the
site
very
very
very
quickly,
while
testing
that
it
works,
and
you
might
think
of
your
qa
people,
you
might
even
think
about
your
customers,
sometimes
while
you're
coding
a
website.
I
do
hope
occasionally,
but
you
have
another
another
set
of
users
who
sometimes
get
sadly
ignored.
A
A
If
you
are
not
re,
if
you
are
rendering
all
of
your
content
through
javascript,
it
is
going
to
be
take
much
longer
for
robots
to
browse
your
site.
It's
gonna
be
much
more
error
prone.
Have
you
ever
been
like
fiddled
with
like
a
wait
for
ajax
handler
in
a
set
of
acceptance
tests?
Oh
you
turn
the
the
sleep
time
up
to.
A
So
do
you
know
when
you
have
a
javascript
error
on
your
pages?
You
think
that
you
have
taken
care
of
everything.
You
are
probably
wrong.
I
just
don't
believe
you
if
you
have
a
javascript
error
on
a
page
and
I've
seen
these
things
happen
for
reasons
as
silly
as
vendors
overwriting,
your
version
of
underscore
on
a
given
page.
You
may
know
that
you
have
a
problem.
A
You
may
not
know
that
you
have
a
problem
because
it's
only
happening
for
like
androids
running,
like
ice
cream
bar
that
aren't
updated,
but
you've
lost
those
users.
If
javascript
is
all
that,
you
have
to
offer
them,
you
can't
control
their
experience
because
they
they
that
client
is
in
control
of
the
experience
and
while
some
very
clever
people
may
be
able
to
fix
your
javascript
in
the
browser
so
that
it
actually
works,
probably
not
a
lot
of
people.
B
A
A
A
If
it's
an
xhr
request,
which
is
to
say
an
ajax
request,
just
respond
with
json
and
if
it
is
not
an
xhi
request,
if
somebody
is
requesting
the
whole
page
on
initial
page
load
then
wrap
up
all
of
that
ajax
with
wrap
up
that
json
in
an
html
page
and
the
way
that
we
do
that
at
rent
the
runway
is
through
node.
We
have
a
very
small
node
process
running
it's
the
only
thing
we
actually
use
node
for,
but
it
is
so
essential.
A
We
use
node
to
render
that
the
our
react,
content
server
side
before
sending
it
down
the
pipeline,
and
it
has
allowed
us
to
have
the
best
of
both
worlds
here.
So
we
don't
wanna.
Why
did
we
go
to
ajax
in
the
first
place
right
if
a
javascript
sucks
so
much,
then
why
on
earth
did
we
ever
go
to
a
world
where
we
were
getting
huge
amounts
of
our
of
the
content
of
our
pages
via?
You
know,
asynchronous
requests?
A
Well,
we
did
it
because
we
didn't
want
to
reload
the
freaking
page
every
single
time
we
wanted
to
just
respond
sensitively
to
exactly
only
giving
you
know
the
changes
in
information
that
the
user
requested
from
an
already
fully
loaded
app.
So
with
this
you
get
the
best
of
both
worlds.
If
you
are
on
an
initial
page
load,
you
you
give
them
the
full
html
if
it's
the
additional
page
loads.
After
that,
you
already
have
a
fully
loaded
app.
A
You
just
go
out,
ask
for
a
json
of
what's
changed
and
continue
with
your
day.
So
you
too,
I
think,
can
be
a
hero
by
adopting
server-side
rendering
on
your
app.
If
you're
in
react,
this
is
a
this
is
something
that's
very
well
documented,
very
easy
to
do.
If
you
are
on
ember,
I
believe
that
they
are
also
moving
towards
isomorphic
server-side,
rendering
solutions
and
that
it
is
possible
if
you
are
on
backbone
or
anything
that
is
a
little
bit
older
and
maybe
a
little
bit
less
on
the
cutting
edge.
A
I
can't
help
you,
but
maybe
you
can
help
you
there's
a
backbone
server-side,
rendering
thing
that's
the
best
thing
I've
heard
all
day.
Thank
you
so
much,
that's
great
good,
good
job
backbone,
guys,
okay,
so
people
on
back
button,
you
have
no
excuse,
never
mind.
I
was
going
to
give
you
an
out,
no
else.
A
A
This
really
really
sucks
as
a
user
experience,
because
what
do
users
want
to
do
when
they
got
onto
your
site?
They
want
to
click.
They
want
to
go
somewhere
if
they're
familiar
with
the
behavior
of
your
site.
They
want
to
get
there
as
fast
as
possible,
just
as
han
had
to
shoot
as
fast
as
possible
han
shot.
First
guys.
Is
that
a
joke?
Anyone
anyone
gets
here
so
here
is
a
quick
and
dirty
list
of
recommendations.
A
If
you
have
infinite
scrolling,
keep
a
more
link
if
you
have
a
modal
back
it
up
with
a
url,
even
better
write
it
as
a
standalone
page
and
render
it
into
a
url.
If
you
have
forms,
remember
that
you
are
still
writing
semantic
html,
keep
their
method
and
action
attributes
and
ensure
that
your
server
is
set
up
to
respond
to
it.
Never
re-implement
functionality
that
browsers
do
better
and
also
maybe
your
acceptance
sets
suck
because
everything
is
implemented
through
ajax.
A
A
Disregarding
all
of
this
advice
is
a
sure
path
to
the
dark
side
of
the
force,
but
you
know-
maybe
maybe
you
actually
want
that
now.
Here
are
some
cases
where
I
could
think
that
you
actually
would
want
javascript
to
be
the
only
way
that
something
works.
If
you
have
a
paywall
on
your
site,
and
you
want
to
make
sure
that
people
who
have
like
no
script,
plugins
or
stuff,
if
they're
not
giving
you
the
page
view,
then
you're
not
giving
them
the
content.
A
As
a
true
star
wars
fan,
the
prequels
really
hurt
me
that
acting
right.
So
what
I
want
to
say
by
that,
though,
is
that
all
of
these
rules
are
conditional,
like
all
best
practices
are.
If
you
have
something
that
is
a.
If
you
have
something
that's
very
complicated,
you
may
not
be
able
to
get
it
to
work
without
javascript.
If
you're,
literally
writing,
google
maps
is
that
going
to
work
without
javascript?
A
So
the
the
principle
that
I'd
like
to
say
then
is
we
talk
about
mobile
first
a
lot,
and
then
I
think
we
should
add
to
that
javascript
last
javascript,
truly
as
a
as
a
progressive
enhancement
on
top
of,
what's
already
a
great
functional
site.
This
is
my
recommendation
for
developer
and
user
happiness.
A
So
thank
you
so
much
for
listening.
This
is
a
picture
of
me
dressed
as
a
sith
at
halloween
one
year.
It
was
a
great
halloween
if
you
want
to
know
any
more
about
how
to
actually
implement
this.
In
your
context,
or
if
you
think
all
of
this
is
really
dumb-
and
you
want
to
fight
me-
please
hit
me
up
on
twitter
and
I'd
be
glad
to
respond
to
you.
Thank
you
all
so
much.