►
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
B
A
C
C
C
C
F
G
G
C
F
C
F
C
A
bunch
of
other
cool
features
beyond
that
span
expect
here,
but
my
dependencies,
which
are
actually
pejorative
my
application
I,
were
stuck
in
2014,
and
so
it
was
really
painful
thing
for
me
and
I
had
to
jump
us,
and
you
know
everything
from
like
just
you
know:
use
source
of
github
get
around
and
chemic,
nor
trying
to
kind
of
for
myself,
so
that
I
could
just
upload
and
save
you.
My
you
know
and
performance
for
my
for
my
board.
So.
C
C
C
C
G
C
I
mean
serve
locally
slow
experiences,
it's
more
fights
over
the
wire.
But,
more
importantly,
for
me,
somebody
who
dies
very
kind
of
conscious
about
time
now
and
just
you
know
what
it
means
to
be
a
new
internet
user
markets.
Working
off.
You
know,
resource
constraint
devices,
not
necessarily
a
fancy
word
like
like
I
had,
but
you
know
maybe
a
ten
dollar
phone
or
30.
Where
you
know
data
your
mobile
data
is
currency,
you
know
so
so
it
might
matter
in
emerging
markets.
C
Not
only
do
the
web
experiences
like
they're,
just
tremendously
crappier,
with
all
that
JavaScript
load
right
and
you
know,
I
love,
you
know,
I
open
my
mentor,
New,
York
and
I
know
you
all
love
the
web
in
emerging
markets,
people
for
the
first
time.
You
know
they
haven't,
had
the
luxury
of
ever
owning
a
desktop
device
or
not
remember
having
any
different
way
to
get
online
right,
and
so
we
have
these.
C
C
C
Of
the
web,
and
as
folks
who
understand
you
know,
mechanisms
community,
let's
take
a
look
and
kind
of
examine.
You
know
what
this
means
for
the
health
of
that
and
why
this
is
bad
for
all
of
us
and
water
first
started
again.
Our
dependencies
are
the
majority
of
our
web
application
code
that
we
should
and
they're
stuck
in
2004
a
14.
We
also
have
native
features
that
are
not
getting
used
or
that
are
underutilized
right
and
so
there's
opportunities.
There's
there's
mrs.
miss
opportunity
here
for
kind
of
harvesting
new
features
at
scale.
C
F
C
E
C
And
all
of
that
lost
kind
of
author
intent,
which
is
like
just
an
unfortunate
thing.
You
know,
so
these
a
few
source
are
definitely
gone,
modern
doctor,
so
you
know
so
I
think
this
is
one.
That's
not
community
and
I
have
invited
here's
one
of
the
big
meat-eaters
and
babble
I
mean
kind
of
we're
talking
a
lot
of
stuff
with,
as.
C
And
it's
kind
of
Earth's
world
of
like
cryptic
bugs
at
scale
I.
You
know
and
we're
should
be
heavily
transpose
everything
pong
field
and
are
and
we're
building
upon
that
infrastructure,
which
now
means
that
we're
also
relying
on
these
pucks
at
scale,
which
you
know,
which
means
you
know,
library,
authors
like
even
if
they
want
to
publish.
C
G
C
C
C
C
We're
kind
of
shipping
and
exporting
in
scale,
so
that's
that's
bad
right,
and
so
there
was
disputed
responsibility
matrix
like
whose
bug
is
it
anyway?
So
let's
look
at
the
table
looking
at
browsers,
you
know
so
one
of
the
problems
is,
you
know
we
have
transphobic
code
poly
code.
Sometimes
it's
different.
E
C
B
C
Code
and
you
know,
and
the
uses
of
use
of
a
polyfill,
it's
meant
to
be
a
stopgap
right.
Who's
never
ever
ever
ever
been
to
status
codes,
never
meant
to
be
something
that
we
just
stuck
with
forever
and
they
kind
of
become
these
fixtures.
These
permanent
fixtures
that
we
just
like
happily
install
and
often
question,
and
so
there's
an
interesting
that
I'd
like
to
point
out
here,
because
we
talked
about
two
kinds
of
code
right.
There's
like
the
code
that
you've
authored
there's
the
code
that
came
from
you.
C
Contributors
all
around
the
world
and
web
developers
I
think
have
solved
this
problem
for
their
application
code
by
creating
a
dynamic
way
for
for
us
to
be
able
to
pick
our
targets
and
and
therefore
kind
of
like
the
minimally
transpose
version
of
for
you
know
the
browsers
that
we're
turning
so
this
case
to
these
kind
of
called
quick
developers
staged
less
than
for
JavaScript,
and
you
know,
our
love
of
proposals
is
pretty
simple
slide.
That
kind
of
demonstrates
folks.
C
F
C
C
B
E
C
C
Cost
to
kind
of
sum
of
the
four
sides
that
we
made
even
in
with
good
intentions
and
anything
for
me,
you
know
thinking
about
this
problem.
It's
I've
learned
it
like
this
is
a
pretty
multifaceted
problem
and
multifaceted
means.
This
is
something
that
touches
every
single
link
element
of
our
distribution
pipeline.
It
starts
all
the
way
like
it
starts.
F
C
C
C
C
C
B
C
H
C
C
Starts
here
right,
the
front-end
communities,
Ted,
hi
and
p.m.
hours
dead,
no
more
tweets
right.
So
for
better
or
worst,
you
know,
we
hijacked
your
hijacked,
our
ecosystem,
for
for
lots
of
good
reasons
too,
and
so
I
think
starting
here
for
me,
is
actually
a
very
important
important
first
step
in
kind
of
like
understanding
manners
in
the
landscape
and
better
understanding
what
place.
What's
what
me
to
do
so
we're
gonna
be
good,
facilitated
discussion.
Next,
we're
all
I
want.
Everybody
here
to
do
is
kind
of
think.
A.
E
F
E
F
C
C
C
E
B
C
E
B
C
B
C
C
C
C
F
D
Number
points
about
Fred,
spyler
fatigue.
Learning
curve
is
hard
speciality
of
building
projects
that
require
just
training.
The
most
challenging
bundler
fatigue
is
also
hard
to
debug
their
problems
and
happen
in
one
year.
Updating
any
dependency
committee
or
seeing
any
changes
in
their
problems
are
not
10x
because
you
get
information.
D
Another
interesting
point
is
like
when,
when
big
big
websites
have
multiple
applications
like
single
page
application,
so
search
from
Sandy
me
oldest
of
them,
you
have
you
know
n
level
complexity
hold
of
different
packages,
I'm
doing
the
same
to
me
and
that
affects
the
user
experience
in
terms
of
constraints
or
requirements.
We
kept
interesting
ones.
The
platform
in
the.
D
G
Like
I
said,
we
actually
reject
that
premise.
We
believe
transpose
very
good
the
number
of
things
doing
it:
code
bloat
and
the
reasons
why
we
actually
transfer
there's
some
difficult
age
cases.
We
have
these
in
black
script
and
big
holes
kind
of
transport
to
an
exact
ocean
mode,
because
the
enterprise
with
very
strict
eating.
We
do
that
latest
version,
but
you
get
one
goes
from
the
latest
version
because
that's
all
we
get
so
as
a
whole.
We
grieve
the
minimalist
approach.
I
think
is
going
out,
but.
C
C
H
H
Babel
we
decided
is
both
a
problem
and
the
solution.
The
library
maintains
among
us
are
very
happy
that
we
have
battle
to
allow
us
to
address
that
compact
with
earlier
versions
of
node.
But
when
we
look
at
the
writer
drumstick
onions,
we
find
that
people
often
have
to
change
that
they
inherited
or
perhaps
set.
E
H
H
F
Would
so
I
think
we
kind
of
bashed
on
this
table
and
it
really
just
comes
down
to
the
number
number
carcasses?
Most
people
don't
get
the
time
to
understand
the
code
as
a
pilot
to
write
and
then
end
up
with
a
number
of
issues
when
they
need
to
solve
functional
issues.
Some
of
the
other
machines
is
when
you
have
multiple
libraries
that
are
32
transpiling,
that
use
competing
polyfills.
F
A
G
A
C
Fantastic
first
of
all,
thank
you.
Thank
you.
Thank
you.
This
was
an
exercise
trying
to
understand.
Take
a
snapshot
of
the
landscape,
drive
requirements,
get
constraints,
understand
where
people
disagree
to
understand
where
they
agree.
So
then
I
can
kind
of
Shepherd
this
forward
throughout
the
community.
Instead,
what's
next,
how
do
we
keep
this
conversation
going
I'll
be
here
a
day
to
this
data
set
will
be
published.
We
have
lots
of
Holly
conversations
tomorrow.
If
folks
are
inspired,
like
you
know,
unconference
session,
or
what
a.
C
C
A
little
bit
been
an
informal
initiative
already
like
today,
like
literally
like
or
just
created,
and
to
basically
solve
this
problems.
It
was
an
independent
JavaScript
package
distribution.
Community
group,
sole
focus,
is
to
drive
solution
and
figure
out
how
how
we
can
solve
this
problem
throughout
our
ecosystem.
C
Can
all
and
I
kind
of
this
is
a
huge
problem
right,
create
massive
problem,
we're
unfurling
ourselves
from
all
this
kind
of
complex
technical
debt,
but
this
with
this
a
quote:
never
doubt
that
a
small
group
of
citizen
of
concerns
the
distance
can
change
the
world.
Indeed,
it
is
the
only
thing
that
ever
has
so.
Thank
you
for
your
time.