►
From YouTube: Hoot [Episode 1] - Istio Service Mesh
Description
Hoot is a livestream by engineers talking about and trying out new technology.
Get to Know Service Mesh
We kick this off with a series on service mesh - each episode will look into a different service mesh provider.
* Istio
* Linkerd
* Consul
* Community requests -- suggest a service mesh
* Compare and contrast the different service meshes, explain their unique features and how to choose which one(s) to use for your applications.
A
All
right,
good
morning,
good
evening,
wherever
you
might
be
joining
us,
my
name
is
Kristen
Costa
and
we're
going
to
kick
off
a
series.
Various
episodes
where
we
dive
it
into
different
cloud
native
technologies.
I'm
calling
it
hoot-hoot
is
the
sound
that
an
album
makes
owl
is
the
mascot
of
the
work
for
I.
Don't
think
it
has
an
acronym,
yes,
but
I
mean
tweet
us
and
maybe
maybe
suggest
some
acronyms.
Maybe
something
like
hacking
on
open
technologies
or
something
I.
Don't
know.
We
don't
have
an
acronym
for
system
name.
A
We're
gonna
try
to
do
this
every
week
or
so
to
the
extent
that
we
can
we're
gonna
start
off
with
a
series
within
a
series,
so
we're
gonna
we're
gonna
start
off
with
looking
at
different
service
mesh
technologies.
Today,
I'll
cover
is
do
and
some
of
the
usability
the
improved
usability
and
much
welcomed
usability
improvements
for
sto
and
then
in
the
next
week,
or
so
we'll
cover
linker
D,
we'll
cover
a
console
and
from
there
we're
open
to
suggestions
from
the
community.
A
So
if
you,
if
you
reach
out-
or
you
know,
mention
it
in
the
chat
or
tweet
us,
then
we'll
try
to
get
that
on
the
list
towards
you
know,
look
at
a
handful
of
different
and
then
we'll
also
look
at
we'll
do
an
episode
on
comparing
them.
I
know
a
lot
of
folks
that
we
talked
to
in
the
enterprises
are
looking
at
different
service
mesh
technologies
and
trying
to
decide
what
parameters
to
evaluate
with
and
which
service
mesh
might
be
best
for
their
situation.
A
A
The
subsequent
episodes
will
be
hosted
by
other
folks
on
our
team,
so
you'll
get
the
chance
to
meet
them
and
if
there's
any
interest
in
guest
hosting
or
you
know,
coming
on
and
showing
us
showing
up
some
of
the
technology
that
you
found
to
be
interesting
in
this
cloud
native
ecosystem
then
definitely
reach
out,
and
let
us
know
we're
very
open
to
that.
So,
let's
kick
this
off
we're
going
to
be
looking
at
sto.
The
latest
release
is
the
CE.
A
O
is
1.4,
which
came
out
I
believe
in
about
November
as
soon
as
it
around
now
for
a
couple
years,
and
it
is
a
service
much
so
unfamiliar
with
with
service
mesh.
That's
one
term
that
you
should
probably
go
do
a
little
research
on
and
I'm,
not
saying
you
gonna
find
crystal
clear
definitions
and
meaning
behind
it,
but
the
the
service
match
is
that
ecosystem.
Those
bits
of
technology
are
intended
to
help
stall,
some
of
the
difficult
challenges
of
securing
and
observing
and
controlling.
A
Ultimately,
the
communication
between
services
in
a
cloud
environment
and
cloud
deployed
to
cloud
infrastructure
things
like
kubernetes,
so
you
can
think
of
kubernetes
as
a
great
deployment
target
for
containerized
applications
and
those
applications
might
interact
with
services
running
on
a
potentially
server
list
environment
or
in
VMs
or
on
CREB.
You
might
find
that
your
existing
either
applications
or
existing
investments
and
applications.
You
know
all
of
these
services
need
to
interact
and
talk
with
and
communicate
with
any
of
the
new
micro
service
style
applications.
A
You
might
be
writing
and
with
that
comes
the
challenges
of
networking
of
security.
You
know
when
you
have
more
of
these
different
services
talking
to
each
other
and
their
ephemeral
and
they're
coming
and
going
you
have
the
challenge
of
identifying
those
services
and
and
securing
and
writing
policy
about
what
services
are
allowed
to
talk
with
which
so
this
do
is
an
open
source
project
that
is,
is
aiming
to
solve
the
problem
of
that
connectivity
and
and
then
controlling
it.
A
A
How
it's
implemented
I
think
is
found,
but
of
course
it
was
a
doddle
technology
and
it's
it's
continuing
to
improve
once
we
get
to
UC
1.3
and
when
a
four
we
see
a
lot
of
improvements
around
both
the
stability
and
usability
of
the
technology.
So
now
is:
do
this
does
a
little
bit
of
a
battle-ax
background?
Is
a
control
plane
that
drives
the
Envoy
proxies
that
are
deployed
with
your
application?
A
So
the
general
general
architecture
of
a
service
mesh
is
some
kind
of
agent
or
proxy
gets
deployed
along
with
your
application
and
runs
outside
of
the
application.
And
then
some
piece
of
of
configuration
is
used
to
drive
the
control
plane.
So
you
define
what
policies
you
want
to
see
what
security
you
want
to
see
and
you
send
that
to
the
control
plane
and
then
the
control
plane
will
disseminate
those
configurations
to
the
the
data
plane,
which
is
where
envoy
is
running.
A
A
So
just
again
this
year,
when
a
4
was
released
in
November.
So
this
is
out
right
now
the
things
I'm
going
to
show
you
are
available
and
then
toward
the
end.
I'll
show
you
some
of
the
things
that
are
happening
in
the
in
the
community.
You
know
1.5
is
targeted
to
be
released
in
the
middle
of
February,
so
these
are
things
that
show
you
will
they're
not
available.
Yet
but
they
will
be
coming
and
something
to
keep
keep
in
the
back
of
your
of
your
mind.
A
So
the
first
thing
that
we're
going
to
do
is
take
a
look
at
the
sto
Docs
for
getting
started
because
I've
seen
and
I've
been
where
I've
been
involved,
with
ACO
community
for
2017
and
I've,
seen
big
changes
and
improvements
in
the
getting
started,
experience
experience
and
the
usability
of
it.
So
first
thing
videos
come
click
on
setup
and
click
on
getting
started.
A
That's
where
most
new
comers
to
disco
would
would
navigate
so
you'll
the
beginning,
starting
experience
depends
on
kubernetes,
so
you'll
you'll
need
a
kubernetes
cluster
you'll
want
to
download
the
release
from
from
github.
You
can
follow
any
of
these
links
to
do
that,
but
the
interesting
part
that
that
I've
seen
is
the
new
manifests
commands.
So
when
you
download
a
steal,
it
comes
with
the
this
steal
cuddle
binary,
and
that
gives
you
in
the
past
that
was
fairly
simplistic
in
the
past.
A
It
was
just
you
could
use
that
to
inject
the
sidecar
next
to
your
kubernetes
deployment,
but
now
the
issue,
a
couple
command
has
become
more
of
a
entryway
to
the
ISTE
own
user
experience.
So
we're
going
to
take
a
look
at
the
disco,
cuddle,
steal,
live
and
then
some
of
the
commands
that
have
been
added
to
simplify
the
experience
of
installing
and
using
SEO.
A
So
first
thing
we
look
at
is:
is
your
cuddle.
We
see
there
are
more
commands
than
just
cube
inject.
We
see
a
few
things
for
doing
debugging
for
verifying
installations
and
and
of
course,
the
manifest
command
that
we're
going
to
take
a
look.
Do
it
right
now?
Actually,
I
just
want
to
make
sure
real,
quick,
all
right,
I
have
a
version
of
this
do
running
already.
I
should
have
cleaned
this
up
one
second,
so
the
the
manifest
command.
A
A
You're
verifying
install,
which
will
allow
us
to
determine
whether
our
cluster
and
the
environment
that
we're
targeting
has
the
minimum
threats
prerequisites
to
be
able
to
install
this
deal,
and
then
once
we
install
it,
we
can
go
back
and
verify
that
yes,
actually
just
was
installed
correctly
or
no
right,
that's
more
important
when
things
are
not
installed
correctly.
You
want
to
know
at
the
at
the
end,
so
just
going
ahead
and
finding
out
later
so
we
deleted
our.
A
Existing
installation,
so
the
first
thing
we're
going
to
do
is:
let's
look
at
that
command.
We
have
a
manifest
apply,
so
there's
a
sudden
command
here
and
we're
gonna
pass
it
a
parameter.
Sets
profile
equals
demo.
So
this
implies
that
there's
there's
some
kind
of
profile
mechanism
or
some
way
of
targeting
specific
pre
curated
sto
packaging.
A
A
And
we
can,
we
can
see
the
applied
cuts
up,
commend
that
waste
on
the
top.
We
also
see
a
couple
other
ones
so
generate
and
migrate
convergence,
and
so
with
with
the
generate
command.
What
we
would
expect
is
that
we
picked
a
profile
and
we
customize
it.
The
way
we
want
I'll
show
you
some
of
the
detail
in
a
second
and
then
we
can
just
generate
the
kubernetes
resources
directly
and
cuba
playa.
So
again
we
don't
have
to
mess
around
with
hell
using
older
helm.
A
You
know
with
tiller
and
all
that
other
stuff
we
can
just
using
the
command
line
that
comes
out
of
the
box,
generate
the
cube
resources
that
we
would
need
to
install
this
dear
now,
because
of
the
dots
in
the
parameter
showed
that
we
can
pass
in
a
profile.
Let's
take
a
look
at
what
that's
all
about.
So
if
we
come
back
here
to
the
hto
fellow
come
in,
we
see
that
there
is
a
profile
command.
Let's
take
a
look
at
that.
A
And
if
we
look
at
the
profile
command,
we
can
see
that
we
can
either
list
Delord
if
the
various
profiles
that
are
available
to
us
that
come
out
of
the
box.
Let's
list
the
profiles
we
have
general
is
the
one
that
we
saw
in
the
in
a
documentation.
But
we
see
we
have
a
couple
other
ones.
We
have
a
default
SDS
or
using
the
SDS
capabilities
for
distributing
secrets
minimal.
There's
something
of
a
remote
installation
I'm
a
little
bit
curious
about
what
is
in
the
minimal
profile.
A
Before
we
do
any
installation,
though
we
do
want
to
take
a
look
at
some
of
the
helper
helper
commands
for
validating
and
sanity
checking
our
environment
before
we
get
going.
So
if
we
do,
if
Co
federal
verify
installed,
this
will
go
through
and
take
a
look
at
our
Q
cluster,
make
sure
the
minimum
communities
requirements
and-
and
that
is
not
already
set
up
and
it
can
take
psych-
are
injecting
web
hooks
and
and
so
forth.
So
everything
looks
good
on
that.
A
So
now,
if
we
wanted
to
manifest
apply,
set
profile
minimal.
If
we
want
to
take
a
look
at
what
this
minimal
profile
looks
like-
let's
just
let's
just
deploy
this
do
like
that,
and
we
can
see
that
under
the
covers,
it's
it's
using
a
few
different
mechanisms
to
shrink
down
the
misty.
Oh,
that
is
one
of
the
things
initially
when
people
got
started,
what
they
see
the
deploy
and
find
you
know
that
it
had
ten
different
components.
A
Let's
look
at
what
it
deployed
and
keep
a
watch
on
that
make
sure
that
it's
running
and
it
will
be
running
soon
hopefully,
but
the
first
thing
we
noticed
is
that
there
isn't
ten
different
components.
This
is
the
most
minimal
deployment
of
this.
Do
that
you
can
get,
and
all
that
is,
is
your
pilot
and
if
you're
not
familiar
eyelet
is
the
component
that
serves
on
boys
configuration
so
it
can
grab
the
API
documents
that
you
create
to
drive
the
mash,
so
things
like
virtual
services
and
destination
rules,
and
so
on.
A
Take
those
documents
and
basically
just
translate
them
into
unvoyage
configuration
that
the
data
plane
can
then
understand.
So
what
this
means
is
it's
a
very
simple
super,
simple
system,
simple
capabilities.
All
it
is
is
a
Envoy
SDS
server
right
and
we
can
do
quite
a
bit
of
video
functionality
using
just
this
this
deployment.
A
You
just
need
the
this
minimal
profile,
so
let's
go
ahead
and
and
delete
that
we're
gonna
come
back
and
deploy
the
full
the
full
demo,
because
I
want
to
show
a
couple
other
other
pieces
here
so
give
that
a
second
to
to
delete,
but
we're
gonna
do
is
we're.
Gonna
wait,
actually
run
this
command
with
profile
equals
demo.
One
thing
that
pop
might
pop
into
your
head
is:
what
are
the?
What
are
the
various
values
that
we
can
configure
here?
All
right,
so
we
can
see,
set
and
we're
supposed
to
being
profile.
A
Equal
demo
with
will
run,
but
what
other?
What
other
values
can
we
can
use
here?
What
can
we
find
that,
if
you
click
on
reference
and
click
on
configuration,
we
get
a
lot
more
detail
about
how
the
ISTE
OCO
command
is,
is
deriving
the
configuration
and
what
configuration
we
have
to
customize
and
so
I'll.
Let
you
read
through
this,
but
the
the
important
to
see
our
knee
that
we
were
interested
in
here
is
still
control,
plane
spec.
A
A
We
also
have
a
few
different
sections
of
the
CR
D,
where
we
can
configure
various
parts
of
the
control
plane
and
then,
lastly,
if
we
want
very
fine-grained
control
over
those
values,
we
can
use
the,
but
we
can
override
and
set
the
values
that
we
would
find
in
the
helm
tablets
using
the
values
here
so
I'll.
You
know,
that's
that's
a
offline
exercise
for
you
all,
but
we
can
see
that
they
see
a
tunnel.
Manifest
command
is
very
customizable
and
you
can.
A
A
And
we'll
give
that
a
second
to
install
now
the
demo
profile
is
going
to
install
more
than
what
we
just
saw,
plus
I
could
go
with
the
minimal
install
so
it'll
install
the
rest
of
the
control
plane.
It'll
install
some
of
the
supporting
components
like
Griffin
ax
for
seeing
telemetry
like
Prometheus
for
capturing
the
telemetry
and
and
so
forth.
So
if
we
do.
A
A
But
what
I
do
want
to
show
is
that
in
the
in
the
past,
it's
been
very
a
little
bit
more
cumbersome
than
necessary
to
try
to
find
all
the
right
you
eyes
and
dashboards
that
that
it
still
has
the
astillero
command
has
as
a
dashboard
sub
command
that
we
can
use
just
apply
that
click
on
that
we
can
see.
We
can.
We
can
pop
up
an
on
delay
web
web
UI
quickly.
A
We
can
get
to
grow
fauna
and
key
Ollie,
and-
and
some
of
these
other
you
eyes
with
your
simple
commands-
sort
of
trying
to
figure
out
exactly
what
port
they're
listening
on
from
version
to
version.
Maybe
the
port's
change
then
sort
of
port
forwarding
session
and
so
on.
So
if
we
just
forget
want
to
take
a
look
at
actor
fauna,
we
can
just
do
this
and
we
should
please
see.
A
A
Then
we
can
see
the
Keala
dashboard
here,
which
is
more
of
an
overview
of
the
various
services
that
are
running
in
the
data
plane
and
the
various
control
plane
components.
So
the
dashboard,
the
dashboard
sub
command
is
the
very
welcome
addition
to
the
user
experience,
especially
when
you're
starting
to
just
kick
the
tires.
Now.
A
A
A
A
This
change
is
intended
and
as
such
tremendous
benefits
and
intended
to
help,
but
it's
not
something
that's
going
to
be
kind
of
switched
on
and
often
and
just
magically
there
right.
So
it's
gonna
there's
going
to
be
an
upgrade
path
to
get
to
it
and
it
will
gradually
be
faced
in
so
we
it'll
be
available
in
1.5
and
you
can
take
a
look
at
it.
A
I'll
show
you
exactly
what
I'm
talking
about,
but
don't
don't
be
worried
that,
oh,
my
goodness,
everything
you
learned
about
this
tio
will
will
now
be
obsolete
because
I
won't
need
the
case,
especially
for
for
me
since
I'm
writing.
A
book
on
this
do
I
am
gonna,
have
to
kind
of
revise
some
of
these
chapters
to
accommodate
these
changes,
but
these
changes
are
are
good.
So
the
first
thing
that
we
want
to
do
is
we
want
to
use
a
snapshot
of
sto
1.5.
So
this
is
a
really
very
alpha.
A
A
There
will
be
an
option
to
condense,
all
of
that
down
into
a
single
fire,
a
single
deployment
so
think
of
the
responsibilities
of
the
Citadel,
which
is
certificate,
signing
request,
request,
signing
I,
mean
and
and
deployment
of
the
certificate
rotating,
the
certificates,
expiring
and
so
forth.
That
will
now
be
merged
into
this
Tod
finer
things
like
the
the
webhook
injector.
We
don't
need
a
separate
weapon.
What
hook
injector?
We
know
we're
going
to
combine
that
with
is
Tod
and
galley
for
doing
API,
validation
and
interchange.
A
Configuration
interchange
with
other
environments
that
will
be
pulled
into
is
Tod
now
the
main
one
of
the
main
reasons
for
doing
that
is
simplifying
operations
of
this.
Do
we,
those
of
us,
have
been
around
the
eastern
community.
We
hear
loud
and
clear
that
the
users
of
this
do
have
found
it
to
be
kind
of
complex
and
complicated
at
times.
A
This
is
an
effort
to
significantly
reduce
that
that
that
reality,
that
the
lore
that
things
are
combined
operationally
it'll
be
easier
to
to
deal
with,
because
what
we,
what
we
found
and
what
we've
seen,
is
that
the
folks
who
are
taking
and
using
and
running
typically
a
single
team
or
sometimes
single
person
right.
So
it
there's
not
much
advantage
to
deploying
as
a
sprawling
set
of
micro
services
when
as
a
single
team
operating
the
steel
installation.
A
So
if
we,
if
we
can
merge
things
down
into
a
single
binary,
it'll
be
easier
to
operate,
it'll
be
easier
to
upgrade
it'll,
be
easier
to
configure
at
runtime
and
and
ultimately,
to
maybe
run
multiple
of
these
control
planes
and
multi-tenant
environments
and
so
on.
So
if
Zod
is
a
big
step
forward,
I
believe
in
simplifying
some
of
the
unnecessary
complexity
that
we
have
in
this
do
today,
and
let
me
let
me
show
you
what
that
might
look
like
and
steel
1.5.
A
We
are
we're
using
a
snapshot
that
was
built
yesterday,
so
this
demo
goes
sideways.
That's
my
problem.
We're
still
we're
still
waiting
for
some
stable
releases
here.
So
the
first
thing
that
we're
going
to
do
is
install
SCO
1.5
and
we're
going
to
we're
going
to
trim
those
extra
control,
point
components
and
we're
going
to
use
the
sto
D
deployment
of
the
controller.
So
first
thing
that's,
this
is
going
to
be
very
difficult
to
text.
So
let
me
just
let
me
just
copy
and
paste
this
and
again.
A
This
is
not
the
final
product,
there's
quite
a
few
values
that
we
have
to
set
here,
that
we
have
to
to
an
inch
crimp
and
so
on
the
way
I
said
this
is
a
snapshot
very
early
release
of
this.
So
some
of
this
will
get
a
lot
of
us
will
get
ironed
out,
but
a
couple
of
other
values
you
can
see
that
we're
setting
here
is
we're
going
to
use.
A
The
so
we're
getting
rid
of
mixer.
So
if
you've
heard
this
in
the
past
the
mixer
component,
first
of
all,
it
was
split
into
telemetry
and
policy,
and
a
little
by
little,
the
capabilities
of
those
two
components
in
the
control
plane
have
been
it
emerged
into
envoy
or
into
the
data
plane
itself
or
leveraging
native
capabilities
that
we
don't
need
separate
components
order.
So
we're
gonna
we're
going
to
enable
v2
of
this
implementation.
A
We're
gonna
turn
off
a
bunch
of
different
components,
and
then,
lastly,
we
are
going
to
use
a
newer
version
of
the
installation
package
that
these
videos
ever
covers.
Just
to
be
able
to
do
this,
so
let's
see
what
that
does
we
use
the
ISTE
Oh
manifest
generate
command
there.
You
can
see
that
it
spit
out
a
bunch
of
yeah
before
us
now.
What
we
were
just
going
to
do
is
cue.
A
A
We'll
give
that
a
second,
but
what's
immediately
noticeable,
is
that
there's
only
two
pods
there
are
only
two
pods
deployed
here,
everything's
running
successfully
now
excellent.
So
there
are
only
two
pots
deployed
here:
one
is
the
ingress
gateway,
and
once
the
pilot
now
is
Tod
is
a
representation
of
the
the
single
daemon
that
we're
going
to
use
for
is
Siva
right
now,
things
that
have
been
renamed,
things
are
still
called
Pilate
and
the
functionality
of
the
rest
of
the
control
plane
has
been
merged
into
Pilate.
A
In
this
case
we
have
a
reduced
number
of
moving
pieces
and
complexity,
but
we
have
introduced
a
feature
step
feature
set.
We
still
get
things
like
the
automatic,
you
know
cyclone
injection
or
we
we
still
get
the
the
security
of
mutual
TLS
and
and
of
course
we
get
to
traffic
crowding
so
but
because
Pilate
I
was
already
doing
that.
So,
let's
take
a
look
at
applying.
Let's,
let's
do
this,
we
don't
have
any
plugs
running
in
the
default
namespace.
A
If
we
do
take
a
look
at
the
namespace
will
notice.
One
important
thing
is
that
the
ISTE
Oh
injection
annotation
is
set.
So
now.
If
we
deploy
the
book
info
application
to
the
default
namespace,
we
should
see
those
pots
automatically
get
there
they're
the
data
plane
injected
into
them.
Even
though
you
see
that
there's
no
web
hook
running
running
here
right.
This
is
all
it's
now
embedded
inside
of
a
pilot.
So
if
we
do,
let's
see
if
we
can
do
looking
for
delete.
A
A
A
A
A
Now,
that's
you
know
quite
nice
to
the
reasoning
really
early
early
snapshot,
things
here.
Okay,
so
now
we
should
be
to
the
simple
bookstore
app
alright
from
here.
We
can
follow
the
rest
of
the
the
tutorial
on
booking
phone,
which
I
won't
do
here.
Well,
another
thing
that
I
do
want
to
show
you
and
the
last
thing
that
I
want
to
show
you
is
we
when
we,
when
we
first.
A
The
commandment
used
to
install
sto
in
the
EOD
matter
we
enabled
v2
of
telemetry.
Now
in
v2
it's
a
logically.
We
don't
need
the
the
mixer
or
the
telemetry
policy
parts
of
Visio
right,
and
we
can
see
that
none
of
those
are
right.
The
way
that
some
of
the
telemetry
components
were
implemented
was
by
using
web
assembly
and
building
the
capabilities,
some
of
the
capabilities
of
extending
the
Envoy,
stat
and
and
and
the
list
of
stats
that
on
Blinky's
by
doing
that
with
webassembly.
A
A
A
A
Let's
look
for
assembly
configuration
and
I
think
we
see
that
one
for
HTTP,
but
then
we
also
see
the
the
configuration
for
for
the
stats.
So
what
this
stats
config
with
this
moment,
configures
it
is
doing,
is
loading
up
a
module
that
handles
creating
the
additional
statistics
that
we
want
to
keep
for
SEO
and
those
those
could.
Those
stats
are
going
to
be
prefixed
with
sto
underscore
or
dot
is
steel
underscore
or
something
so
itself
which
isn't
in
the
default
or
base
envoy
configuration?
A
So
if
we,
let's,
we
can
come
back
here
and
take
a
look
at
the
stats
Prometheus.
We
should
we
worked
correctly,
so
we
start
to
see
the
ISTE
underscore
request.
So
these
are
the
different
statistics
that
were
originally
generated
by
mixer
out
of
process
of
envoy
now
they're
being
through
to
this
web
assembly
extension
and
without
any
other
process,
manipulations.
A
They're
being
generated
inside
the
proxy
itself,
so
in
this
this
you
know,
quick
little
review
of
some
of
the
stuff
is
coming
1.5.
We
we
showed
that
the
control
plane
and
the
complexity
of
the
control
plane
has
has
been
improved
like
and
it
slimmed
down
the
components
that
we're
running
as
a
complementary
components
to
each
other,
collaborating
components
with
each
other
they've
been
merged
into
a
single
binary
to
the
extent
that
they
can
and
some
of
the
stuff
is
it
pushed
actually
into
the
data
plane
itself.
A
So
you
know,
if
you
know,
one
up:
five
release
will
be
coming
like
I
said
in
mid-february
sometime
around
then,
and
if
you
have
any
questions,
are
you
interested
in
getting
started
with
steel?
Take
a
look
at
it
from
a
more
simplified
perspective
than
definitely
go
to
the
Bustillo
dot
IO.
The
community
is
very
a
connecting
of
solids
from
the
top
five
fastest-growing
projects
on
on
github
come
down
here.
Take
a
look
at
the
community
tab
and
get
involved,
so
feedback
on
is
tio
1.4
1.5,
appreciated
feedback
on
this
initial
episode
of
hoops
also
appreciated.