►
From YouTube: YUI Open RoundTable May 30, 2013
Description
YUI Open RoundTable May 30, 2013
A
B
B
B
Actually,
no
second,
my
first
time
was
march.
We
had
spring
break
and
I
had
a
chance
to
visit
yahoo
through
some
mutual
friends
so
yeah.
I
definitely
love
the
city,
definitely
different
from
where
I
come
from.
Where
are
you
originally
from
well?
I
live
in
tennessee,
born
and
raised
in
new
orleans
and
in
california,
just
a
different
culture.
A
Yeah,
I
spent
a
lot
of
my
life
in
kentucky
and
we
came
out
here
for
a
visit.
There's
no
other
better
place
to
be
oh
yeah
kind
of
grows
on
you,
so
you'll
probably
be
here
the
rest
of
your
life,
so
we've
got
a
pretty
light
show
today
in
terms
of
things.
We've
we've
been
doing
a
lot
of
behind
the
scenes,
work
to
make
things
go
smoother
in
terms
of
or
requesting
issues.
D
I
think
it
ended
up
getting
about
400
points
and
there
were
like
150
comments
on
it,
and
I
I
didn't.
I
didn't
get
a
chance
to
like
comment
on
everything,
but
a
lot
of
the
people
from
the
community.
I
know
juan
and
and
a
few
other
people
I
think,
alex
schuster
and
some
other
people
commented
and
like
were
were
in
there
and
you
know
actively
answering
questions
and
stuff.
D
D
A
D
All
right
awesome,
so
I've
been
giving
I've
given
this
talk
a
few
times
so
hopefully
it's
still
fresh
so
pure
is
a
set
of
small,
responsive,
css
modules
that
you
can
use
in
every
web
project
for
a
bit
of
background
about
why
or
what
this,
how
this
relates
to
yui?
You
can
kind
of
look
at
the
yui
blog
post
that
went
up
earlier
today.
D
So
css
frameworks
are
really
useful.
Bootstrap
and
zurb
are
some
of
the
more
popular
ones
and
I've
used
both
of
them
in
different
projects,
and
they
definitely
have
their
use
cases.
I
think
they
make
web
development
a
lot
easier
and
a
lot
faster
in
some
cases,
and
so
I'm
I'm
all
for
using
css
frameworks.
D
In
fact,
some
of
my
favorite
user
interfaces
on
the
web
are
made
using
css
frameworks.
So
here
are
a
few
that
I
grabbed
from
the
bootstrap
expo
page
and
you
can
see
that
they
all
look
pretty
different.
So
that's
that's
great,
but
if
you,
if
you
look
at
these
sites
and
if
you
actually
kind
of
get
through
the
source
code,
it
makes
you
think
a
bit
more.
D
So
when
you
look
at
websites
on
on
the
internet,
they
all
look
unique,
but
they
all
share
some
common
elements
and
we
nailed
it
down
to
six
of
them,
although
they
might
be
more,
firstly,
they're
all
css
all
websites,
sorry
usually
have
some
sort
of
base
or
some
sort
of
foundation
css,
whether
it's
like
reset
or
normalize,
or
some
sort
of
foundation
layer
that
just
normalizes
or
resets
everything
across
browsers
removes
all
the
browser.
Chrome.
Essentially,
most
websites
also
use
goods
nowadays,
whether
it's
responsive
grids
or
non-responsive
frameworks
come
with
their
own
grid
systems.
D
So
that's
something
that's
common
and
then
you
get
to
html
elements
that
are
common
across
websites,
so
most
sites
have
inputs
and
have
to
use
forms
for
user
input
and
styling
and
aligning
forms
across
browsers
and
across
mobile
devices
is
actually
kind
of
tricky.
So
that's
something:
that's
that
that
we
need
css
for
all
websites
need
some
type
of
navigation
structure,
whether
a
fixed
nav
as
a
fixed,
horizontal
navigation
or
a
vertical
nav
or
responsive
nav.
D
D
So
there
are
some
cons
with
this,
even
though
it
works
well.
Sometimes.
Firstly,
you
end
up
with
potentially
lots
of
unused
css
rules
at
basketballs.
These
frameworks
are
quite
heavy,
so
some
people
say
that,
well
you
don't
need
to
pull
out
all
of
bootstrap.
You
can
just
pull
down
the
modules
that
you
need,
which
is
true,
but
even
if
you
pull
down,
let's
say
forms
from
bootstrap.
It's
actually
like
over
16kb
of
css
for
forms,
and
do
you
really
need
pre-pending
or
pending
inputs
in
your
in
your
website?
D
D
D
So
as
an
example,
if
your
framework
has
a
lot
of
text,
shadows
and
box,
shadows
and
gradients-
and
you
won't
have
a
flat
ui
you're,
still
pulling
down
all
that
code,
which
has
the
gradients
and
box
shadows.
But
then
you
have
to
go
in
and
add
rock
shadow
non-touch
shadow
non-backgrounds
all
over
the
place
right,
so
it
becomes
kind
of
painstaking
to
do.
D
The
other
extreme
is,
if
you
don't
use
a
framework
at
all
and
we
just
use
a
base
which
is
like
a
reset
or
a
normalize,
and
then
we
write
our
application
css
directly
on
top
of
that,
so
this
is
great.
This
lets
you
have
complete
control
of
your
css,
but
the
problem
here
is:
you
have
to
handle
browser
inconsistencies
of
your
design.
D
You
have
to
make
your
own
sort
of
grid
or
something
you
have
to
deal
with
things
that
you
don't
necessarily
want
to
deal
with.
You
can't
focus
on
your
application's
design
anymore.
You
have
to
focus
on
lower
level
foundational
pieces
that
will
slow
you
down,
so
instead
here
is
meant
to
act
as
an
alternative.
D
If
you
use
peer,
you
can
take
the
pure
css
file
and
build
your
custom
application
styles
on
top
of
it,
and
what
pure
is
is
a
minimal
set
of
css
styles
or
common
components
on
the
web
and
the
best
part
about
pure
is
that
it
doesn't
stop
you
from
using
a
css
framework.
Necessarily
so
if
you
let
pure
handle
the
foundational
css,
the
six
things
that
we
saw
that
we
mentioned
before,
you
can
still
use
this
css
framework
to
pull
down
the
modules
that
you
need.
D
D
So
here
is
this
foundational
set
of
css
modules
that
you
can
use
in
every
web
project,
and
it's
really
really
small
right.
It's
only
it's
under
4kb
minified
inch,
so
it's
tiny!
It
has
a
very
minimal
and
flat
design
so
that
you
can
build
on
top
of
it
and
you
don't
have
to
overwrite
rules.
You
can
add
your
words
in
as
you
go
along
and
it
works
really
well
with
other
frameworks
out
there,
because
everything's
name
spaced.
D
So
all
the
classes
have
a
pure
prefix
and
you
can.
We
made
it
really
easy
step
to
get
started
with
it,
because
it's
on
youtube
and
you
basically
copy
paste
your
link
tag
on
your
on
your
page
and
you're
good
to
go
so
obviously
pure
is
completely
open
source.
I'm
sure
you
guys
know
this
by
now.
We
open
sourced
the
website
as
well,
which
is
something
that
a
lot
of
people
know.
The
pure
website
is
actually
dog
food
in
pure,
so
the
menu
on
the
left
side
is
a
pure
menu.
D
Everything
is
kind
of
dog
feeding
pure
under
the
hood
animated.
That's
how
we
kind
of
tested
to
make
sure
that
we
appear
the
right
way,
because
this
was
a
real
life
example
that
we
were
building
on
top
on
top
of
the
chamber.
So
you
can
check
it
out
on
github
at
the
yu,
pure
or
yy,
slash
puresight,
and
there
are
actually
some
layouts
that
we
made.
D
I
don't
know
if
people
have
checked
this
out,
but
we
have
some
responsive
layouts
out
there
for
both
iphone
for,
like
they're
all
responsive,
so
they
work
great
on
iphone
ipad,
larger
screens.
So
you
can
check
those
out
as
well
and
if
you
guys
are
willing
to
contribute
layouts,
then
that
would
be
great
too
so
yeah,
that's
pretty
much.
The
talk
that
I
gave
at
css.
A
D
There's
definitely
room
for
a
lot
more,
and
so
that's
something
that
any
contributions
that
we
get
on.
That
would
be
great,
I'm.
Actually.
I
actually
have
another
layout
in
the
works.
I
have
a
layout
for
kind
of
kind
of
like
a
form
like
it
has
really
heavy
form
based
ui,
but
the
gold
layouts
is
twofold.
We
have
some
layouts,
for
example,
in
the
marketing
layout,
which
is
like
copy
paste.
D
Well,
you
can
put
in
javascript
too,
ideally
not
too
much,
but,
for
example,
with
the
email
layout.
I
have
like
two
lines:
javascript
to
toggle
a
class
name
to
add
the
responsive
menu
behavior.
So
you
can,
as
long
as
the
idea
is.
The
layout
should
be
very
easy
to
understand
if
someone
is
viewing
source
or
something,
maybe
in
the
future-
we'll
have
some
sort
of
documentation
along
with
the
layouts,
but
today
we
just
have
resource.
So
keep
that
in
mind
easy
to
understand.
A
D
A
D
C
So
what
is
the
I
guess,
the
grand
scheme
of
css
developer
tools,
the
libraries
and
frameworks
and
base
foundation
layers
that
they
can
build
off
of?
How
does
pure,
I
guess,
differentiate
itself
from
so
it
uses
normalized
css,
correct
yeah,
that's
right,
yeah!
So
then
it
basically
uses
normalized
css
is
the
bottom
layer
to
normalize
the
browsers,
which
is
the
point
of
that
library
and
then
pure
adds
on
a
layer.
On
top
of
that
that
what
I
guess,
what
what
would
that
layer.
D
So
the
way
I
think
about
pure
is
you
can
think
about
it
as
normalized
for
html
like
components
on
the
web.
So
what
it
does
is
you
have
normalized,
which
is
kind
of
like
just
apply
styles
kind
of
like
whatever
normalizes
the
browser
styles,
and
what
peer
does
is
basically
allowed
to
allow
you
to
have
like
a
menu
or
like
a
table
or
like
a
form
which
is
within
a
line
form
which
is
kind
of
very
tricky
to
do
in.
D
If
you
were
writing
the
css
yourself,
so
common
style
that
you
use
on
the
web
to
just
have
that
available
to
you
with
just
a
class
name
right
so
in
in
some
ways
it's
similar
to
bootstrap,
because
the
strength
of
bootstrap
is
that
you
had
a
class
name,
and
you
have
this
like
style
and
layout
of
this
thing,
that's
ready
to
go
the
way
it's
different.
Is
it
doesn't
impose
a
design
on
you
because
bootstrap,
I
feel,
is
very
opinionated
and
it
does
it's.
A
lot
lighter
right,
like
boot.
D
D
D
E
D
It's
okay,
you
will
get
the
idea,
so
there
are
two
ways
to
really
play
with
the
skinner
one
is
to
like
I
did
this
master
color
here
and
then,
like
it
kind
of
changes,
some
colors
down
under
the
hood
here.
But
what
I
do
is
I
kind
of
go
into
it,
and
skinner
plays
really
well
with
the
rest
of
the
wire
widgets.
D
D
So
what
I
usually
do
is,
if
you
can
create
this
custom
color
scheme-
I
don't
know
if
you
guys
saw
that,
but
you
can
click
on
this
custom,
color
scheme,
tab
or
sorry
like
radio
button
here,
and
that
brings
up
this
sort
of
ui
and
you
can
kind
of
select
the
colors
that
you
that
you
want
here.
So
let's
look
at
your
orange
whatever
I
want
this
to
be.
D
Jeff
has
mapped
these
these
colors
up
here
to
specific,
dom
elements
in
in
here.
So
you
can
you
basically
this.
So
you
get
something
that
looks
like
this
now.
You
can
start
tweaking
this
to
get
something
that
you
think
looks
right
and
then
once
you're
ready,
you
can
like
copy
paste
the
css
code
in,
and
you
have
like
styled
elements
without
kind
of
writing
any
of
your
own
css.
D
A
D
D
E
E
D
So
matt
matt,
I
think
matt
sereni,
is
working
on
the
command-line
virtue
of
it
and
I
think
stay
tuned
because
I
think
we're
gonna
try
to
integrate.
Like
my
my
ideas,
integrate
this
sort
of
scanner
like
functionality
directly
to
the
pure
site,
so
you
can
kind
of
have
a
toggle
that
brings
this
down
and
start
pulling
around
the
site
and
the
site
will
start
changing
in
front
of
you,
and
so
I
think,
there's
a
command
line
tool.
That's
in
the
works!
A
D
So
pure
is
an
independent,
yui
project.
That's
how
I
think
about
it,
like
the
people
who
use
yui
might
not
be
superior
and
people
who
use
superior
might
not
use
white
white.
I
think
the
latter
is
more
likely
to
happen,
but
people
who
use
pyramids
will
be
used
for
a
period
of
groups
or
something
else,
so
the
blog
post
that
we
put
out
earlier
just
tells
like
when
it
explains
how
here
and
why
do
I
fit
together
and
summarize
kind
of
what
that
pro
says.
D
So,
for
example,
data
table
right
now
has
its
own
custom
css
in
the
future.
It
would
probably
inherit
like
pure
table
css
and
then
overwrite
the
prefix,
instead
of
being
pure
to
the
ui
through
the
table
generator,
and
then
it
would
have
its
own
if
it
would
still
have
its
own
styles
for
like
they
will
sort
include
scrolling,
etc.
D
So
you
can
imagine
the
yui
grid's
importing
infantry
grids
and
just
making
small
changes
as
as
they
see
fit.
So
this
allows
pure
grids
to
kind
of
do
its
own
thing.
It
doesn't
have
to
be
restricted
by
whatever
yui
grades
needs.
Why?
Why
grades
can
just
import
in
from
a
specific
version
of
peer
groups
that
it
finds.
A
D
You
don't
so
how
that
thing
should
how
that
thing
works
is
include
the
peers,
link
tag
on
your
page
and
then
include
the
css,
that's
generated
by
skinner,
and
I
didn't
show
this,
but
on
the
skinner,
all
the
css
is
prefixed
with
the
pure
skin
foo,
where
you
specify
what
foo
is.
So
you
add
pure
skin
food
as
a
class
on
your
body
tag,
and
then
you
include
pure
the
pure
css.
Then
you
include
the
cases
return
to
by
scanner
and
when
pure
updates,
you
should
be
fine.
D
So
pure
follows
december,
so
if
there
are
backwards
of
capital
changes,
just
look
for
that
on,
like
the
version,
so
every
time
there's
backlighting
typical
changes,
the
x
version
should
probably
go
up.
I
don't
foresee
any
backwards.
Parallel
changes
right
now,
where
I
have
some
things
planned
for
like
pure
1.0,
which
I'm
kind
of
working
on
towards
right.
Now
I
don't
foresee
any
backwards.
A
D
I
think
eric
and
I
were
talking
about
either
weekly
or
biology
releases,
so
I
think
we're
gonna
get
we're
gonna,
probably
have
a
post
out
for
that
soon
to
figure
that
out
and
we're
also
looking
to
figure
out
our
contributor
model
and
if
it's
the
same
as
yui,
if
it's
likely
different.
So
that's
something
we're
working
on
right
now
as
well.
D
So
I
think
version
one.
So
this
is
personal
opinion.
So
don't
don't
quote
me
on
any
of
this
because
well
yeah,
but
this
might
not
happen,
but
my
emphasis
or
what
I
would
like
to
see
from
here
is
for
it
to
be,
have
better
examples
for
how
to
make
web
and
mobile
response
like
more
responsive
and
more
unique,
responsive
layouts.
D
So,
for
example,
the
menu
on
the
pure
website,
the
kind
of
the
one
that
comes
out
from
the
side,
that's
actually
using
raw
javascript
like
two
lines
of
raw
javascript
and
some
custom
css
that
we
wrote,
but
it
uses
pure
menu
under
the
hood.
So
to
have
that
in
it
as
an
example.
So
we
can
just
pull
that
in
very
easily
some
more
examples.
Kind
of
like
that.
Yes,
part,
is
the
actual
source
code.
D
There
is
a
little
section
down
there,
which
shows
css,
typography
and
css
extracts,
which
are
these
two
css
modules
that
I
wrote
that
extend
pure,
so
css
typography
allows
you
to
have
type
of
typography
css
on
your
site.
You
can
basically
have
have
these
common
typography
elements
really
easily.
Css
extras
allows
you
to
have
it's
common
stuff
that
not
every
site
needs,
but
are
very
useful
to
have
so
things
like
image,
thumbnails
alerts,
etc.
D
Right
exactly
so,
these
are
things
that
we
don't
want
to
put
into
the
core
of
pure,
but
these
are
things
that
we
want
the
third
party
like
the
community
to
develop,
and
we
want
to
be
able
to
showcase
that.
So
I
think
the
way
we're
going
to
go
about
doing
that
is
through
bauer.
So
you
can
have
a
github
repo
and
we'll
have
examples
of
this
when
it
does
come
about.
D
If
it
comes
about,
but
for
example,
let's
take
css
typography
as
an
example,
I
think
it's
on
my
github
repo
right
now,
but
I
can
have
like
a
bauer
dot.
Jc
file,
which
says
put
this
on
the
bower
package
package
management
system
as
pure
dash,
typography,
and
then
someone
could
say,
bow
or
install
pure
typography
and
then
they'll
get
like
all
the
css
for
typography
that
they
need
for
their
project
so
and
on
the
pure
css
side.
D
We
would
have
a
list
of
all
these
things
that
are
on
valor,
so
that
it
makes
it
really
easy
for
people
to
pick
and
choose
modules
that
they
need
to
make
their
site
look
different
because
someone
might
go
and
come
and
say.
Oh,
I
don't
really
care
if
my
alerts
look
the
same
as
everyone
else's,
because
my
website
focuses
on
something
else.
I
don't
really
care
about
the
work,
so
they
can
just
pull
in
like
pure
alerts
or
pure
exporters,
or
something
like
that.
A
D
I
was
talking
to
eric
earlier
today
and
we
were
talking
about
how
grunt
does
it.
So
if
you
go
to
crunch.js-
and
you
know,
grunt
has
the
idea
of
plugins
and
they
have
this
page,
where
you
can
search
plugins
really
easily
and
they
do
have
they
have.
They
have
a
notion
of
like
what's
blessed
because
they're
like
a
star
in
front
of
it
like
that,
but
the
idea
is
we,
don't
you
wouldn't
host
those
necessarily
on
the
cdn,
but
someone
can
some
devil.
D
C
D
Yeah
I
mean
this
place.
This
is
still
so
young
right
like
two
to
three
years
old,
so
I'm
still
freaking
out,
and
so
all
the
stuff
is
just
very
hypothetical,
but
I
kind
of
made
a
couple
of
sites
using
pure
and
that
those
are
some
things
that
I
found
would
be
useful
to
have
some
sort
of
overlays
to
pull
in
other
css
that
you
don't
want
to
write
yourself
over
and
over
again.
A
Awesome
very
cool.
Well,
I
appreciate
you
coming
today
to
talk
to
us
about
pure.
I
know
a
lot
of
people
are
excited,
especially
received
on
twitter,
one
of
the
first
tweets
that
I
saw
that
mentioned
this
has
over
100
retweets
now
about
it,
which
is
pretty
phenomenal
for
twitter
paid
that
link
usually.
A
C
C
Yeah,
so
I
figured
there's
probably
some
questions
out
there
about
why
there
are
so
many
new
issues
popping
up
with
test
failures.
Well,
what
we've
been
doing
and
focusing
on
a
lot
over
the
last
few
weeks
as
we've
much
longer
than
that?
Actually
yeah
well
yeah.
So
a
couple
months
ago
we
started
onboarding
more
and
more
and
more
c
and
testing
environments
in
the
ci.
So
using
yeti
up
until
a
few
months
ago
we
were
only
testing
per
commit
or
per
push.
C
C
E
C
Different
versions
of
firefox
mobile
devices,
everything
that
we
can
find
and
put
our
hands
in
we're
putting
those
into
ci
now.
So
the
reason
why
we're
getting
all
of
these
new
failures
aren't
they're,
not
regressions,
they're,
just
tests
that
have
not
previously
been
extensively
tested
in
these
new
environments.
C
So
we've
spent
a
lot
of
work
a
lot
of
time
over
the
last
few
weeks
and
few
months
actually
going
through,
and
updating
and
updating
yeah,
so
updating
all
the
tests
to
essentially
work
in
all
these
new
environments,
and
so
the
reason
why,
over
the
last
week
or
two
we've
seen
so
many
more
issues
filed,
is
because
now
we're
there's
a
higher
sense
of
priority
on
getting
all
of
these
resolved
and
fixed
and
closed
out.
So
one
thing,
you'll
notice
that
it's
not
that
necessary.
A
That
there's
anything
code
wise
that
we're
fixing
is
that
we're
discovering
we're
trying
to
beef
up
the
robustness
of
the
tests
themselves.
So
there
may
be
a
test
that
fails
like
five
out
of
ten
times.
So
we
can
see
that
a
flaky
test
right,
so
we're
trying
to
do
is
identify
which
tests
are
the
flaky
tests
and
work
out
either.
You
know.
First,
they
go
into
a
special
bucket
where
we
monitor
them
more
closely
and
we
don't
let
them
be
part
of
the
noise
of
the
regular
testing
environment.
C
Yeah
so
bottom
line.
No,
these
aren't
regressions
that
are
popping
up
they're,
just
yeah
tests
that
we
need
to
fix
or
tweak
or
update
yeah
to
essentially
get
them
to
to
pass
in
all
of
these
new
environments
and
the
end
result,
hopefully
in
the
next
few
weeks,
once
we
get
them
all
taken
care
of
is
that
the
library
will
be
rock
solid
and
tested
in
pretty
much
every
environment
that
we
can
think
of
so
yeah.
All
this
is
effort.
A
C
A
C
A
So
we
have
the
other
items
we
have
are
the
stale
pull
requests,
and
the
great
thing
about
this
week
is
that
people
been
really
rocking
on
getting
responses
back
or
working
their
lists,
and
there
are
no
candidates
for
the
staple
request
discussion
this
week.
There
are
two
that
are
old,
but
they've
been
there
forever
and
they're,
not
they're,
not
coming
up
right
now.
C
That's
pretty
awesome
because
I
think
this
is
the
first
time
we've
had
there's
been
other
times
when
we've
skipped
the
scale
request
review,
but
I
think
this
is
the
first
time
we
have
actually
not
had
any
stale
pull
requests
since
we
started
doing
the
open
route
table
like
six
months
ago.
That's
pretty
awesome,
yeah.