►
Description
Discussion for Chapter 1: Tokenization & Parsing of the book Ruby Under a Microscope. The first 5 minutes or so were regrettably not recorded, but the discussion points can be found in the Google doc (https://docs.google.com/document/d/18Ekce5kFaEdAvY9OMRETmp8ukCmhhQqRjpbN9N0ssmk/edit#).
A
There
it
is
it
had
options.
I
couldn't
just
hit
the
button
once
all
right.
Well,
we've
already
been
a
little
bit
into
the
discussion,
but
this
is
the
ruby
under
a
microscope
book
club
meeting
in
the
american
and
apac
time
zone
friendly
time.
So
we
will
continue
the
discussion.
Some
talking
points
already
in
the
git
lab
or
the
sorry,
google
doc.
So
for
the
few
minutes
that
were
missed
in
the
recording
feel
free
to
check
that
out.
A
A
Okay,
just
like
how
much
is
going
on
under
the
hood
like,
I
think
there
was
one
point
where
they
had
us
run
like
ripper
on
some
simple
code
example-
and
I
was
just
like
blown
away
with
like
how
much
output
there
was
for
that
simple
file,
all
of
the
stuff
that's
reporting
on
doing,
which
is
probably
not
even
all
of
the
stuff
it's
doing,
but
yeah.
It's
just
kind
of
it's
kind
of
understandable,
then,
to
think
of
ruby
as
a
slow
language.
A
C
D
A
A
Yeah,
I
think
there
are
some
comments
about
that
in
the
other
one
too,
about
the
fragility,
perhaps
of
those
those
language
rules.
I
guess
I
don't
remember
what
they're
called,
but
those
rules
that
define
the
compiled
or
the
generated
parser
like
there's
a
lot
going
on
in
there
and
like
how
do
you
actually
test
it?
What
you're,
adding
or
changing
is
doing
what
you
want
to
the
language.
So
that's
really.
A
E
E
D
Yeah
I
like
that,
but
if
you
really
want
a
deep
dive
and
you
want
to
go
into
the
guts
of
it,
you
can,
if
you
like,
but
it's
not,
I
don't.
I
don't
think
I
wouldn't
call
it
strictly
required,
but
definitely
if
that
you
have
that
kind
of
interest,
you'll
be
interested
in
it.
But
if
not,
then
I
think
you
can.
You
can
skip
it
and
just
be
like.
E
A
C
A
F
F
Well,
this
whole,
it
kind
of
had
me
taking
a
look
like
as
I've
been
writing
code
of
sort
of
like
breaking
things
down
into
like
what
is
my
code
actually
made
of
like
okay,
like
I'm
working
in
a
class,
I'm
in
a
method,
this
method
has
a
couple
conditionals
and
some
other
things,
and
it
was
kind
of.
I
was
realizing
like
how
many
things
I
was
defining
the
name
of
and
in
just
defining
the
name
of
something.
F
F
One
thing
I
was
curious
about
when
I
was
reading
was
like
I'm
not
familiar
with
how
languages
are
written
or
much
about.
You
know
how,
like
the
people
that
work
on
them,
but
I
was
curious,
like
a
lot
of
languages,
are
built
on
c
and
I'm
I
was
kind
of
curious
like.
Are
there
a
lot
of
similarities
with
other
languages
that
are
built
on
c
or
is
it
like
a
completely
different
thing
altogether?
D
It
kind
of
makes
you
wonder
like.
Could
you
compile
any
language
in
other
in
some
other
in
any
other
language?
I'm
sure
somebody
has
tried.
You
know
I
mean
I've
seen
the
internet,
there's
lots
of
things
on
it,
but
yeah,
and
I
mean
I
know
that
certain
programming
languages
just
have
inherent
limitations
and
strengths.
A
E
That
was
one
just
another
like
ast
observation
of
something
I
thought
they
explained
well
was
the
order
of
operations
affecting
how
the
tree
ends
up
like
just
treating,
plus
and
multiply
differently
and
then
how
that's
expressed
kind
of
a
part
of
the
language?
That's
not
syntax
related,
but
still
communicates
something
just
by
the
shape
of
the
tree.
A
B
F
B
D
I
I
thought
I
thought
you
comment
about
how
to
be
as
expressive
as
it
is,
there's
so
much
more
work
that
goes
into
lexing
it
and
passing
it,
and
you
don't
just
say:
oh
the
user
has
to
do
this,
like
you
have
to
make
sure
that
you
define
everything
up
front
ruby's
like
oh,
you
know
what
it's
okay,
if
you
don't
because
I'll
figure
it
out
and
now
we
have
this
massive
file.
So
that's
why
so
I
mean,
I
know
that
that's
already
been
said,
but
I'm
really
appreciating
that.
A
D
A
B
A
E
A
E
Like
13
000
lions
is
a
bit
much,
but
I
personally
don't
mind
the
single
big
file
approach
to
things
I
I
feel.
Maybe
this
is
just
a
javascript
thing,
but
they've
gone
far
too
far.
They
we
and
javascript
just
has
thousands
of
tiny
files,
and
I
personally
think
it's
far
worse
than
one
big
file
distributed.
Complexity.
C
D
A
A
D
My
sense
is
that
this
this
chapter
is
probably,
although
it
was
really
interesting.
I
think
we'll
probably
get
to
juicier
discussions
as
we
get
into
some
of
the
stuff
past
the
passing
and
lexing,
because
it's
like
oh,
this
is
how
it
is,
and
then
we
can
get
into
more.
I
don't
know
juicy
stuff,
especially
as
a
as
it
integrates
with
rails
and
our
day-to-day
stuff,
because
it
feels
like
this
is
the
kind
of
thing
that's
kind
of
abstracted
away,
and
it's
like
a
kind
of
a
good
fyi,
sorry
about
the
construction
noise.
D
F
D
D
And
yeah,
I
would
think
I
would
think
that
that
it
would
be
in
a
in
a
good
curriculum.
I
can
I
can.
I
can
go
through
notes,
we
did.
We
did
some
accreditation
work
way
way
back
like
10
years
ago
or
something
and
we
also
yeah.
There
was
also
there.
There
are
sort
of
standards
that
they
have
to
have,
and
I
think
that
this
kind
of
thing,
even
if
it's
not
taught
directly
you'll,
run
into
it.
B
So
I
had
an
entire
course
in
you
know
the
beginning
of
my
graduation
for
hold
the
compile,
but
it
was
not.
You
know
specific
to
any
particular
language.
It
was
just
concepts
theoretical
concepts,
so
we
didn't
have
any
practical
implications
like
no
labs
or
any
kind
of
those
stuffs,
but
yeah
pretty
much
after
that.
I
don't
think
I
ever
went
back
to
these
topics.
D
A
A
A
A
E
I
like
one,
I
imagine
that
yeah,
like
I
think
charlie,
was
said
that
after
the
first
couple,
then
we're
more
into
relatable
stuff,
and
it
is
more
discussion
and
just
having
one
chapter
kind
of
gives
us
a
focus
yeah
I
agree
rather
than
yeah.
Then
you
run
the
risk
of
something
not
getting
discussed
right.