►
From YouTube: YUI Open RoundTable - Alberto Chan and modown
Description
Discussion of all things YUI!
A
All
right,
everybody
welcome
to
the
next
yy
open
round
table
today's
thursday
january
30th
2014,
and
we
have
two
folks
here
to
give
some
talks
on
various
yui
related
things.
Jeff
clarence
who's
here
quite
often,
and
alberto
chan,
who's
from
the
would
it
be.
The
mojito
team
would
be
the
mo
down
team,
both
both
yeah,
because.
A
D
D
D
D
That's
just
the
existing
one,
and
always
this
flame
was
debate
so
yeah,
so
we've
been
there
and
we
just
want
to
avoid
all
this.
So
what
so
as
a
result
of
this,
so
this
causes
us
to
to
refocus
our
motivations
in
terms
of
really.
What
we
want
to
do
is
solve
big
problems
for
everybody.
So
whenever
someone
is
building
an
application,
there
are
very
common
issues
that
you
have
to
solve.
So
we
want
to
address
those.
D
You
know
to
use
the
unix
philosophy
where
you
build
this
very
small
tool.
That
does
one
thing
very
specifically,
but
very
good
at
it,
but
the
ability
to
take
these
different
components
put
them
together
and
build
something
meaningful
that
addresses
your
problems
and
ultimately,
what
we
want
to
do
is
have
a
set
of
components,
so
these
components
would
be
npm
packages.
D
And
yeah,
so
so
that
that's
that's
what
we
we
want
to
achieve
with
lower
down
so
modern
is
so
white
is
not
well
done.
Without
is
not
it's
not
a
product,
it's
not
a
a
framework.
It's
it's
more,
like
a
collection
of
libraries
that
falls
under
the
you
know
that
umbrella
name.
So
there's
no
there's
no
component
called
noidam.
D
D
A
talk
about
express
map
today,
yeah,
it's
expressed
now
so
so
far.
What
we
have
in
in
in
the
modern
umbrella
is
a
set
of
packages
for
express.
So
if
you
are
building
a
javascript
based
application,
most
likely
you're
using
express,
so
we
have
about,
let's
say
like
five
to
eight
packages
that
is
very
specific
to
express
and
they
solve
very,
very
specific
problems
so
just
to
give
an
overview.
So
we
have
packages
that
allows
you
to
serialize.
D
Data
from
your
self
environment.
To
your
browser,
so
express
state
is,
is,
is
the
package
that
you
would
like
to
use
if
you
want
that
functionality?
So
what
usually
people
use
this
package
for
is
for
similarizing
rods?
For
example,
like
you
know,
if
you
have
an
express
app,
so
you
have
your
browser
defined
on
server,
but
you
want
to
somehow
reuse
this
on
the
client
to
drive
the
the
responsive
behavior
of
the
application.
D
So
you
don't
want
to
duplicate
those
information,
so
you
would
define
it
once
on
the
server
package.
It
serialize
it
ship
it
to
the
client
and
then
reply
it
will
be
available
for
you
to
to
restore
and
use
it.
As
is
we
have
the
the
expressway
ui
package
that
allows
you
to
ship
your
why
white,
ui
configuration
and
load
the
metadata
to
your
application
on
the
client.
D
So,
instead
of
having
a
bunch
of
very
specific
javascript
imports
in
your
page,
you
would
use
that
specific
extension
on
the
server
to
allows
you
to
allow
the
component
to
pause.
Your
application
bundle
retrieve.
All
the
wi-fi
modules
generate
the
method
to
load
the
data
data
and
then
serve
it
through
for
your
through
express.
Can
you
can
you
have
your
metadata
referred.
D
Terms
of
metadata,
I'm
referring
to
the
yui
loader
metadata.
So
if
you
have
a
bunch
of
modules
that
are
packaged
as
part
of
your
application
on
server,
you
need
to
tell
the
yui
loader
on
the
client
which
which
module
to
fetch
so
as
part
of
that
process,
that
specific
module
will
direct
those
data
for
you,
based
on
the
modules
that
are
available
in
your
application.
E
D
E
D
D
E
D
Other
related
express
related
packages,
so
we
have
express
map
express,
slash,
express
annotations
view.
So
all
these
little
things
solve
very
specific
problems
and
and
those
addresses
and
then
the
the
last
big
component,
that
is
part
of
the
modern
pro
umbrella
set
of
components
is,
is
the
locator
so
so
located
as
a
terrible
name
for
it.
So
so
so
what
you
want
to
visualize
the
locator?
D
What
it
does
is
it's,
it's
a
runtime,
it's
a
build,
it's
a
built
time
and
a
runtime
component
at
the
same
time.
So
the
build
time
part
of
it
is
as
your
application
boots
up.
It
will
pause
your
application
bundle
directory.
It
will
pause
your
application
directory
and
look
for
a
very
specific
modules
that
you
define
as
part
of
a
rule
set.
So
you
can
tell
this
confirm
that
modules
that
is
part
of
the
views
directory
or
my
views,
and
they
should
be,
they
should
be
associated
with
certain
metadata.
D
So
you
can
all
configure
this
through
the
rule
set.
So
what
this
analysis,
I
think
very
highly.
What
this
allows
you
to
do
is
to
not
have
to
worry
about
how
you
structure
your
applications
from
a
module
perspective,
but
to
logically
arrange
your
your
modules
that
fills
fits
better
your
application
structure.
So,
typically,
what
you
would
do
is
you
would
have
like
a
views
and
models
and
a
controller
and
a
template,
and
maybe
some
just
javascript
code
that
is
helpers
and
things
like
that.
D
So
what
this
means
is,
if
you
have
a
handlebar
template
in
your
application
directory,
so
with
the
combination
of
the
locator
component
and
its
corresponding
plugin,
it
will
load
the
handlebars
determine
that
it
is
a
handball.
Template
then
wrap
it
up
inside
a
yui
module
register
it
with
by
template
so
that
it
is
accessible
in
both
server
and
current
environment.
Without
you
having
to
know,
you
know
where
the
template
is
coming
from,
is
it
located
industry
or
by
directory?
D
So
all
you
have
to
do
is
look
up
the
template
based
on
the
name
and
and
be
able
to
have
access
to
it,
and
the
name
can
be
whatever
you
want,
and
the
name
would
be.
It
would
be
a
combination
of
the
the
name
of
the
template,
obviously,
together
with
the
the
the
name
of
your
application,
so
which
is
typically,
you
know
the
name
value
that
you
have
in
your
package
of
json,
so
just
in
case.
So
we
have
this.
I
don't
want
to
talk
about
bundles
because
it
tends
to
be
very
confusing.
C
D
Okay
yeah.
So
if
you
look
at
the
my
yahoo
page,
that
has
a
big
frame
and
then
lots
of
little
applets,
so
potentially
each
other's
outlets
could
could
be
a.
I
don't
want
to
use
module
because
it's
very
confusing
like
we
refer
this
as
done
as
a
bundle.
So
it's
an
application,
it's
a
bundle.
So
if
bundle
is
oh
yeah,
okay,
so
the
bundle
is
is,
is
a
grouping
of
assets
that
can
be
can
be
executed
on
its
own
to.
D
All
right,
so
in
the
case
of
of
my
yahoo,
that
class
is
referring
to
so
each
of
those
apps
could
potentially
be
a
bundle
right.
So,
as
you
deploy
this
application
that
you
have
here,
you
could
potentially
have
multiple
bundles
in
your
application,
so
to
be
able
to
differentiate
those
inside
metadata.
We
have
to
be
able
to
name
space
each
bundle
as
a
separate.
I
guess
what
we
call
like
the
yui
group.
D
E
C
E
C
E
Right
that
is
a
bundle,
so
then
going
back
to
what
you
guys
are
I'm
just
trying
to
get
my
head
around
this.
So
how
does
the
bundle
in
the
locator
like?
Where
does
that
tie
in
again,
so
you
were
saying
that
for
the
locator,
the
names
itself
is
a
combination
of
the
bundle
name
yeah
and
then
the
file
name
and
the
photo.
E
D
D
You
can
query
or
request
for
specific
asset
types,
as
in
like
I
want
to
retrieve
all
my
models
I
want
to
which
people
might
use,
or
I
want
to
run
my
controllers,
so
you
can
do
so
without
having
to
be
aware
of
where
it
is
located
on
the
phone
system,
because
everything
after
once
that
browsing
face,
has
done
it's
all.
That
metadata
is
sitting
in
your
directory
in
memory.
So
for
you
to
access
so
on
its
own.
That
component,
the
locator
component,
doesn't
do
very
much.
D
I
mean
it
does
a
lot,
but
it
doesn't
do
very
much
so
you
need
the
help
of
those
plugins.
That
does
very
specific
things.
So,
every
time,
for
example,
if
you
have
a
locator,
handlebar
plugin
every
time,
locator
is
encounters
a
file,
that's
defined
as
a
handlebar
template.
It
will
execute
the
plugin
on
that
and
then
the
plugin
will
do
its
thing,
independent
of
whatever
you
know,
independent
of
what
the
cable.
E
C
So
so
yeah,
I
think
a
better
example
of
this
might
actually
be
with
like
css
and
locator.
So
with
css,
for
instance,
like
you
might
have
like
people
putting
their
like
style
sheets
in
like
a
bunch
of
different
directories
with
different
names.
So,
like
one,
you
might
name
your
css
directory
like
css,
another
person
might
name
their
css
directory
like
style
sheets,
or
something
like
that.
C
Working
on
like
that,
twitter,
applet
and
another
person
is
working
on
that
news.
Applet,
like
they
don't
know
like
what
the
other
person
is
doing
and
the
idea
behind
locators
like
normalize,
all
that
and
then,
when
you're
ready
to
deploy
your
application.
You
basically
it
combines
all
that
css
and
even
does
like
pre-processing
on
it.
So
if
you're,
using
like
a
css
pre-processor
like
sas
or
less,
it
doesn't
matter
like
what
you
use,
it'll
combine
them
all
together
and
you
can
all
access
it.
The
same
way.
D
A
D
Ease
a
difference
between
the
build
time
process
and
the
runtime
process,
so
the
built-in
process
is
where
the
locator
is
actually
physically
going
inside
your
application
directory
and
reading
every
single
file
asset,
and
it
does
so
recursively
so
that
it
knows.
Where
is
what?
But
the
process
of
the
application
aquarium
for
all
controllers
for
all
models?
That's
a
runtime
component!
E
Yeah,
that
makes
a
bit
more
sense
now.
What
I
was
looking
at
is
the
just
the
locator
read
me
on,
and
I
I
I
I
didn't
understand
the
so
I
understand
you
have
to
declare
this
locator
rulesets.js
javascript
file,
but
inside
it
says,
inside
of
your
app.js.
You
have
to
do
this
like
locator.parse
bundle
and
then
like
it
does
like
it
loops
over
resources.templates.
So
I
wasn't
sure
about
like
what
the
what
like
what
that
setup
is
like
like.
E
Is
that
something
that's
like
copy-pastable
or
is
that
like
I'm,
not
not
sure
exactly
what
that
logic
is
doing
so
right
now?
How
locator
works
is
that
it
runs
right
before
your
app
starts
so
right
that
makes
sense
yeah.
So
that
makes
it
makes
sense
why
it's
an
app.js,
I'm
just
saying
like
the
specific
lines
there
I
can
see
like
located
on
parse
bundle.
Now
I
kind
of
know
what
bundles
are.
E
D
D
Right
as
part
of
your,
so
the
get
rid
bundle
would
mean
get
the
main
bundle.
But
if
you
actually
are
accessing
some
resource,
which
is
part
of
the
sub
bundle,
you
can
also
specify
them
by
name
so
that
you
have
this
option
right.
So
it's
just
a
way
to
determine
which
bundle
so
which
bundle
to
use
to
just
execute
your
query,
and
in
this
case
it's
saying
get
resources.
It
will
just
return
everything
because
you
didn't
say
what
kind
of
resources
you
want
right.
So
you'll
just
return
everything
that's
in
memory.
D
E
E
D
B
E
D
A
So
I
have
a
question
about
about
this.
Just
in
terms
of
the
suite
of
10
plus
things
yeah
in
terms
of
versioning,
are
they
all
versioning
at
the
same
time
yeah?
Are
they
all
going
to
be
like
like
what
they're
at
least
a
couple?
Is
there
anything
any
sort
of
commonalities
that
keep
them
from?
You
know.
D
They
have
to
like
work
together
or
so
so
far
we've
been
pretty
very
much
independent
of
each
other,
so
there
are
extensions
like,
for
example,
express
yui,
which
is
you
know,
one
obvious
responsibility
to
generate
your
configuration,
but
it
does
also
other
things.
So
there
are
times
where
you
know
we're
supporting
a
new
feature
that
we
have
to
depend
on
yui
first
to
release
before
we
can
actually
release
that
functionality.
D
So
you
might
have
code
dependencies
like
like
like
that,
but
like
so
far
each
and
every
single
one
of
those
components
have
been
pretty
much
in
panel,
so
in
the
case
of
locator,
if
we
make
a
phenomenal
a
chain
that
is
not
that
way
compatible,
it
might
be
that
you
need
to
go
and
update
your
plugin
to
work
with
that.
But
but
so
far
it's
been
pretty
much
very
juicy
couple.
D
A
But
I
really
like
the
idea
of
like
this
is
like
one
of
the
things
that
that
you
kind
of
it's
implied
is
that
this
is
a
different
methodology
than
from
say
old
yui,
where
you've
got
like
this
model
of
the
thing,
and
it
can
it's
like.
You
have
to
get
all
of
it
or
nothing,
or
this
is
more
loosely
coupled
and
sort
of
a
la
carte
you
haven't.
Can
you
talk
a
little
bit
about
why.
B
D
Use
promises:
it's
like
an
embarrassment
of
choice.
You
just
don't
know
which
one
to
use
right
and
that's
a
good
thing
if
you
know
what
you're
doing,
maybe
not
so
good,
if
you
know,
if
you're
not
too
sure
which
one
to
use
but
but
generally
speaking,
the
trend
has
been
towards
micro,
libraries
and,
and
that's
what
we
want
to
do
so.
The
hope
is,
instead
of
us
being
that
building
the
next
mojito.
C
D
F
But
if
you
like
library,
though
I
like
framework
at
the
moment,
so
I
think
it's
pretty
interesting
what
what
else
could
do
can
do
to
do
and
yeah
I'm
following
it
and
I
I
would
also
like
to
know
how
to
how
to
dive
in
what
is
the
best
way
to
to
learn
a
bit
more
because
I
have
the
feeling
children
has
seen
more
than
I
have
seen,
perhaps
looking
by
the
code
on
npm
of
the
current
modems
that
are
available.
I
think
where
do
you
start
where
you've
started
learning
about
yeah.
D
Yeah,
so
that's
a
question:
that's
very
popular
these
days,
so
that's
still
in
progress,
so
we
don't
have
a
essential
place
for
people
to
go
regarding
documentation.
So
the
best
place
to
look
at
is
to
start
with
is
on
npm
registry
and
just
do
a
search
for
no
down.
So
what
one
thing
that
we've
been
trying
to
do
is
in
every
single
in
every
obvious
of
these
packages,
we've
we've
been
trying
to
include
examples
for
people
to
to
help
people
learn
about
those
components
so
yeah.
E
F
So
will
there
be
a
general
place
for
the
moderns
of
yahoo,
on
a
some
library
or
on
an
umbrella,
or
can
anyone
who
wants
just
write
a
mode
on
and
put
it
on,
npm
and
say
well,
this
is
my
modern
and
it's
one
of
the
many
moderns
that
will
be
available
in
the
future.
How
how
is
this
gonna
go
to
be
managed.
G
C
Thanks,
I
guess
to
tie
them
all
together,
like
basically
like
most
of
the
mo
down,
like
modules,
are
on
npm
they're
focused
on,
like
the
idea
of
like
being
able
to
like
do
server,
rendering
of
like
basically
like
single
page
applications
like
what
we're
working
on.
So
I
think
that's
like
that's
one
of
the
things
that
like
ties
them
together,
but
there's
there's
also
like
the
parts
of
like
locator
and
all
of
that.
So.
D
Yeah
so
marcos,
I
know
you're
a
big
mojito
fan
so
just
want
to
let
you
know
also
that
in
in
mojito
we
have
this.
I
don't
know
if
you
familiar
with
the
the
next
branch,
that's
on
our
repo,
so
some
of
the
work
that
we've
been
doing
is
trying
to
integrate
back
some
of
these
no
down
work
that
have
been
that
has
been
done
into
mojito.
So
so
far
we
are
using.
E
D
Free
lowdown
packages
in
mojito,
so
we're
using
express
map,
express
state
and
express
annotations.
So
all
these
is
helping
us
bring
the
the
integration
with
express,
more
more
more
natively,
so
as
in
more
tech
integrated
with
express
and
also
removing
a
lot
of
code
that
you
know
was
duplicated
across
the
code
base
that
these
modern
components
address
very
succinctly
and
very
concisely.
D
F
D
So
so
again,
so
I
want
to
re-emphasize
so
emergent
is
it's
a
very
high
level
concept
of
a
of
a
bundle
that
contains
code
contains
templates,
contains
css
and
everything
else,
and
these
modules
they
need
a
like
a
runtime
like
a
mojito
runtime
engine
to
execute
right.
So
that's
a
high
level
construct.
D
So
what
we're
talking
here
about
no
down
is
like
the
really
low
level
building
blocks
to
to
help
you
build
your
application
so
so
like
like
yeah,
so
a
module
will
never
be
replaced
by
by
moda,
but
that's
not
the
goal
of
node
hunter.
To
do
so.
We're
not
trying
to
replace
them.
It
concept
of
launcher
all
right,
so
the
guts
of
mojito
might
be
replaced
with
noidam,
but
as
a
mojito
developer,
you
will
structure.
Your
modules
is,
should
not
be
affected,
so
remains
the
same.
D
A
C
E
So
I
had
a
question
about
express
view.
I
I'm
pretty
familiar
with
the
other,
express
you
know
plugins.
I
guess
yeah
I've
never
really
used
express
view,
and
I
was
wondering
if
anyone
could
like.
I
was
just
trying
to
read
through
the
documentation
again
but
again
like
if
someone
could
give
me
like
a
real
world
use
case
of
when
I
should
be
using
this
or
like
what
what
it's
useful
for.
I
don't
know
if
you
guys
worked
on
it
or
not,
but
yeah,
okay.
C
Wanna
go
ahead
all
right,
so
kari
actually
has
a
pretty
good,
like
blog
post
about
like
when
expressview
should
be
used.
So
the
idea
is
that
you
don't
want
to
like
link
your
templates
directly
to
the
file
system
like,
for
example,
if
like
people
are
like
working
on
all
sorts
of,
like
templates
and
they're,
all
over
the
place
like
you
might
have
like
templates
that
are
stored,
like
inside
of
the
database,
for
instance,
or
basically
templates
that
you
don't
control
the
idea
with
espresso
it
lets.
C
D
What
express
view
does
it
very
cleverly
overrides
the
lookup
mechanism
within
express
to
load
up
those
with
templates?
So
instead
of
express
going
back
to
the
file
system
and
say
hey,
somebody
is
requesting
for
template
foo,
because
somebody
said
rest
of
render
foo,
so
what
it
will
does
it
will
inject
itself
and
capture
that
call
a
full
thing
and
then
translate
it
into
something
that,
like
you
know,
for
example
like.
E
C
C
Yeah,
like
think
about
the
use
case
like
if
you
like,
again
like
for,
like
the
my
yahoo
example
like,
if
you
have
a
bunch
of
teams
working
on
like
these
separate
like
little
widgets,
then
like
putting
them
all
together.
You
want
to
have
like
a
way
to
manage
that
and
that's
where
expressview
really
comes
in.
E
I
guess
there's
like
a
there's
like
a
slight
difference
right
like
it's,
it's
it's
hard
to.
I
guess
unless
like,
for
example,
if
you
look
at
a
lot
of
like
all
the
mow
down
components,
that
start
with,
like
the
prefix,
express
something
like
express
view,
and
I
guess
locator
to
an
extent
they're
more
like
abstractions
right,
they
make
it
easier
to
work
with
the
underlying
system,
they're
more
like
abstractions,
but
then
some
of
the
other
things
like
express,
slash,
express
state
express
map.
These
are
more
like
helpers
they're.
E
They
they're
like
they're,
like
give
you
like
little
functionality
or
helpers.
So
I
guess
some
of
those
helpers,
I
guess,
would
be
more
useful,
possibly
for
even
smaller
projects,
right
like,
for
example.
Now
when
I'm,
when
I'm
writing,
like
a
node.js
app,
I
always
almost
use
express
state
express
map
express
annotations.
I
haven't
found
a
use
case
for
locator
and
stuff
here,
because
I'm
probably
not
like
making
something
of
that
scale
that
distributed,
but
right
might
be
useful
for
like
to
like
maybe
annotate
them
in
some
way
like
like.
C
E
That's
kind
of
like
I
don't
know
if
that's
a
good
way
to
say
it
but
like,
but
just
like
from
like
from
looking
at,
I
was
like
I
use
express
map.
I
use
express
state.
I
use
express
slash
but,
like
I
don't
use
express
view
like
am
I
like
and
and
like,
is
there
something
there
that
I'm
missing
but
like
now
that
I
know
more,
I'm
like
okay
yeah.
Maybe
it's
not
exactly
for
the
types
of
apps
that
I
built,
but
so.
D
I
think,
like
yeah,
something
to
take
a
step
back.
I
think
the
the
larger
problem
is
as
somebody
who
is
new
to
mowdown.
It
is
very
hard
to
know
you
know
which
one
I
should
use
one
exactly
what
to
use.
So
that's
so
there's
a
lot
of
there's
a
lot
of
work
that
needs
to
be
done
there.
So
that's
definitely
for
sure.
So
it's
one
of
those
I
guess
cons,
of
having
these
little
components
that
are
kind
of
lucy
couple.
E
A
E
I
think
that
would
be
useful
because
I
know,
for
example,
eric
has
photos
near
me
right,
which
is
pretty
much
like
an
app
that
I
think
uses
most
of
these
things,
but
once
you
start
using
a
lot
of
these
things
for
the
average
person
who
just
wants
to
see
how
express
map
works,
they
have
to
go
through
a
lot
of
this
other
stuff
right.
So
I
think
it
helps
to
have
just
simple,
like
little
apps
inside
of
these
each
of
these
repos,
like
just
app.js
and
like
one
template
or
something
yeah,
to
show.
D
D
B
C
And
solved
of
the
things
we're
working
on
is
also
like
taking
this
like
beyond
yui
so
like.
We
want
to
make
sure,
like
these
models,
also
work
with
like
if
you're
not
using
just
yui.
We
want
them
to
work
with,
like
whatever
like
front-end
framework.
You
want
to
use
like
what
alberto
was
saying
before
so
we'll
be
trying
to
make
like.
D
E
A
A
B
D
D
So
having
code
you
would
you
write
once
and
those
can
be
shared
between
certain
clients,
so
you
can
execute
you
know
in
the
browser
or
on
the
server.
The
other
thing
is:
we've
also
been
trying
to
showcase
how
people
can
use
logo
model
to
leverage
our
app
framework
on
the
client.
So
we
do
that
by
leveraging
like
express
state
express
map,
how
we
can
ship
routes,
that's
defined
on
the
server
and
then
being
shipped
to
the
client.
D
A
You
about
that
I
mean
it
always
talks
about
this
kind
of
magic
thing,
but
is
there
any
difference
in
behavior
on
a
mobile
side
of
things
versus
like
a
desktop
because
on
desktop
you
know,
connections
are
cheap.
You
can
send
connections
back
forward,
but
on
mobile
you
know
you
fire
up
that
radio.
You
know
you
kind
of
want
to
send
off
things
in
batches
versus
like
on
demand.
Do
you
know
if
there's
any
work
being
done
to
help
you
know
cut
down
the
battery
issues.
C
Well,
that
goes
back
to
like
the
idea
of
like
doing
server,
rendering
rather
than
client
side
rendering
so
for
mobile
devices
when
you
do
client-side
rendering
that
takes
a
lot
more
time
to
get
to
like
your
initial
content,
because
you
need
to
make
multiple
requests
you
send
down
like
the
initial
html,
then
your
html
like
sends
like
an
ajax
request
over
to
your
server.
You
get
that
data,
and
then
it
does
client-side
rendering
on
that
data,
whereas
with
like
modem.
D
The
behavior
is
optimized
for
mobile
is
what
you're
saying
exactly.
It
is
optimized
mobile
and
also
you
can
provide
the
correct
configuration
you
know
based
on
you
know,
whatever
user
engine
you're
targeting
so
that
you,
you
know
you
disable,
for
example
the
javascript
runtime
on
the
client,
because
you
know,
if
you
don't
have
like
a
high-end
device
running,
you
know,
lots
of
javascript
code
tends
to
slow
down.
Things
might
be
easier
to
just
have
everything
rendered
mostly.
D
C
E
A
C
But
so
part
of
the
things
that
we're
doing
like
with
our
example
like
application
with
photo
news
like
we're,
also
integrating
some
of
the
newer
things
that
are
going
to
like
yui
core
today.
So
it's
not
like
we're
ignoring
yui
or
anything
like
that
yeah.
So
like
the
work
that
we're
doing
with
like
es6
modules
and
all
of
that.
That's
also
like
part
of
the
system.
D
D
C
And
so,
if
you
like,
saw
like
eric's
talk
at
uwe,
so
the
idea
is
that
we're
trying
to
like
make
it
easier
for
you
to
use
like
the
stuff.
That's
coming
in
the
next
version
of
javascript
like
today,
and
that's
what
we're
doing
with
like
modem
now
and
we're
also
giving
you
like
those
like
performance
improvements
with
like
server
rendering.
A
A
So
there's
a
lot
of
really
exciting
javascript
type
things?
That's
related
to
this
that
I
think
you
would
find
there's
a
lot
of
really
a
great
work.
That's
being
done
right
now,
a
lot
of
like
cutting
edge
stuff.
So
if
you're
interested
in
this
kind
of
thing
definitely
reach
out
to
us,
because
this
is
one
of
the
hot
areas
inside
all.
C
To
add
yeah,
I
don't
know
how
much
time
we
have
for
today,
but
I
was
just
going
to
do
like
a
bit
of
a
more
of
a
deep
dive
on
like
some
stuff
that
we
were
doing
with
like
some
specific
modem
component,
which
was
like
express
map,
for
instance,
and
what
we're
doing
with
express
map
is
that
the
idea
behind
it
is
that
we
want
to
like
create.
We
want
to
be
able
to
like
share
routes
between
the
client
and
server.
C
Then
these
routes
can
be
shared,
and
what
express
map
does
is
that
if
you're
using
express
you
all
you
need
to
do,
is
you
create
your
routes
once
and
then
these
routes
can
be
serialized
turned
into
like
a
single
json
object
and
that's
sent
over
to
a
client,
and
then
we
can
immediately
put
that
into
like
a
y-dot
router
instance,
for
example,
and
then
your?
Why
not
router
instance
automatically
gets
the
routes
already
set
up?
C
You
don't
need
to
write
it
twice,
so
the
express
map
is
used
like
already
on,
like
a
bunch
of
sites,
there's
actually
a
good
use
case
for
it
like,
even
if
you're,
not
building
like
a
single
page
application
or
even
using.
Why
not
router,
for
example,
you
take
a
look
at
like
the
pure
site,
for
instance,
the
puresight
is
using
like
express
map
today
and
how
it's
using
it
is
that
if
you
look
at
like
the
sidebar
for
the
pure
site,.
C
Like
all
of
these
links,
right
now
are
generated
using
express
map
and
express
annotations,
and
the
idea
is
that
in
express
like
these,
these
sidebar
links
all
they
need
to
do.
We
have
like
this
like
shortcut,
helper
called
page
and
then
all
we
do
is
we
link
this
page
with
like
a
specific
label
and
a
name,
and
these
are
passed
over
to
the
peers
site,
and
then
it's
automatically
rendered
this
and
then
inside
your
templates.
C
C
So,
instead
of
having
to
like
change
the
links
every
single
time,
let
me
zoom
in
on
that,
instead
of
having
to
change
write
like
your
links
specifically
out
inside
your
templates,
all
you
need
to
do.
Is
you
can
reference
a
link
using
this
path
to
helper
and
by
doing
that,
you
don't
need
to
like
hard
code
any
links
anymore,
and
the
benefit
of
that
is
that
if
you
ever
decide
to
like
change
how
your
website's
urls
are
structured,
you
don't
need
to
like
go
through.
C
All
of
your
templates
go
through
every
single
thing
and
make
sure
that
they're
they've
been
changed
because
of
this
helper.
All
you
do
is
like
you,
reference
a
specific
url
using
like
home
or
some
other,
like
name
and
that's
the
benefit
of
using
express
map
like
just
as
a
standalone
module
you.
It
saves
the
time
for
you
to
like
not
to
separate
out
like
your
urls
from
your
templates,
so
it's
kind
of
like
locator.
C
For
paths,
well,
it's
specifically
it's
inside
your
template,
so
it's
it's
a
bit
of
a
different
use
case.
It's
not
like
compiling
anything
or
anything
like
that,
but
it
just
makes
it
easier.
It's
like
a
better
separation
of
concerns
between
your
templates
and
your
application
code,
where
your
routes
live.
E
D
So
so
one
thing
that's
worth
adding
to
to
currents.
Explanation
is
so
you
can
also
use
express
map
to
to
add
a
very
specific
metadata
for
your
application,
so
I
can
tell
only
express
copies
using
express
annotations,
but
you
know
by
attaching
extra
metadata
to
specific
route
that
you
have.
You
can
have
this
information
available.
Also
so
not
you're,
not
just
shipping
like
routes,
information,
but
you
could
be
shipping
metadata.
That
is
applicable
to
your
application
based
third
round,
and
I
think
that's
that's
very.
C
Good,
and
so
like
an
example
of
that
is,
if
you're
like,
if
you
want
to
group
like
a
set
of
routes
together.
So
if
you
want
to
group
like
a
set
of
routes
under
like
a
block
as
part
of
your
blog
or
something
like
that,
another
set
of
routes
as
part
of
your
main
application,
you
can
set
that
up
inside
your
metadata,
like
grouping,
is
use
case
that
you
can
do
with
that.
E
C
C
A
Okay,
well,
let's
see
outside
of
the
this,
the
lowdown
focused
content
that
we
want
to
cover
today.
I
encourage
you
guys
to
look
at
the
road
map
for
yui.
The
next
sprint
sprint
12,
which
is
on
the
wiki
page.
You
can
see
the
dates
there
for
our.
Why
why
the
whitebase
release
there's
a
lot
of
really
interesting.
A
C
Some
other
time
when,
like
once
around
so
right
now,
like
a
whole,
bunch
of
people
are
we're
hosting
tc39
at
yahoo
this
week,
which
is
basically
the
ecmascript
meeting,
so
they
help
to
decide
like
the
future
of
javascript.
So,
basically,
all
these
famous
javascript
celebrities
are
all
downstairs
right
now,
like
douglas,
amongst
others
like
brendan
nike,
the
guy
that
invented
it
yeah.
So
they're
all
right
downstairs,
they're,
like
five
floors
below
there's.