►
From YouTube: Node.js Everywhere - Node.js Live London
Description
Mikeal Rogers discusses the growth of Node.js and the direction he predicts that it is heading.
A
Hey
everybody
how's
it
going.
I
need
to
turn
the
notifications
off
on
my
watch
or
I'll
be
still
and
know
everybody.
Okay,
so
welcome
everybody!
I'm
glad
that
you
got
to
see
the
the
nice
changeover
of
the
laptops,
it's
sort
of
a
ritual.
It's
really
nice,
okay,
I'm
going
to
talk
about
code,
how
node
is
doing
how
it
spread
and
how
we've
come
to
think
about
node
at
the
node
foundation,
as
we've
tried
to
broaden
our
view
of
what's
going
on
so
node
objectively
by
any
criteria.
A
Right
now
is
the
fastest
growing
platform
in
open
source
in
the
world,
so
we're
not
the
biggest
yet,
but
we
are
definitely
growing
faster
than
anybody
else
by
any
measure,
which
means
that
eventually,
we
actually
will
be
the
largest
platform
in
the
world.
What
does
that
mean?
There's
a
couple
different
metrics
that
you
can
look
at
this
is
module
counts.
Obviously
we
have
an
amazing
packaging
system
and
a
lot
of
great
modules
actually
hates
this,
oh,
and
also
it's
old.
A
So
actually
it's
just
like,
like
oh
man,
no
we're
way
about
3000
thousand
now
yeah
yeah.
So
this
is
like
you
know,
and
NPM
is
not
happy
with
my
slide.
I'm
sorry,
but
but
we
are
over
twice
as
large
as
the
next
ecosystem
down
in
terms
of
package
count
and
the
more
impressive
thing
actually
is
that
if
you,
if
you
don't
look
at
a
graph
like
this,
that's
an
absolute
number.
A
But
if
you
look
at
growth
in
terms
of
percentage
growth
quarter
over
quarter
or
year
over
year,
we're
still
growing
faster
than
actually
every
other
ecosystem
in
the
world
as
well.
So
our
lead
is
continuing
to
increase
over
everybody
by
any
measure
in
terms
of
in
terms
of
open
source
packaging
is
my
thinking
that
I'm
working
there
we
go
okay,
so
this
is
probably
old
too,
and
actually
I
gave
you
some
about
in
a
second,
but
more
than
400
packages
are
published
every
day.
A
That's
not
updates
two
packages,
that's
new
packages
arrived
in
the
ecosystem
every
day,
and
this
is
really
important
for
people
that,
like
don't
want
to
write
all
of
their
code
from
scratch.
People
that
just
want
to
solve
problems
with
technology
which
turns
out
to
be
the
majority,
get
people
that
want
to
write
code
or
people
that
want
to
solve
a
problem.
They
don't
want
to
build
out
an
entire
new
framework
in
an
entirety
library,
so
the
the
larger
and
more
cohesive
ecosystem
that
we
have.
The
better
node
has
around
4.5
million
users.
A
Now
that's
estimated,
we
have
a
really
complex
model
that
we
shove
a
lot
of
enough
person
to
to
try
to
figure
this
out.
But
the
important
thing
is
that
we're
consistently
growing
at
one
hundred
percent
year-over-year,
which
means
that
we
double
every
year
we've
doubled
every
year
for
four
years
and
that
rate
isn't
slowing
down.
A
There's
no
signs
of
it's
starting
to
level
out
anytime
soon,
which
means
that
you
know
in
a
little
over
a
year,
then
from
now
we'll
be
over
10
million
users,
and
you
know
in
a
couple
years
that
would
make
us
the
number
one
platform
in
the
world
it'll
make
us
longer
than
Java
and.net.
Who
were
really
the
only
people
we're
competing
with
this
point.
So
why
is
no
growing
like
this
and
we
started
the
foundation?
A
We
we
really
wanted
to
broaden
the
view
of
what
node
was
and
why
it
was
successful
up
until
that
point,
we'd
really
thought
about
note.
As
a
back-end
technology,
you
know
the
people
that
had
funded
node
and
had
led
the
effort
were
mostly
back
in
people,
and
so
we,
we
kind
of
had
a
bit
of
a
blind
spot
to
what
was
going
on
outside
it.
Back-End
technology
as
a
node
and
after
we
started
the
foundation
and
really
started
to
break
down.
Why
is
node
successful?
Why
is
it
growing
so
much
faster?
A
We
initially
had
put
things
into
buckets.
We
looked
at
verticals
right,
so
you
have
mobile
you.
You
have
people
doing
iot
stuff
people
doing
back
end
and
that
actually
didn't
seem
to
tell
the
right
story
to
us,
because
it
was
really
the
diffusion
of
all
these
things
together.
So
what
we
found
was
that
if
you
look
at
what
you
need
to
do,
if
you
want
to
build
a
modern
application
right,
you
want
to
solve
a
problem.
You
want
to
build
a
new
application.
What
is
the
world
that
a
developer
has
to
contend
with?
A
Okay,
so
you
have
a
web
front
end,
because
people
still
use
websites
believe
it
or
not,
I
mean.
Obviously
you
have
a
cloud
back-end
like
everybody
has
a
back-end,
and
you
know
what
that
back
in
looks
like
and
what
the
API
is
is
changing
over
time.
You
have
mobile
and
tablets
in
very
responsive
designs
and
and
outputs
that
you
need
to
worry
about.
You've
got
desktop
like
I
mean
desktop,
is
still
a
thing.
Some
people
still
use
desktop.
A
Applications
like
I
still
use
slack
on
my
desktop
and
I
still
use
it
to
stop
text
editor
its
a
thing.
People
use
it.
You
have
this
entire
new
class
of
API
services
that
you're
connecting
to
right.
So
it's
not
just
my
own
back-end
with
all
my
own
infrastructure,
but
also
other
people's
infrastructure.
Other
people's
API
is
that
I'm
trying
to
connect
to,
and
in
case
this
wasn't
complicated
enough
for
everybody.
You
have
IOT
devices,
so
you
have
this.
A
This
whole
other
platform,
where
the
interface
is
different,
where
all
of
the
patterns
are
different
right,
and
so,
if
you
need
to
build
an
application
that
stretches
like
even
half
of
these
things,
much
less
all
of
them.
You
really
need
some
kind
of
connective
tissue
that
allows
you
to
as
a
developer,
have
a
unified
development
environment
have
unified
debug
environment,
at
least
to
the
best
of
your
ability
and
there's
really
no
credible
story
other
than
node
to
actually
tie
all
these
things
together.
A
One
was
you
shouldn't:
do
shell
scripting
things
or
like
scripty
stuff
that
has
like
outputs
like
you,
should
do
that
in
bash
or
whatever,
and
and
like
that
turned
out
to
be
one
of
the
largest
things
that
anybody
ever
did
with
the
code
actually
having
a
unified
language
for
fern
and
tooling
ended
up
being
more
important
than
the
you
know,
annoyance
of
doing
callback
for
for
things
that
are
essentially
just
piped
together.
So
we
have
all
these
great
tools
now
for
compiling
like
front-end
JavaScript
right.
A
We
have
these
lower
level
tools
like
like
Babylonia,
slint
and
last,
and
then
we
had
so
many
tools
that
we
like
started:
inventing
tools
that
oh
I'm
pulling
up
the
stage
that
was
fun
all
right.
Let's
start
that
again,
all
right
there
we
go
so
we
had.
Somebody
tells
me
we
literally
wrote
tools
to
manage
the
tools,
so
we
have
like
tools
to
manage
our
tool
chains,
which
is
kind
of
absurd
to
me,
and
then
you
know,
I
don't
put
in
p.m.
A
scripts
in
here,
because
I'm
not
trying
to
troll
anybody
and
then
and
then
react
is
something
that
really
caught
me
off.
Guard
and
I
think
got
a
lot
of
people
off
guard.
We're
in
that
react
is
a
front-end
framework
right.
It's
it's!
Well,
okay,
I
Ashley's,
going
to
disagree
with
me
and
she's
from
mpm
she's
going
to
represent,
but
we
had
to
the
front
and
framework.
It's
it's
comparable
to
say,
like
you
know
the
first
version
of
angular
or
dojo
or
frameworks
that
we're
used
to
think
about
on
the
front
end,
but
it's
actually.
A
The
first
framework
that
is
not
a
script,
include
before
a
bunch
of
your
client
javascript
in
the
browser
it's
actually
implemented
as
a
compile
chain,
rather
than
anything
else,
which
is
somewhat
unique
and
and
I
think
it's
kind
of
a
one
directional
shift
in
front-end
framework,
so
we're
now
we're
actually
not
going
to
have
a
lot
of
front-end
frameworks
that
we
just
include.
Script
includes
because
there's
so
much
more
power
to
be
had,
as
we've
seen
with
react
and
I.
A
Think
that
that's
just
really
just
the
beginning,
regardless
of
what
you
think
of
react,
so
obviously
no
just
kind
of
change.
The
way
that
we
do
web
front-ends.
Let's
look
at
something
else,
looks
look
at
mobile
development,
so
Apache
Cordova
basically
takes
the
entire
know
the
ecosystem.
It
leverages
it
into
a
tool
chain
that
can
allow
you
to
write
basically
native
web
application
for
lack
of
a
better
term
for
mobile,
and
it
I
think
it
was
a
like.
Sixty
percent
of
the
top
100
applications
in
the
Android
and
iOS
stores
are
built
on
this
technology.
A
You
don't
actually
know
when
you're
in
a
webview
a
lot
of
the
time
on
mobile,
a
lot
of
really
really
popular
applications
without
anybody,
knowing
it
or
actually
built
on
Cordova
and
and
that's
because
being
able
to
leverage
the
node
ecosystem
being
a
lover.
Web
technology
just
has
a
lot
of
advantages.
If
you're
trying
to
build
a
cross-platform
application,
there's
really
nothing
but
the
web.
That's
ever
been
successful
at
doing
cross-platform.
A
So,
let's,
let's
move
on
again
and
I.
Think
now
we're
going
to
talk
about
desktop
yeah,
so
never
thought
this
would
happen.
It
turns
out
the
desktop
application.
I
mean
I've
known
the
disciplic.
Asians
are
popular
for
a
long
time
if
you've
worked
at
any
bigger
company.
You
know
that,
like
your
usage
of
desktop
applications
is
absurdly
high
and
you're
like
who
are
these
people
this
to
use
a
desktop
application?
And
then
you
look
at
your
desktop.
A
You
have
like
20
applications
open
and
you're,
like
oh
good,
some
of
the
person,
but
electron
was
built
by
github
in
order
to
build
the
atom
editor
right.
So
it's
it's
just
a
it's.
It's
honestly,
the
most
enjoyable
development
environment
in
the
whole
world
because,
like
the
annoying
things
about
web
development,
are
like
cross-platform
issues
and,
like
you
know,
security
issues
so
like,
let's
just
like
throw
out
the
security
model
and
just
only
have
one
version
of
Chrome
you
ever
to
write
to
and
also
just
like,
require
node
modules.
That's
electron!
It's
brilliant!
A
I
love
it!
It's
my
favorite
thing,
but
it's
it
essentially
just
like
brings
the
entire
node
ecosystem
in
all
of
this
web
technologies
to
every
major
desktop
platform
and
a
lot
of
applications
using
today
are
built
in
this,
like
it
is
insanely
surprising,
actually
how
many
applications
have
been
built
into
the
short
amount
of
time.
I
mean
the
slack
desktop
application.
I
use
every
day
is
built
in
this.
Not
only
add
the
atom
editor,
but
Microsoft
Visual
Studio
code.
A
Editor
is
built
on
electron,
like
I
did
not
think
10
years
ago
that
I
would
say,
Microsoft
new
visual
studio
is
built
on
web
technologies
and,
and
you
know,
an
open-source
JavaScript
framework.
That
would
be
crazy,
but
it's
it's
happened
and,
and
if
you,
if
you
really
don't
feel
like
this,
has
come
full
circle
yet
like
the
brave
browser
is
built
on
electron
like
we,
we
took
the
language
from
the
web
and
built
note
on
it
and
then
brave
when
a
browser
on
top.
No,
it's
it's
awesome.
A
So
a
lot
of
great
things
happening
really.
I
really
encourage
everybody
to
check
this
out.
It's
like
it's
actually
more
fun
and
kind
of
easier
than
regular
web
development.
Surprisingly,
it's
a
great
way
to
just
like
try
out
node
and
try
out
ideas
super
fun,
but
this
is
really
changing.
Desktop
development
to
like
everyday
new
applications
that
I'm
running
get
replaced
by
electron
applications.
I
just
got
rid
of
I
term
actually
for
hyper
term,
which
is
this
new
terminal.
A
A
There
is
not
a
cloud
platform
where
node
is
not
one
of
the
primary
supported
environment
right
so
you're,
never
a
second-class
citizen
running
node
on
anybody's
public
cloud,
but
you
know
even
further
than
that
and
we'll
get
in
an
earlier
actually
I'm
getting
ahead
of
myself.
So
let's
talk
a
little
bit
about
a
team
so
from
very
early
on.
A
No,
it
had
a
great
robotics
community.
It's
like
hands
up
if
you're
involved
in
the
node
BOTS
community
at
all
I
have
any
experience
in
the
mid.
Both
community
hands
up
just
a
couple:
people
really
it's
in
it's
honestly,
like
the
most
fun
community
in
ever
like
they're,
super
nice,
super
fun,
doing
really
really
cool
stuff.
So
there's
been
a
hobbyist
community
for
at
least
like
six
years,
just
doing
node,
robotic
stuff
and
this
framework
that
it's
kind
of
sitting
below
a
lot
of
it.
A
So
the
low-power
and
high-power
the
tehsil
to
the
BeagleBone.
Everybody
is
running
node
on
device.
So,
like
these
chipsets,
you
know
today
they
are
for
developers
to
go
out
and
build
new
IOT
devices,
but
in
a
couple
years
the
cost
of
these
come
down
so
that
they
end
up
in
your
light
switches
and
they
end
up
in
in
all
of
the
little
IOT
devices.
Do
you
have
in
your
house.
A
So
this
means
that
the
entire
node
platform
will
be
accessible
to
developers
on
those
devices
right,
and
so
this
solves
a
lot
of
the
issues
like
if
you
really
heavily
involved
in
EIT
world
right
now.
One
of
the
problems
is
a
complete
lack
of
standardization,
around
ap
is
or
data
or
anything,
and
the
fact
that
now,
if
you
implement
a
protocol
or
implement
some
idea
in
the
node
ecosystem,
you
can
actually
get
in
all
the
devices
is
going
to
be
really
empowering
and
and
I
think
that
this
is
really
going
to
kind
of
shift.
A
Some
of
the
the
way
in
which
we're
trying
to
develop
IOT
in
the
future,
so
last
one
here
is
AP
is
eight
ap
eyes
and
micro
services
because
more
buzz
words,
because
we
need
them.
So
a
P
eyes
are
on
the
rise,
like
we
know
that
the
way
the
developers
consume
infrastructure
has
changed,
they
consume
it
like
a
product.
It
can
seem
it
like
an
API
rather
than
a
hey.
Here's,
a
hunk
of
technology
on
our
cloud
figure
it
out.
You
know
everything
is
getting
more
amateur
eyes,
and
so
we
have
this
resume.
A
Is
that
are
happening?
Obviously,
a
lot
of
this
is
fueled
by
node
notice,
accessible
like
like
very
good
at
marshaling
between
a
lot
of
different
ap
is,
if
your
application
is
doing
that,
but
then
recently
we
have
this
new
suite
of
server
lyst
technologies
right.
So
first
it
was
lambda
and
then
everybody
had
to
do
one.
So
everybody
did
one,
and
in
all
of
these
notice
is
not
only.
A
You
know
well
supported
up
front,
but
in
some
of
them
is
the
only
available
language
for
these
server
list
technologies,
and
so
part
of
this
is
that
in
this
new
landscape,
where
you're,
not
you
don't
even
know
how
many
of
your
processes
are
running
and
they're
just
coming
up
and
coming
down
really
quickly.
You
need
a
really
fast
start
time
and
need
to
be
incredibly
efficient
at
the
process
level.
A
The
history
of
Noda
is
is
someone
interesting,
but
we've
always
had
a
huge
focus
on
being
very,
very
fast
and
very
efficient
ryan
used
to
say
back
in
2009.
That
performance
is
a
feature.
It's
a
core
feature
of
node,
because
we've
always
focused
on
non-blocking
I/o,
that
meant
being
efficient
in
a
in
a
single
process
environment,
and
we
got
a
lot
of
from
people,
especially
in
the
Java
world,
about
like
how
we
weren't,
you
know
scaling
out
to
multiple.
A
You
know:
processors
ended
it
up
as
this
world
is
built
out
and
as
the
micro
service
world
is
built
out,
the
addressable
space
for
your
application
is
actually
gotten
smaller.
It's
now
I
a
slice
of
one
process
inside
of
a
container
inside
of
a
vm
somewhere
right
and
in
that
environment.
All
of
this
work
that
we've
done
for
years
to
be
really
efficient
for
processes
really
paid
off
and
so
we're
a
natural
fit
for
these
new
server
lists
and
Microsoft
technologies.
A
So
when
you
put
all
this
to
get
it,
no
one
of
these
is:
why
does
successful?
It's
actually
all
of
them
together,
right,
like
when
people
adopt
note
in
IOT
that
drives
cloud
adoption
when
people
like
start
adopting
it
in
the
cloud,
it
actually
drives
like
front
end
and
desktop
adoption,
and
so
because
we're
a
general
platform,
because
we've
done
so
much
work
to
be
good
in
all
these
different
areas.
A
A
It's
that
node
has
this
history
from
the
web
of
being
very
easy
to
use
and
and
amateur
izing
the
spaces
at
it's
in
so
when
we,
you
know,
are
supported
in
an
IOT
platform,
we
actually
make
it
easier
for
people
to
program
that
IOT
platform
and
we
make
that
IOT
platform
accessible
to
an
entire
generation
of
developers
that
wouldn't
have
been
able
to
get
involved
before.
So
that's
really
exciting
and
that's
not--
everywhere,
and
that's
my
talk,
and
so
thank
you.