►
From YouTube: What should the web do - Mike Geyser
Description
Sometimes we take things for granted. We get so caught up in the churn of software development, that we never take the time to reflect, introspect and ask the important questions. For me, this is wondering where we are, how we got here and where we should go next.
Join me as I unpack a little bit of history, a little bit of context, and ask a really hard question: what *should* the web do?
This talk was recorded at the Jozi.JS meetup group on 31 January 2019.
https://www.meetup.com/Jozi-JS/events/257737169/
Disclaimer: The opinions in this talk are those of the individual and do not necessarily represent those of this channel, the meetup group, or it’s sponsors.
A
So
for
those
of
you,
thank
you.
Thank
you
for
coming.
I'm
gonna
talk
to
you
tonight
about
a
whole
bunch
of
stuff.
It's
only
my
weight
that
is
on
I
am
recording
I'm
gonna
talk
to
you
about
a
whole
bunch
of
stuff.
That
is
only
tangentially
related,
and
it's
a
topic.
That's
very
near
and
dear
to
my
heart
right.
It's
this
question
of
well.
A
What
should
the
wave
do
so?
I?
Don't
need
a
hell
of
a
lot
of
any
introduction,
but
for
those
of
you
that
don't
know
me,
hi,
I'm,
Mike,
I,
think
you'll
agree
that
that's
a
reasonable
likeness
of
me
I'm
not
wearing
the
same
shirt,
but
you
can
agree
that
it
is
me
I'm,
a
Google,
developer
expert
in
web
technologies.
This
is
now
my
second
year
being
a
gde,
so
I
am
yet
again
an
uncharted
territory.
A
They
haven't
kicked
me
out
yet
so
hopefully
that
means
that
I'm
not
stuffing
up
too
badly
again
I
work
here
at
BBD,
along
with
Jerry
in
the
research
and
development
team.
Here,
okay
and
the
reality
is
that
I,
don't
think
I
could
succinctly,
explain
to
you
what
I
do
on
a
day
to
day
basis.
We
do
we
do
stuff
right,
they
pay
us
every
month
they
haven't
fired
us
and
I
have
no
written
warning,
so
I
think
I
think
it's
sort
of
working
out
and
I've
been
here
for
six
years.
A
This
light
is
completely
redundant
because,
while
you're
here,
Jerry
and
I
with
Lynn
who's,
unfortunately
super
super
busy
organized
the
show
so
yeah
we're
really
really
keen
for
for
you
to
be
here.
We're
really
keen
for
some
of
you
to
speak.
So
if
you
are
interested
in
speaking
of
you'd
like
to
scratch
an
itch
or
if
you
think,
you've
got
something
meaningful
to
share,
let
us
know
we'll
help
you
through
it.
We're
really
really
keen
to
take
first
time
speakers
and
we
give
really
really
good
feedback.
A
A
Jeri
encouraged
me
to
just
not
have
slides
at
all
and
just
talk
for
a
half
an
hour,
but
I
felt
like
it
was
really
really
important,
because
otherwise,
how
was
I
gonna
put
memes
in
the
presentation
right
and
like
what's
a
presentation
what
that
means
anyway.
So
just
so
that
you
know
does
keep
in
mind
that
this
is
going
to
flow.
It
may
be
a
little
bit
tangential
at
times
and,
like
it
said,
expectations
properly.
A
This
topic
is
also
very,
very
near
and
dear
to
me
very,
very
personal
to
me
and
the
reason
why
is
because
my
last
round
interview
for
the
gde
program
was
with
my
dev
hero,
which
is
Eddie
Oz
many
right?
Who
knows
that
EOS
Mini?
Yes,
there
are
at
least
some
hands
right,
super
super
cool
and
it
was
like
the
ultimate
boss
battle
right.
I
have
to
speak
to
my
dev
hero
and
answer
a
whole
bunch
of
questions
about
the
whip.
A
So
I
was
all
psyched
out
and
all
in
the
zone
and
and
thought
I
was
doing
really
really
well
talking
about
how
I
speak
community
and
things
about
the
web.
That
interest
me
and
then
he
stumped
me.
He
nailed
me
with
this
one
question
that
has
haunted
me
ever
since
for
the
last
8
15
to
18
months,
and
that
is,
if
you
could
change
anything
on
the
web,
what
would
it
be?
I
was
unprepared
for
that
right,
I
had
never
even
thought
in
those
terms.
What
do
you
mean
if
I
could
change
anything?
A
A
Then
we
also
talk
a
whole
bunch
of
rubbish
on
social
media
and
that
can
be
whatever
flavor
that
you
want
right.
If
you
like,
sharing
images
or
we
connect
with
one
another,
we
connect
with
one
another
on
silly
human
levels.
We
use
this
amazing
platform
to
talk
some
of
that
meaningful.
Some
of
it
isn't
meaningful
some
of
its
awful,
my
Instagram
but
hey
Jerry
likes
Instagram,
and
we
don't
judge
her
for
it.
A
Then
what
else
is
the
web
for
the
web
is
for
ads?
No,
really.
It
is
for
ads
and
I.
Think
it's
an
important
point
right.
There's
a
lot
of
information.
That's
coming
at
us,
people
trying
to
sell
stuff
to
us
and
it's
only
partly
a
joke,
because
the
web
is
for
commerce.
We
buy
stuff
who
who's
bought
stuff
this
week
from
the
web.
Ok,
please
some
people
right.
We
use
it
as
a
commercial
platform.
I
think
it's
disingenuous
for
us.
A
As
software
develops,
professional
software
developers
are
aiming
to
be
professional
software
developers
to
look
at
this
platform
that
we
build
for
as
not
being
commercially
viable
right.
We
want
to
get
paid
for
this
stuff.
It
needs
to
be
an
ecosystem
that
can
support
payment
news
information
right.
We
use
this
as
a
platform
to
disseminate
very,
very
valuable,
critical
information
that
saves
lives
right.
There
changes
political
landscapes,
we
use
this
platform
for
knowledge,
I
have
learned
so
much
from
it.
I
remember
before
the
internet
was
ubiquitous.
A
I,
remember
how
difficult
it
was
looking
up
in
encyclopedias,
I
still
have
encyclopedias
at
home.
I
haven't
opened
them
up
since
the
internet
right
because
we
have
amazing
sources
of
information.
We
have
encoded
the
sum
total
of
human
knowledge
in
a
universally
accessible
mechanism,
and
that's
something
that
I
feel
very,
very
passionate
about.
So
I
think
that's
that
sort
of-
and
there
might
be
some
bits
and
pieces
that
we're
missing
around
the
edge.
But
that's
what
we
use
it
for
right.
A
Does
anybody
else,
have
anything
salient
to
add
any
other
things
that
we
use
it
for
that
I've
missed
sorry,
gaming,
there's
exactly
another
way
of
us,
interacting
with
other
human
beings
right
I.
Remember
when
we
used
to
play
games
without
being
connected
to
the
Internet
right
when
you
had
to
drag
your
laptop
or
you
saw
your
desktop
to
a
LAN
party
and
actually
see
people
in
meatspace
to
be
able
to
frag
them,
okay,
so
gaming,
yes,
telecommunications,
voice,
connectivity
like
let's
be
real.
A
A
Why
should
we
really
care
and
I
feel
that
this
is
an
important
one
to
dig
into,
because
we
take
a
lot
of
the
stuff
for
granted
right,
it's
just
a
thing:
it's
a
thing
that
it
has
always
existed
for
some
of
you,
okay,
and
the
reason
why
I
think
we
should
care
is
exemplified
by
luckily
a
tweet
that
happened
just
three
days
ago.
Four
days
ago
now
by
David,
Hanna
Maya
Hansen,
the
web
is
isn't
just
another
software
platform.
It's
the
greatest
software
platform.
The
world
has
ever
seen
no
permissions,
no
masters
readable
source
code.
A
A
At
the
same
time
and
like
I'm,
gonna,
I'm,
gonna
dig
into
a
little
bit
of
a
history
lesson:
I'm
gonna
start
going
backwards
and
forwards
and
time
and
I'm
first
going
to
go
back
now,
just
over
20
years,
a
couple
weeks
over
20
years
ago,
this
gentleman
said
the
following
stuff
about
the
World
Wide
Web.
Now.
B
A
Now
he's
clearly
in
an
intelligent
man
he's
departed
as
those
who
know
bow,
he
is
dead,
I'm
not
saying
he
was
holding
the
fabric
of
reality
together,
but
it
does
feel
like
we're
on
the
darker
timeline
Sundays,
but
this
was
this
was
20
years
ago
right.
Let's
talk
about
a
little
bit
further
back,
let's
talk
about
50
years
ago
and
in
fact,
coming
up
March,
it's
the
50th
anniversary
of
this.
So
who
knows
where
these
pictures
are
taken
from
anybody
other
than
Jerry,
because
I've
been
talking
to
her
about
it
for
a
week.
A
A
This
is
titled
the
mother
of
all
demos,
and
it
happened
at
the
American
computer
manufacturers
association
in
1968,
where
he
showed
the
first
working
version
of
a
software
to
the
first
version
working
version
of
the
mass.
He
showed
the
first
version
working
version
of
document
sharing
and
live
code,
a
live
document,
editing
of
voice
communications
in
1968
before
anything
existed
right.
The
ideas
here
were
not
necessarily
his
own.
A
He
cobbled
them
together
by
ideas
that
had
preceded
him
and
in
fact
the
idea
of
this
network
sharing
of
information
was
built
off
of
something
created
or
theorized
by
a
gentleman
by
the
name
of
Vannevar
Bush
in
1948.
Okay,
his
idea
was
we
could
we
could
link
information
together
on
microphone
and
he
called
this
thing-
a
mimics,
okay,
and
that
basic
theory
from
1948
ended
up
resulting
in
the
world
wide
web
that
we
used
today.
A
Okay,
so
when
we
think
of
the
this,
the
revolutionary
new
feature
that
has
react
hooks,
it
keeps
in
perspective
on
what
revolution
means
and
what
real
innovation
looks
like.
Okay,
not
heading
on
react,
I'm,
not
heading
on
react,
but
let's
history,
a
lesson
aside
now:
I
believe
that
this
is
compulsory
watching
for
any
software
developer
right.
You
should
see
this.
We
should
understand
our
heritage
where
we
come
from,
but
moving
a
little
bit
forward
in
time
from
that
heritage.
Who
knows
what
that
is?
Who
can
give
me
a
wild
guess
as
to
what
that
is?
A
A
No
I
closed
it
down
apologize
to
him
for
me,
so
this
is
the
first
humble
website
that
was
created
as
a
part
of
the
World
Wide
Web
in
1989
when
it
went,
live
in
1991
and
was
created
by
this
gentleman,
so
Tim
berners-lee,
ok
and
all
he
did
is
he
built
on
the
work
of
others.
He
didn't
invent
the
Internet,
the
network
of
networks
that
had
to
exist
already.
There
are
other
people
that
did
amazing
work.
A
He
there
were
other
people
that
theorized
this
idea
of
linking
information
being
Vannevar
Bush's
Memex,
almost
a
half
a
century
previously
to
him,
even
maybe
not
like
40
years,
30
years,
whatever
the
case
may
be,
and
he
built
all
other
stuff
up
and
invented
the
world
wide
web
wallet.
Sir.
Ok,
how
we
could,
rather
than
having
to
log
on
to
different
computers
and
copy
information
locally,
to
be
able
to
view
it.
We
could
link
that
in
a
distributable,
crawlable
public
manner
right.
A
A
A
This
is
a
snapshot
of
what
this
mission
and
vision
looked
like
at
this
moment
and
that's
to
say
that
this
World
Wide
Web,
this
invention
is
a
web
for
all
for
every
human
being
that
it's
a
web
on
everything
it
needs
to
be
accessible
and
every
device
every
form
factor
it
mustn't
be
predictive
as
to
where
it
can
be
used.
It
needs
to
be-
and
this
is
a
relatively
new
one-
a
web
for
rich
interaction.
It
mustn't
just
present
documents
and
present
information.
A
It
needs
to
enable
experiences
for
people
right,
a
web
of
data
and
services
that
we
expose
our
data
as
being
inherently
linkable
our
services
as
being
inherently
consumable
by
one
another.
Creating
this
this
global
composited
interface,
if
that
makes
sense,
and
then
the
last
one,
is
that
this
web
of
trust
and
I
don't
think
we
always
do
so
well
with
that
one.
But
the
idea
is
that
we
should
understand
what
is
trustworthy
information
and
what
is
not
when
are
we
safe
and
when
we
are
not?
When
are
we
exposed
and
I
think
as
developers
this?
A
Okay,
I,
don't
know
how
many
of
you
have
actually
looked
and
thought
about
this
so
before
we
can
figure
out
like
where
the
web
is
going,
I
think
we
need
to
look
at
the
slice
and
time
of
what
the
focuses
of
an
organization
like
the
w3c
are,
and
this
is
the
stuff
that
they
care
about
representing
in
the
web.
Commerce.
It
needs
to
be
an
commercially
viable
platform,
an
open
marketplace
where
everyone
can
compete
right,
entertainment.
We
use
it
for
interesting
things.
Right.
A
Entertainment
is
a
fundamental
part
of
the
human
condition
communication
speaking
to
one
another
payments,
again
the
other
side
of
that
commerce
marketplace.
We
need
to
be
able
to
safely
transact
online
we're
going
to
buy
via
this
platform
things
it's
no
longer
just
browsers
on
a
big
CRT
desktop
like
Tim
berners-lee.
Had
it's
it's
everything
we
touch
that
somehow
connected
to
the
Internet,
some
people's
toasters
and
washing
machines
and
fridges
are
connected.
How
does
this
all
work
together?
Accessibility,
we've
been
relatively
poor
with
surfacing
this
information
to
very
few
people.
A
Accessibility
is
important
to
people
that
I,
don't
know,
may
not
be
able
to
see
a
perfect
idli
may
not
be
able
to
consume
media
the
same
way
as
we
assume
that
they
should
be
able
to
internationalisation
people
that
don't
necessarily
speakers,
speak
English
want
to
consume
this
resource
and
that's
always
been
a
big
concern
and
it
continues
to
be
a
big
concern
today.
How
do
you
code
for
the
web
and
work
with
the
web?
If
you
don't
speak
English,
it's
not
easy
and
then
finally,
security
in
the
representation
of
data
is
consumable
manner.
A
There
are
a
lot
of
people
from
different
backgrounds
involved
in
how
we
use
this
thing,
so
I'm
going
to
focus
a
little
bit
on
how
we
build
on
this
thing
rather
than
how
we
consume
on
this
thing,
because
we're
all
programmers
here,
okay,
but
I,
think
I-
think
it's
valuable
asking
that
question
and
I
think
just
just
hang
on
to
it:
okay,
so
what
I'm
gonna?
What
I'm
gonna
look
at
next
is
I'm
gonna.
Look
at
some
features
as
to
where
the
way
it's
going,
that
you
may
or
may
not
be
aware
of.
A
Give
me
a
nod
if
you
are
aware
of
it,
because
this
is
all
stuff,
that's
in
the
short
to
medium
term.
Okay,
so
we're
going
to
start
off
with
their
commerce
aspect.
We've
got
the
payment
request:
API
who's
used
who's,
put
their
credit
card
into
a
website
and
not
known
whether
it's
going
to
be
stolen.
Okay,
that's
terrifying
or
use.
The
service
like
PayPal,
so
you
don't
have
to
do
that
right.
Security
is
a
big
deal
and
security
with
payments.
A
We
need
to
be
able
to
tender
payment
safely
and
effectively
and
with
trust,
so
the
payment
request
API
as
a
way
of
abstracting
that
a
little
bit
so
that
the
browser
has
a
consistent
interface
behind
asking
you
for
money.
So
you
can
save
your
credit
cards
in
something
you
trust
or
put
your
details
into
a
text
box,
that's
Chrome
based
rather
than
or
Firefox
based,
rather
than
some
random
pop
up
in
a
website.
A
Okay,
so
I
think
that's
a
big
one
for
us,
as
consumers
and
as
service
providers,
because
we
want
people
to
feel
comfortable
buying
our
services
in
a
safe
mechanism
online.
The
web
share,
API,
okay,
who's
gone
to
a
website
that
has
a
million
social
media
icons
and
you're,
like
oh
man,
the
social
media
icon
that
I
want
doesn't
work
or
it
doesn't
work
the
same
way
to
share
to
Twitter
as
the
previous
site
that
I
was
on
that
shared
to
Twitter.
So
you
know
what
I'm
gonna
do
it
myself?
A
Okay,
this
is
something
where
Native
has
gotten
it
far
better
like.
Oh
it's
level.
Integration
for
sharing
and
sharing
social
content
is
very,
very
good.
The
web
is
playing
catch-up
and
this
is
a
way
of
encoding
that
so
that
we
can
have
a
consistent
mechanism
to
share
our
information.
Why?
Because,
if
we
share
our
information
consistently,
we
respect
the
rights
of
the
IP
holders
better.
We
have
a
better
mechanism
to
to
trust
the
stuff
that
we're
putting
into
the
textbox
at
somewhere
on
somebody's
computer.
A
Okay,
so
moving
on
from
that,
then
we've
got
web
us
be.
Who
knows
about
web
us
be
okay?
Why
do
we
need
web
us?
Be?
What
is
this
rubbish?
Well,
that's
because
who
has
an
old
computer
with
all
peripherals
that
no
longer
work
right,
because
you
update
your
operating
system
and
the
drivers
done
update?
That's
a
real
problem,
our
platforms
suck
right.
We
want
a
consistent
way
of
engaging
with
the
stuff
that
we
can
use
across
Mac,
Windows,
Linux
and
whatever
operating
system
comes
in
the
future.
A
So
who
understands
what
I
mean
when
I
say
vo
right
who
understands
what
I
mean
when
I
say
AR
now,
XR
is
this
idea
of
anything
that
adds
shape
to
the
web
either
depth
or
breadth
or
volume
or
additional
information
merges
our
realities?
Okay,
this
is
a
really
really
interesting
and
growing
field
from
a
device
perspective
and
how
we
engage
with
the
world.
We
don't
care
about
flat
documents
anymore
right,
we're
exploring
interactivity,
different
ways
of
engaging
with
the
world
around
us
and
we
expect
the
web
to
grow
with
us
in
that
sense.
A
Otherwise,
if
it's
just
forever
remains
an
analogy
for
some
paper
oriented
document,
that's
just
linkable:
it
loses
some
of
its
relevance.
Ok,
webassembly!
Who
knows
what
I
mean
when
I
say
this?
Ok
right
so
webassembly
is
this
idea
that
javascript
is
great.
We
like
javascript,
because
it
interacts
well
with
the
Dom.
It
serves
a
very
particular
problem,
but
there's
a
whole
bunch
of
either
old
code
or
really
really
performant
optimized
code
that
will
never
ever
run
on
the
web
and
JavaScript
as
a
compiled
target.
A
It's
really
awful,
taking
your
c-sharp
code
or
your
java
code
or
go
and
generating
it
to
JavaScript,
is
just
a
awful
idea.
It's
not
meant
for
that
right,
so
web
assembly
is
this
idea
that
we
want
to
make
us
a
more
open
platform
for
everyone
to
give
better
constructs
for
more
performant
code
for
more
for
better
ways
of
building
stuff
for
the
web.
So
web
assembly
gives
us
this
lower-level
primitive
that
lets
us
reach
into
the
heart
and
soul
of
the
machine.
A
It's
little
sandbox
by
the
security
that
we
come
to
trust
in
the
browser
and
do
cool
stuff.
Ok,
awesome
web,
often
API
now
I'm
pretty
sure
nobody
knows
what
I'm
talking
about
here.
Ok,
everybody
in
this
room
has
entered
a
password
into
a
website
right
everyone's
had
password
details
emailed
to
them.
By
have
you
been
porn?
Calm
right,
all
you,
you
reuse
passwords,
because
you
can't
remember
a
million
of
them
or
you've
got
a
password
manager.
I've
got
a
password
manager,
passwords
suck
right,
there's
transmitted
in
plain
text:
they're
awful!
A
There
are
terrible
mechanism,
they're
insecure,
inherently
by
design
web
orphan
is
this
idea
of
we
can
be
better
than
passwords
and
we
can
use
asymmetric
cryptography
to
generate
private,
to
keep
private
public
key
pairs
and
use
that
to
start
to
log
in
to
God
our
identity
online.
A
far
more
secure
mechanism
like
who
uses
SSH
keys
right
some
people
using
SSH
keys
to
log
into
websites
right
and
using
security,
densifies
I've
got
one
in
my
bag.
A
Well,
you've
got
a
cheap,
$5,
little
plastic
key
that
you
can
plug
in
and
push,
and
it
generates
a
public/private
key
pair
that
I
can
move
between
machines.
That's
my
identity
like
this
is
amazing
stuff,
and
this
is
this-
is
now
you
can
use
this
now
and
then
stuff.
That's
coming!
Where
portals
now,
who
does
anybody
watch
chrome,
dev
summit,
where
they
talked
about
web
portals
and
the
idea
for
a
new
internet
changing
the
way
we
navigate
between
pages
and
surfacing
it?
A
This
is
basically
iframe
2.0
right
doing
it
properly
for
a
change
so
that
we
can
show
moving
between
different,
realms,
moving
between
different
pages
in
our
site,
far
more
naturally
and
progressively
we're
packaging.
Okay,
we're
still
tied
to
this
idea,
even
though
we've
got
this
decentralized
framework
or
this
decentralized
platform
we're
still
tied
to
this
idea
of
having
to
visit
a
origin
to
server
site.
A
We're
packaging
is
this
concept
that
we
can
take
all
of
our
website,
build
it
sign
it
properly
and
then
have
any
one
servant
who
should
care
right
as
long
as
it's
actually
our
content
where
it
comes
from,
and
that
means
that
it's
far
more
performant
for
us,
for
example,
saying
we
don't
have
to
pay
the
300
millisecond
text
to
go
download
something
from
what
West
Europe,
and
this
is
a
thing
that
is
being
pushed
for
very
heavily.
Has
anybody
heard
of
the
amp
project
accelerated
mobile
pages
or
played
around
with
amp?
A
This
is
basically
amp
standardized.
Okay,
so
that's
some
of
the
stuff
that's
coming.
This
is
the
cool
stuff.
That's
coming
down
the
road,
and
this
all
sounds
great
right
who
thinks
this
song?
Anybody,
like
anybody,
still
excited
I
think
this
is
awesome
stuff,
but
some
of
it,
like
portals
I,
don't
know
I
didn't
think
there
was
really
a
problem
where
US
beef
I
think
it's
great,
where
the
assembly
is
great,
but
not
all
of
it.
Not
all
of
it
is
stuff
that
I
care
about.
So
let's
unpack
that
a
little
bit.
A
How
did
how
did
this
stuff
come
to
be?
How
was
this
the
direction
that
we
went?
Okay
now
you
would
be
forgiven
if
you
said
the
w3c.
Was
it
this
organization
that
Tim
berners-lee
organized
and
still
exists
and
manages
the
standard
and
make
sure
that
HTM
and
the
browsers
do
what
they
need
to
do?
Who
thinks
that's
the
answer
or
have
I
already
prompted
you
I
already
prompted
you
who's
heard
of
the
what
working
group
again?
A
Yes,
Jerry
so
in
2004,
Mozilla,
opera
and
Safari
after
a
w3c
meeting
where
they
were
deciding
on
XHTML
and
I
know,
at
least
one
person's
gonna
nod
say
actually
in
the
room
when
I
say
XHTML,
when
they
were
particularly
happy
about
the
direction
of
HTML,
they
decided
that
they
were
going
to
go
and
develop
HTML
in
a
much
more
open
manner.
Okay,
they
were
going
to
organize
their
own
thing,
their
own
working
group
and
then
several
years
later,
in
2008
they
decided
right.
We'll
have
html5
done
in
the
Year
2022.
A
Now
that
wasn't
acceptable
to
anybody
right.
There
was
an
awful
answer
and
there
were
seeing
that
the
web
atrophy
really
quickly.
So
they
decided.
This
is
an
awful
joke.
We're
gonna,
take
control,
we're
gonna,
run
the
standard.
Okay
and
the
w3c
was
like
wait,
but
aren't
we
the
standard
provider?
What
do
you
mean?
You're
gonna
run
the
standard,
we're
running
the
standard
we
have
our
own
standard
and
then
over
time.
A
There
was
this
impasse
where
they
were
driving
the
standard
forward
in
the
living
manner,
in
an
open,
publicly
accessible
way,
and
the
w3c
was
trying
to
catch
up
and
trying
to
make
sure
that
they
merged
it.
There
are
versions
of
the
the
what
working
group
HTML
spec.
They
were
forked
and
copied
into
the
w3c
that
have
died.
There
are
multiple
versions,
there's
55.1,
there's
a
living
standard
and
the
net
result
is
I
mean
this
question
of
like.
Why
why?
Why
is
this
a
problem?
A
Why
are
we
in
this
world
and
unfortunately,
it's
where
we
are
so
perhaps
to
shed
a
little
bit
of
light
on
HTML
and
some
of
the
key
standards
like
fetch,
for
example,
SEC,
like
the
Dom
itself,
how
the
w3c
works
is
it
has
standards,
recommendations
that
it
proposes?
So
when
you
get
to
rec,
which
is
the
far
right-hand
side,
that's
the
recommendation
of
how
a
browser
should
work
with
something
with
two
browser
implementations
that
prove
that
it
works.
A
Ok,
so
that
means
that
browsers
have
to
implement
it
properly
before
it
gets
to
wreck
on
the
far
left-hand
side.
They
accept
input
from
two
sources,
one
of
which
is
an
organized
workshop
and
the
other
one
is
this
wick
G,
which
is
a
working
into
a
web
incubation
group
where
they
trying
something
weird
and
radical
and
very,
very
different.
That
may
not
result
in
anything,
but
it's
time
boxed
to
about
a
year.
Okay,
now
out
of
that
whole
structure,
either
via
a
workshop
or
the
working
group,
we
get
this
working
draft
specification.
A
We
get
this
idea
of
we're
going
to
start
growing
a
standard,
however
long
that
may
take,
then
that
goes
to
a
candidate
recommendation
and
the
the
candidate
recommendation
goes
to
a
proposed
recommendation
and
the
proposed
recommendation
once
it's
got
two
browsers
that
have
implements
it
goes
to
an
actual
okay
cool.
This
is
now
our
recommendation.
A
So
that's
a
little
bit
heavy-handed.
Some
of
you
may
recognize
that
as
a
very
waterfall
oriented
approach,
okay,
but
the
real
challenge
is
this
that
all
of
that
is
driven
by
w3c
members.
You
have
to
pay
to
be
a
w3c
member,
only
the
big
organizations
or
independent
bodies,
or
are
people
who
have
input
into
this
process.
Okay,
and
in
fact,
workshops
are
only
composed
of
w3c
members.
A
You
may
get
an
opportunity
as
the
general
public,
so
there's
two
ways
that
you
can
interact
with
this
process,
and
this
is
just
this
is
as
best
as
we
can
explain.
This
opaque,
opaque
process.
Gerry
can
attest
the
fact
that
I've
been
trying
to
figure
this
stuff
out
for
a
little
while
you
can
comment
on
proposed
recommendations
as
they
go
through
and
try
and
raise
awareness
on
the
Internet
or
the
working
incubation
groups
when
they're
spitballing
a
really
random
idea.
A
They
have
their
own
community
that
they're
required
to
listen
to,
and
if
you
can
engage
in
their
community,
you
can
shape
the
view
of
where
this
proposal
is
going
before
it's
too
late,
but
by
the
time
it
gets
to
recommendation
like
you've
got
two
browsers
that
are
working
like
that.
There's
no
way
you
can
change
it
really
right.
That's
why
we
still
have
the
marquee
tag
anyway,
so
this
is
maybe
a
little
bit
of
insight
into
why
that
schism
between
the
what
working
group
and
the
w3c
happened,
but
that's
only
part
of
the
problem
right.
A
The
other
thing
that
we
rely
on
and
is
very
brilliant
to
us
being
the
JavaScript
meetup
group
is
this
idea
of
JavaScript
now
javascript
is
a
trademark,
a
trademark
owned
by
Oracle
I,
don't
know
how
many
people
that's
news
to
okay,
but
it
is
affect
the
JavaScript
that
we
actually
write
is
called
ACMA
script.
Ecmascript.
Yes,.
A
No,
it's
run
by
an
institution,
so
that's
an
important
point:
there's
a
difference
between
open
standard
and
open
source
right,
open
source.
You
can
take
and
modify
and
go
on
in
there.
Parts
of
the
web
that
are
open-source
but
open
standard
means
that
everyone
can
see
what
the
standard
is.
You
don't
have
to
pay
for
it
like.
There
are
other
standards,
iso
standards
particular
or
some
iso
standards
and
some
other
things
I
think
I.
A
Triple
E
is
one
of
them
where
you
have
to
pay
to
get
whatever
that
standard
may
be
okay,
you
have
to
pay
them
to
be
able
to
see
it.
So
the
web
is
open
standard,
definitely
in
some
parts
of
our
open
source
and
that's
a
big
difference
between
the
w3c,
which
is
the
open
standard
view
and
the
what
working
group.
That's
the
open
source
view
so
make
sense.
A
Where
was
that
right,
so
I'm
just
quickly
going
to
talk
to
you
about
Eckman
script?
So
we
understand
that
because
this
is
the
part
where
we
probably
rarely
engage
with.
So
we
write
ECMAScript
now
ACMA
is
the
european
computer
manufacturers
association
that
was
given
in
the
mid
90s
javascript
to
look
after
hey
here's,
the
thing
that
we
wrote.
A
We
think
it
needs
to
be
standardized,
look
after
it
and
then
by
the
late
90s,
the
the
european
computer
manufacturers
association
was
like
well,
it
doesn't
really
make
sense
for
this
to
be
a
European
thing
and
they
formed
the
Ekman
International.
So
much
like
so
many
acronyms
ACMA
doesn't
actually
stand
for
anything
anymore.
It's
become
what's
the
organization
name
of
particular
interest
to
us.
Is
this
working
committee,
which
is
technical
committee
39
and
those
are
the
awesome
people
that
in
a
very
open
manner,
grow
and
evolve?
A
A
What
should
the
web
do
now?
I
bet
you're
waiting
for
an
answer
right
now,
you'd
be
wrong
because
I
still
don't
know
and
I
think
the
important
part
is
that
we
need
to
talk
about
this.
This
isn't
just
a
thing
that
exists.
This
isn't
just
a
fake
to
complete
that
we
must
accept
that
other
people
are
developing
right.
We
may
not
be
able
to
change
it
as
easily.
We
may
not
be
able
to
go
into
the
w3c
and
hack
away
at
something,
but
we
can
speak
to
the
incubation
group.