►
From YouTube: YUI Open RoundTable 04/04/2013
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I
think
a
lot
of
people
are
suffering
from
hangout
fatigue
syndrome
and
I.
Wear
yes,
Esther
lunch,
so
I'm
here
with
me
and
Derek,
and
everyone
who
may
or
may
not
be
watching
from
now
until
the
infinite
future
until
generations
will
be
watching
this
he'll
dig
up.
Some
archive
now
find
this
YouTube
collection
and
we'll
be
in
there.
I
wonder
why.
A
B
A
A
That's
right:
Luke
enters
the
battle.
He
uses
headphones.
It's
super
effective,
so
in
terms
of
discussion
topics,
one
I
there's
a
lot
of
things
going
on
next
week
in
terms
of
meetups
and
hang
out
some
things
like
that.
Luke
has
a
hangout
scheduled
for
next
tuesday
at
11am,
PDT
or
PSD
X
PDT,
because
daylight
saving.
B
A
C
When
it's
actually
put
to
use,
then
it's
natural
use
cases
emerged,
but
then
there's
still
a
lot
of
extra
stuff.
That's
left
over,
and
so
there
are
a
lot
of
opportunities
in
the
current
event
system
for
performance
enhancement,
which
Satya
and
Eric
have
been
doing
a
really
fantastic
job.
Recently,
the
new
stuff
going
into
I
think
310.
C
Some
really
good
performance
numbers
coming
out
of
that,
but
the
performance
enhancements
that
they're
putting
on
the
event
system
are
using
the
existing
infrastructure
and
there
are
some
opportunities
to
to
clean
up
the
code.
It's
it's
a
fairly
large
code
base
at
this
point
clean
up
the
code,
simplify
it
and
actually.
C
C
The
two
large
differences
between
the
current
event
system
and,
what's
going
on
in
Ventax,
aside
from
the
loose
tens
that
aren't
yet
filled
out,
are
that
are
the
notion
of
events
being
published
statically.
So
you
define
the
events
for
a
class
and,
just
like
you
would
define
your
attrs
collection,
you
would
define
your
your
events,
collection
as
well,
and
so
there's
no
publisher
being
involved
on
a
per
instance
basis.
C
A
Focus
on
Tuesday
Adam
about
this,
like
do
you
see
this
living
alongside
the
existing
event
system
for
a
while,
and
what
do
you
think
about
like
migration?
What's
a
migration
strategy
for
somebody.
C
A
Thanks
for
the
notice
right,
no,
but
number
folks
will
be
giving
short
as
I
have
formal
presentations.
Anyone
else
is
invited
to
do
so
as
well.
The
main
thing
is
to
get
everybody
in
the
room
together
to
talk
about.
Why
you
I
and
cool
ways,
though
we've
guarded
we've
got
Luke,
is
planning
on
coming
Ryan's,
fighting
a
coming,
Eric
and
rested.
Why
why
team
who's
available
will
be
coming
as
well
and
they're.
C
A
A
A
C
A
A
So
if
you
are
in
the
Bay
Area-
and
you
want
to
there's
someone
that
on
the
Yui
team,
they've
been
dying
to
talk
to
and
the
times
are
open
to
come
and
you
know
don't
you
don't
have
to
worry
about
any
specific
time
that
we
already
have
set
up.
If
you
want
to
schedule
something
else,
that's
like
that
feel
free
to
get
ahold
of
me
or
talk
to
email
to
get
on
IRC.
If
you
like
that,
I
folks
know.
B
C
A
C
B
C
A
A
A
C
A
C
A
I
think
what,
when,
whenever
he
was
talking
about
this,
there
was
this
there
was,
you
know
the
foreknowledge
they
wanted
to
get
the
code
in
and
that
that
was
forthcoming
afterward
and
they
didn't
want
to
hold
up
the
release
for
that.
So
I
think
that
was
either
especially
accepted
or
something.
But
given
the
issues
that
we
had
with
the
previous
two
belts,
it
was
good
that
we
didn't
want,
wait
any
longer.
C
A
B
C
C
A
C
That
the
short
form,
which,
of
course
I'll
also
give
the
meet
up
next
week,
is
that
promises
allow
you
to
represent
some
value
that
may
exist
or
needs
to
be
calculated,
asynchronously
I
in
a
more
synchronous,
looking
manner,
and
so
it
actually
helps
clean
up
your
code
and
make
your
code
a
lot
more
readable.
So,
for
example,
I
have
a
value
that
I
need
to
get
using
I.
Oh
so
right
now,
you'll
call
into
I,
oh
and
you'll
set
up
these
callbacks
and
you
so
now
you're
going
to
be
managing
these
callbacks.
C
You
can
use
that
promise
right
there
and
right
then,
to
reference
whatever
that
value
will
be
when
it
comes
back
and
that
that
promise
sticks
around
as
long
as
you
can
store
that
promise,
and
you
can
reference
it
as
many
times
later,
as
you
want
to,
and
whether
or
not
it's
resolved
when
you're
referencing
it
it'll
will
call
back
into
your
your
then
call
back
asynchronously
always
asynchronously,
but
your
code
ends
ends
up
looking
like
do
this,
and
then
this
and
then
this
and
then
this
and
then
I'm,
going
to
keep
this
promise
around.
Here.
C
That's
going
to
represent
this
asynchronous
value
so
later,
on
elsewhere,
in
your
code,
you
can
say
that
promise
dot
then
I'm
going
to
use
this
value
in
this
way
right
zip.
It
really
simplifies
a
lot
of
consumption
of
data
from
asynchronous
sources
and
and
composing
transactions
in
individual
steps
or
even
asynchronous
steps.
So
yeah.
B
At
least
within
Yui
benchmark
I've
been
there's
a
lot
of
async
code
in
there,
so
I
been
using
the
make
it
remember
the
guy
who
wrote
it,
but
there's
a
note
pad
or
an
Indian
package
called
a
sink.
So
basically
the
code
books
like
about
what
a
sink
series
are
then
function,
one
two,
three
four
five
and
six
and
then
it'll
execute
each
one
of
those.
In
order
that
you
specify
and
then
inside
of
each
of
those
functions,
you
just
have
to
call
callback
which
will
make
it
proceed
to
the
next
one.
C
That's
a
callback
implementation
of
effectively
the
white
batch
method,
which
is
part
of
promises.
Okay,
a
batch
takes
actually
an
any
number
of
promises.
Originally,
it
was
written
to
take
functions
as
callbacks
or
functions
as
callbacks
or
promises
or
even
raw
values,
but
for
the
sake
of
the
simple
getting
it
out
the
door
version
we
started
with
promises,
you
might
expand.
It
I
actually
liked
it
better
when
it
took
functions
with
call
back.
So
you
didn't
have
to
go
the
overhead
of
creating
promises.
Everything
yeah.
B
B
C
Promises
are
very
popular
in
the
client
said
pretty
much.
Every
library
has
them
now
and
there
are
a
lot
of
different
implementations.
The
work
that
I
was
doing
on
the
promises,
a
plus
specification,
there's
a
lot
of
movement
now
for
promise
implementers
to
be
compatible
with
the
A+
spec,
which
is
fantastic,
because
it
means
that
everyone's
agreeing
on
how
to
make
this
stuff
work,
but
in
terms
of
owing
including
the
dom
by
the
way,
dom
futures
are
really
promises
a
plus
compatible.
That's.
C
C
Futures
yeah,
so
the
Alex
Russell
has
been
working
on
with
the
the
I
forget
which
committees
on,
but
in
creating
a
specification
for
Dom
futures
and
AKA
promises,
so
actual
promises
in
the
Dom
followed
up
by
actual
promises
in
atmos
crypt.
So
that's
the
promises
and
ActionScript
in
language
core
is
future
but
potentially
having
futures
by
the
name
of
yeah
futures,
I'm.
C
Sorry
I
promises
by
the
name
of
futures
in
the
Dom
could
very
well
happen
in
the
in
the
relatively
near
future,
which
is
pretty
exciting
and
especially
exciting
that
they'll
be
promises
a
plus
compatible,
which
means
that
how
you're
using
promises
today
will
not
change
when
they
become
a
native
natively,
supported
feature
in
the
Dom
and
then
potentially
in
in
equus
crew,
but
oh
so
yeah.
So
promise
is
a
very
popular
in
terms
of
the
client
side
and
every
library
has
support
for
them.
Node
is
its
own
sort
of
Beast.
C
There's
been
a
little
bit
of
tension
between
the
node
community
who
previously
had
promises,
and
then
they
were
extracted
from
from
knock
or
another.
They
prefer
the
callback
syntax
there
are
there
promise
modules,
but
the
the
typical
way
to
do
things
involves
call
back
and
they
use
callbacks,
so
a
sink
is
is
where
they
would
go
to
if
they
wanted
to
do
some
async
resolution
stuff.
Instead
of
going
to
promises,
it
sounds
sounds
more
typical,
I'm
not
really
close
to
the
community,
so
I
can't
really
speak
authoritative.
Let's.
A
C
In
fact,
promises
uses
y
dot
soon,
which,
as
Steven
Olmstead
created,
which
is
compatible
with
next
tick.
So
if
it's
used
in
node,
it'll
use
the
nodes
version,
her
a
node
method
was
processed
next
tick,
which
is
effectively
a
set
timeout
0,
but
it
schedules
the
next
tick
of
the
event
loop.
Something
happening
then
so
so
it'll
happen
as
soon
as
possible,
including
on
node.
So
so
that's
there
already
so.
A
C
Well,
not
really,
that
was
part
of
the
documentation
that
I
wanted
to
write,
but
for
lack
of
time
the
and
also
it's
it
is
I.
Myself
have
not
written
an
awful
lot
of
promise
based
code.
You
know,
I,
have
you
know
I
wrote
promises
so
that
I
could
write
promise
base
code
and
now
I'm
starting
to
write
from
a
space
code
and
so
I
not
having
it
an
extensive
background
in
using
them.
I
can't
really
speak
to
what
the
best
practices
are
with
any
with
any
level
of
confidence.
B
C
A
I
have
just
a
couple
of
the
request
to
talk
about
real,
quick
or
request
542
I'll.
Just
for
my
lack
of
wasting.
A
A
B
Who
owns
that
further
cook
that
I
do
not
know,
I'm
not
even
sure
if
there
is
no
way
we
can
look
it
up,
and
me
me
used
to
be
just
to
be
me.
A
A
Things
like
this
I
feel,
like
you
know,
we
have
people
who
want
to
volunteer
to
do
things
and
we
have
course
low-hanging
bugs,
but
I
think
one
of
the
aspects
that
would
be
nice
to
do
is
get
folks
to
begin
to
make
comments.
You
know
on
other
people's
or
requests
as
a
way
of
wearing
the
code
base.
Yeah.
A
A
B
A
A
bracket
step
I,
oh
and
one
things
they
really
have-
is
a
really
great
community.
That's
growing
quickly
and
they
prioritize
poor
requests
from
the
community
over
their
own
progress
for
each
release,
but
they
won
things
literally.
Hey,
that's
cool.
Is
this
in
the
github
account
they
have
issues
organized
by
sort
of
level
of
level
of
experience
and
if
you're,
like
a
new
person,
you
can
go
and
look
at
starter
bud.
So
if
you
go
to,
let
me
suppose
to
spiral
arce
list.
A
A
A
And
I
thought
this
matches
our
sort
of
unassigned
an
unassigned
right
now.
It
seems
to
be
kind
of
like
this:
no
man's
land
right
like
there's
no
rhyme
or
reason
for
something
in
there.
Just
someone
didn't
want
to
use
it,
whereas
this
seems
a
lot
more
targeted
toward
people
who
could
check
things
out
and
a
size.
Other
cool
labels
like
code
cleanup
like
so
you've,
worked
on
something
and
you
don't
have
time
to
like
make
it
pretty.
But
you
know
it's
working
you
could.
A
Instead
of
spending
that
time,
you
could
assist
someone
else
to
get
a
poor
question
for
that.
So
I
thought
those
are
pretty
cool,
so
I
think
some
of
these,
but
request
I
may
try
to
get
some
more
folks
involved
in
that
because
a
lot
of
times
what
happens
is,
like
you
said,
look
like
you,
there's
not
an
owner
or
people
really
busy,
and
this
would
really
feel
a
need
for
that
to
get
feedback.
A
Let's
have
that
again,
we've
got
if
you
look
on
the
round
table
topics,
page
that
on
the
side,
bugs
review
and
I.
Think
now
what
I'm
going
to
do
is
I'm
going
to
add
a
new
section
of
their
four
issues
that
could
be
useful
for
new
new
folks.
I
could
be
an
excellent
thing
to
do
so.
We
go
take
the
idea
from
these
brackets
folks
and
jump
on
that.
So
that's
how
that
that's
it
for
today,
I
thanks
everybody
for
coming
in
for
watching
and
next
week
will
be
really
busy.