►
From YouTube: Clojure visual-tools meeting 13 - interactive datavis: Shiny, Clojurescript Bayesian animations
Description
In this Oct 14th, 2022 meeting of the Clojure visual-tools group, we had two presentations about interactive data visualizations:
- Adham Omran gave an overview of the Shiny R package for interactive data visualizations, demonstrated through a geospatial analysis use case.
https://shiny.rstudio.com/
- Jamie Pratt presented the use of Clojurescript for interactive animations of Bayesian inference, a project done in the Jointprob study community.
https://jointprob.github.io/jointprob-shadow-cljs/
Following the presentations, we also had a discussion of the current Clojure data visualization ecosystem
A
Hello,
this
meeting
is
meeting
13
of
the
visual
tools
group,
where
different
closure,
Library
creators
and
Tool
creators
and
users
need
to
discuss
experiences
and
working
prop
progress
projects
and
discuss
collaborations
and
hopes
for
the
future.
Today
we
will
have
two
interesting
talks,
one
by
Adam
about
the
shiny
framework
of
the
r
ecosystem
for
interactive
database
organizations
and
another
one
by
JD
about
creating
interactive
animations
in
closure
script
for
some
Bayesian
inference
and
as
always,
we
will
Begin
by
introducing
ourselves.
A
B
B
A
C
C
C
Perfect
perfect
yeah
thanks
Daniel
I'm
happy
to
be
here.
Actually
it's
my
first
time
to
be
here
and
around
the
glory.
Community
I'm
I'm,
mainly
I'm,
currently
like
data
science
and
and
research
associate
currently
based
in
in
Istanbul,
but
I
have
finished
my
master's
degree
in
computer
science
from
Armenia
American
University
of
Armenia
I'm,
mostly
doing
all
the
I'm
on
the
data
analysis,
side.
Obviously,
I
know
this
is
a
small
part
from
of
your
community,
but
I'm.
Mostly
now
doing
my
data
analysis
in
in
R.
C
A
Thank
you
so
much
so
nice
to
meet
for
the
first
time,
and
you
know
to
you
and
to
anybody
who
is
new
to
closure.
This
community
is
really
looking
to
create
a
good
experience
for
you.
So
if
anything
is
difficult
or
confusing
or
blocking,
then
let
us
talk.
Let
us
chat
afterwards
and
see
how
we
could
make
it
easier
for
you
to
to
be
part
of
this
and
wonderful
to
meet
and
Adrian.
Would
you
like
to
get
something.
C
C
E
Yes,
hello,
everyone
I
am
a
data
analyst
with
a
background
in
finance.
I've
worked
with
r
for
the
past
two
to
three
months
and
I've
gotten
into
closure.
In
the
past
couple
of
weeks,
loving
the
ecosystem,
there's
a
lot
of
have
a
lot
of
interesting
visual
tools
and
in
building
what
ways
to
visualize
data
to
get
and
gain
insights
from
the
data
and
I
think
the
way
closure
treats
data
lends
itself
well
to
how
data
is
processed
and
manipulated
and
visualized.
So
it's
interesting
being
in
this
community.
F
I
might
be
able
to
learn
enough
closure
and
closure
script
to
to
produce
something
of
value
for
people
all
right,
I,
really
like
the
working
with
a
language
that
has
a
a
strong
philosophy
behind
it
and
and
it
it
yeah.
I
I
love
the
the
idea
of
of
separating
out
processing
yeah.
That's
it
Moodle
yeah
processing
processes
and
processing
and
transforming
data
to
app
to
State.
F
A
Thank
you
so
much
yeah,
so
I
guess
now
we
will
go
about
the
presentations
by
Adam
and
JV
and
we
have
about
75
minutes
to
the
official
time.
So
we
have
lots
of
time.
So
each
of
you
could
say
talk
and
discuss
your
topic
for
about
half
an
hour,
and
then
we
have
15
more
minutes
to
to
chat
further
and
maybe
then
stay
later
on.
If
anybody
wishes
to
stay
and
but
I'm
just
saying
that
so
that
you
know
we're
flexible
and
we
could
change
the
process
to
see
how
we
go
and
yeah.
C
E
I'll,
be
mainly
talking
about
the
concepts
behind
shiny
and
telling
an
experience
of
using
shiny
and
a
real
world
project,
and
the
many
aspects
that
makes
shiny
interesting
to
work
with
first
of
all,
shiny
Works
in
RR
is
a
language
for
successful
Computing
Graphics.
It's
a
free
and
open
source
language.
It
has
a
lot
of
statistical
functionality
built
into
its
core,
so
it
lends
itself
well
to
use
by
statisticians
and
like
what
I
love
about
R
is
like
there's.
E
You
can
quickly
start
working
with
it
like
you
get
the,
for
example,
data
and
CSV
format.
You
can
quickly
build
plots.
The
language
is
easy
to
read
it's
based
on
S.
It's
inspired
by
scheme
which
I've
like
learned
about.
While
I
was
doing
research.
There
is
some
inspiration
from
best
languages
and
art.
It's
used
for
this
wrangling,
manipulation,
visualization
analysis
and
research
in
many
fields,
Finance
medicine,
and
it's
also
used
for
building
dashboards
cool
things
of
what
are
like.
This
is
what
made
me
stick
to
art
for
a
long
time.
E
Ripple
raffle,
driven
development
similar
to
closure.
You
can
just
work
in
the
rebel
manipulate
your
data
visualize
it
quickly.
It
shortens
the
time
between
thinking
and
getting
things
out
like
this
ability
to
just
immediately
work
with
your
data
makes
it
very
fun
to
work
with
it's
extensible.
You
can
write
packages
for
R
and
the
ecosystem
is
very
large
and
very
active
and
expanding
many
packages,
such
as
the
thigh,
diverse,
shiny
and
Netter
title
versus
a
basically
Universal
packages
for
manipulating
and
visualizing
data.
E
Ggplot2
is
one
of
the
most
famous
visualization
packages
for
our
Chinese
buffet
about
today,
and
Netter
enables
you
to
basically
do
literary
programming
where
you
have
documentation,
have
code
blocks,
knit
them
together,
export
that
to
HTML
PDF
and
show
that
off
very
quickly,
and
my
fate
like
this.
This
is
very
fun,
the
piping
macro,
which
is
basically
for
closure
users.
It's
a
thread
first
macro
where
you
write
an
expression
and
you
pipe.
The
output
of
the
expression
to
the
expression
that
follows
so
filter
to
plot
and
so
on.
E
E
Shiny
embodies
the
easiness
in
terms
that,
once
you
know
r
reading
a
bit
about
shiny,
you
can
use
shiny
to
build
a
web
application
with
little
to
no
web
background
and
that's
a
very
powerful
thing.
And
it's
one
of
the
points
that
I'll
discuss
about
in
my
like
ideas
for
like
a
shiny
enclosure.
It
has
reactivity
built
in
so
the
application
reacts
to
the
users,
changes
and
inputs
without
having
to
write
JavaScript
and
like
basically
without
getting
your
hands
dirty
with
JavaScript.
E
You
can
write
R
and
have
that
deal
with
the
interaction
shiny
has
modules
which
enable
you
to
reuse
and
organize
code.
I'll
show
a
demonstration
of
how
useful
modules
can
be
later
on,
but
they
enable
the
user,
the
developer
or
a
team
of
developers
to
work
together
on
a
project
and
have
no
interference
between
them
and
basically
one
person
can
write
module
a
another,
characterized
module,
B
and
another
current
module
C,
and
they
all
develop
together
and
incorporate
the
modules
into
a
single
big
application.
E
E
Users
tend
to
go
for
Frameworks
such
as
Golem,
which
is
used
to
build
robust
Shrine
applications
and
it
models
the
application,
nlr
package
format
with
an
R
directory,
a
Dev
directory
and
directories
for
our
development
I'm
not
going
to
get
into
the
details
of
those
because
that's
unnecessary
for
like
seeing
the
big
picture
of
shiny.
But
it's
a
Well
organized
system
and
I'll
come
back
to
this
later
on.
E
When
talking
about
like
the
Simplicity
principle
of
closure
and
how
that
can
get
into
the
in
the
way
of
new
developers
such
as
me,
because
I'm
the
disclosure,
the
process
of
building
an
application
with
shiny,
is
very
simple,
you
design
your
UI,
you
build
with
the
modules
and
you
incorporate
everything
together.
It's
straightforward
to
get
started
with
reactivity
and
modules.
E
E
E
This
is
great
because
after
learning
or
you
can
immediately
start
building
applications
that
you
can
show
and
that
you
can
put
on
your
portfolio
or
show
your
experience
with
and,
of
course,
your
ideas
will.
Reactivity
basically
describes
the
simple
yet
very
powerful
mechanism
behind,
for
example,
choosing
a
data
set
and
having
all
the
data
changes
with
the
choice
of
the
user.
E
E
E
E
So
an
input
is
where
something
the
user
can
change
and
an
output
is
something
the
user
can
see
and
they
outputs
can
interact
with
the
inputs
through
your
reactivity
here,
the
server
function
simply
runs
a
reactive
switch
which
updates
on
the
user's
input.
So
it
goes
for
all
data
sets
and
for
another
way,
even
simpler
demo.
E
So
how
does
this
all
happen
in
shiny?
There
are
three
components
to
reactivity:
we
have
reactive
values,
reactive
expressions
and
Observers.
The
reactive
values
are
values
the
user
can
interact
with
and
that
the
user
can
change.
They
are
the
source
of
reactivity
and
they
can
be
linked
to
an
expression
or
an
observer.
E
E
E
A
E
Yeah,
like
these
are
processed
all
on
the
server
side,
like
the
expressions
these
all
live,
like
the
the
declaring
of
Expressions
lives
in
the
server
side
of
the
application.
So
when
you
have
a
UI
site
and
a
server
side,
all
this
is
declared
and
happens
in
the
server
side.
So
the
user
does
like
declare
what
gets
updated
reactively
and
they
choose
where
that
output
is
where
it
goes.
So,
for
example,
in
the
demo
I
show
it
goes
into
the
table.
E
F
E
C
E
E
F
F
Interesting
because
I
was
just
thinking
of
this
compared
to
what
I'm
going
to
present
later,
where
closure
script,
the
closure
script
compiler
itself,
determines
you,
have
your
state
for
the
application
and
the
I
I
create
an
erective,
a
react
application
where
the
compiler
determines
what
needs
to
be
updated.
When
the
Slate
changes
all
of
your
functions,
there's
not
a.
E
So
you
know
how
the
resources
are
gonna
work
out
but
like
if
the
compiler
determines
I,
don't
know,
what's
going
to
be
reactive
and
what's
not
going
to
be
reactive.
So
how
will
the
load
the
balance
and
all
that
and
I
have
to
reiterate
I'm
a
beginner
enclosure,
so
state
is
still
just
a
bit
beyond
minus
my
understanding
but
I'm.
Getting
there.
E
E
E
E
E
A
single
closure
file
represents
a
module
with
its
UI
and
server,
and
then
that
gets
called
or
maybe
I,
don't
know
exactly
how
to
I.
Don't
know
how
to
see
modules
enclosure
yet
so
I'll
demonstrate
them.
I'll
show
some
structure
for
them,
and
I
can
hear
from
the
people
with
more
experience
in
closure
how
this
can
be
implemented.
E
Chinese
ecosystem
is
large.
It
has
Golem,
which
is
a
framework
for
building
shiny
applications.
It
has
shiny
dashboard,
which
is
and
yet
another
abstraction
that
helps
with
the
building
dashboards.
So
with
shiny
dashboard
and
bs4
dash,
you
basically
declared
the
layout
and
then
you'll
have
the
entire
application
and
I'll
show
that
and
I've
been
talking
a
lot
about
showcases,
so
I'll
be
showing
a
real
world
new
scenario
of
shiny
Golem
and
dashboarding.
E
E
Each
of
these,
the
map,
the
circles
and
the
bar
graphs-
are
a
module
so
When
developing.
We
were
three
developers
working
on
the
project
and
the
supervisor
is
real.
Who
is
present
with
us,
and
two
of
us
worked
on
the
back
end.
Basically,
and
the
third
developer
worked
on
the
UI
of
the
entire
application.
So
what
happens
is
the
the
UI
is
written
and
the
back
end
is
plugged
into
the
UI.
So
here,
for
example,
we
have
this
map
module,
which
is
a
leaflet.
E
E
E
The
code
here
interacts
with
a
basically
a
dollar
quality
CSV
file,
because
it's
it's
a
binary
for
R,
which
makes
the
loading
of
the
data
quicker,
but
basically
the
State
updates.
Whenever,
like
the
state
of
the
application
updates,
whenever
a
any
input
is
changed-
and
this
happens
across
the
all
the
modules.
E
E
C
E
The
experience
with
shiny
has
a
lot
of
pros
and
cons.
The
main
Pro
is
that
we
used
what
we
already
know,
which
is
R
to
build
this
application
and
the
cons
are,
we
don't
know
web
development
so
when
we
wanted
to
modify
some
elements
such
as
the
bars
on
the
right
on
the
left,
we
wanted
to
put
them
on
the
top.
We
had
to
get
our
hands
working
with
JavaScript,
and
that
was
too
much
work
to
modify
such
a
simple
element
that
we
just
opted
to
not
deal
with
it.
E
How
would
we
present
shiny
enclosure
because
shiny
abstracts,
a
lot
of
code
which
can
lead
to
issues
when
the
developer
wants
to
change
something
as
simple
as
a
where
an
element
is
I've?
Seen
work
with
the
collages
which
Danielle
I
think
you
worked,
you
worked
on
yeah
it
it's
not.
The
interoper
is
with
are
not
training,
sorry
for
the
grammar
here.
It
basically
leaves
the
r
abstraction
in
r
and
brings
the
interop,
and
you
just
basically
call
the
functions
and
call
to
the
same
structure.
E
I
thought
about
reagents
and
providing
templates
to
use
shiny,
like
capabilities,
or
you
basically
declare
aoi
or
like
in
the
reagent
element.
You
create
the
UI
element
and
then
you
embed
the
insert
the
reactive
functionality
in
that,
but
that
also
needs
more
discussion.
So
and
another
question
came
to
mind,
which
is
from
my
understanding
of
the
closure
ecosystem.
It's
mainly
Library,
based
rather
than
framework
based
when
I
started
working
on
a
project.
E
I
found
myself
searching
for
libraries
rather
than
picking
a
framework
and
working
with
it,
so
with
shiny
enclosure
even
be
plausible,
like
who
would
use
a
complete
framework,
such
as
shiny
enclosure,
I
think.
The
main
use
case
for
this
is
for
people
new
to
closure
who
want
to
get
applications.
Running
quick
like
me,
like
just
maybe
a
number
of
kindly
functions
that
ease
up
the
operation
or
a
framework
in
itself.
So
I
want
to
hear
any
questions
if
there
are
any
and
what
would
an
a
framework
like
shiny,
look
like
enclosure.
A
Thank
you
so
much
yeah.
Thank
you.
You
know
for
bringing
Clarity
to
this
topic,
which
you
know
for
me
has
been
confusing.
Always
and
now
you
draw
the
picture
for
us
about
it
and
also
such
an
inspiring
use
case
to
see
and
and
yeah.
It
would
be
great
to
discuss
these
questions.
Maybe
it
makes
sense
after
Jamie's
presentation,
where
we
see
free
agent,
for
example,
so
we
have
a
little
taste
of
how
it
looks
like
in
Florida
Street.
A
B
E
On
the
reading
list,
the
okay,
so
for
a
quick
background
and
what
I
already
know
about
closure,
I'm
going
through
the
I
finished,
the
getting
started,
guide
and
I
started
going
through
the
reference.
I
read
the
reader
I
know
about
the
raffle.
How
evaluation
happens
I'm
still
far
from
atoms
agents,
vars
and
references.
So
do
tell
me
how
closure
deals
with
the
this
I'm
happy
to
learn.
So,
okay,.
B
F
I
don't
know,
maybe
maybe
we
could
delay
this
till.
We
were
looking
at
my
app
because
it's
a
it's
a
reagent
app
with
States
maintained
in
atoms
and
we
I
I
might
not
do
Justice
to
explain
it
very
well.
So
maybe
if
anyone
else
wants
to
chime
in
to
to
explain
things
better
than
me,
then
let's
have
a
discussion
about
about
closure
script
and
how
it
works.
Based
on
looking
at
my
app
as
an
example
of
I
that
might
be
better
than
it
might
be
better.
A
C
A
B
Be
useful
at
this
point:
okay
I'll
just
see
if
it's,
if
this
works
done,
I
I
agree,
Jimmy
you're
definitely
going
to
touch
on
this.
So
I,
don't
know
whether
I'm
going
to
provide
anything
and
I'm.
Also
seeing
that
my
share
screen
button
from
Zoom
doesn't
do
what
I
expect
so
I,
don't
think
I'm
going
to
be
able
to
share
my
screen
regardless
so
yeah
I
suggest
we
just
keep
going.
E
How
easy
do
we
want
to
make
it
for
closure
users
to
work
because
well
learning?
There
are
many
like
build
systems
like
devstate,
Eden
and
lining
and
I
had
to
learn
about
those
one
going
for
a
database.
I
had
to
learn
about
the
like
three
libraries,
closure.gdbc
and
jdbc
next,
and
that's
a
lot
of
like
learning
to
get
going
with
a
topic
as
simple
as
like
working
with
a
with
some
UI
in
the
web
and
reagent
is
simple,
but
it
still
requires
some
learning.
E
D
I
think
part
of
the
there's
some
there's
typically
some
trade-offs
there,
where,
when
you
simplify
things,
you
often
end
up
with
more
options
which
makes
it
harder
to
learn
and
there's
what
you
try
to
do.
Is
you
try
to
make
simple
things
and
then
you
try
to
find
the
common
use
cases
and
then
have
packages
of
the
simple
things
and
a
lot
of
the
other
ecosystems
have
much
bigger
communities,
and
so
they
can
package
the
different
options,
much
more
rightly
because
they
just
have
more
people
working
on
it.
A
Yeah
it
is
such
a
central
question,
so
everything
we're
doing
and
and
yeah
I
think
the
truth
is
we
don't
have
anything
like
shy.
There
are
a
few
things
which
are
interesting
steps
in
that
direction,
but
something
as
complete
this
kind
of
experience
that
you
demonstrated
well,
one
actually
does
not
need
to
know
anything
about
web
development
that
actually
go
very
far
this
way.
That
is
something
that
we
don't
have
incred
ible
at
the
moment,
and
there
are
a
few
interesting
attempts
like
that
area.
I.
D
D
I
think
closure
does
a
good
job
of
making
it
easy
to
make
simple
things,
whereas
other
ecosystems,
don't
necessarily
do
that.
So
basically
you
get
one
framework
or
two
Frameworks,
because
it's
so
hard
to
do
anything
that
basically
everybody
built
on
top
of
react
or
whatever
the
the
main
thing
is
where's
enclosure,
it's
easier
to
make
simple
things.
D
D
Think
a
lot
of
other
ecosystems
basically
just
like
they
have
one
option
and
it
does
the
one
and
everybody
kind
of
works
on
the
one
one
framework
and
it's
tough
for
closure,
because
obviously
you
do
want
you,
you
do
need
new
people
coming
to
closure
and
trying
things
but
kind
of
packaging.
Those
common
use
cases
is
still
a
lot
of
work
because
it
takes
a
lot
of
Polish
and
there's
a
lot
of
like
drudgery.
D
There's
the
what
which
is
like
you
have
all
the
different
steps
and
how
they're
all
their
dependencies
they're.
How
they're
connected
so
a
depends
on
B
depends
on
C,
which
may
depend
on
two
different
steps.
So
you
have
the
what
and
you
really
want
to
enclosure
the
way
is
you
really
wanted
that
separated
from
how
so
there's
multiple
ways
to
implement
that
you
can
use
the
watches
that
teodora
has
mentioning,
but
you
know
there's
also.
D
B
Yeah
I
I
want
to
follow
on
on
what
a
lot
of
people
have
been
saying
here.
I
think
one
of
the
challenges,
because
closure
is
so
flexible
and
we
want
there's
a
lot
of
us
that
value
that
flexibility
and
that
composition
and
there
is
to
choose
to
do
they-
make
the
easy
thing
where
so
many
people
that
have
self-selected
into
closure
are
reluctant
to
cut
off
the
paths
that
are
necessary
to
make
the
easy
thing
like
design
is
choice
right.
B
You
have
to
make
a
choice,
and
a
lot
of
us
are
saying
well
I
want
those
options
available
and
being
able
to
own
that
design,
choice
and
say
look.
This
is
what
I
want
to
accomplish
and
and
not
necessarily
feel
like.
You
need
to
apologize
for
that
you're
not
going
to
be
everything
to
everybody,
that's
what
the
general!
That's!
What
closure
the
language
and
the
ecosystem
is
for
like
saying
you
have
a
shiny
application.
Sorry,
but
now
the
pun
on
shiny
is
making
me
smile.
B
The
the
use
case
for
shiny
is
incredibly
valuable
right.
It's
not
going
to
be
everything
to
everybody
and
to
say
look.
This
is
what
we're
doing
and
for
both
for
people
on
the
outside
saying
I
want
all
of
this
configuration
that
can
be
really
hard
for
a
developer.
To
say:
look,
that's
actually
just
not
what
I'm
trying
to
do
here.
I
recognize
what
you're
trying
to
do.
B
It's
not
actually
part
of
our
project
and
navigating
that
is
difficult,
but
I
think
to
have
a
successful
I
would
actually
call
shiny
more
of
an
application
as
opposed
to
a
framework
or
like
shiny
itself
being
an
application,
because
it's
got
so
many
design
choices
already
made
in
it.
I
think
that's
perfectly
valid
and
just
owning
that
and
saying
hey.
This
is
what
we've
decided
we're
going
to
do.
B
We
recognize
these
other
trade-offs
being
upfront
and
honest
about
them
and
saying
yes,
this
is
what
we're
doing
and
we're
going
to
do
an
excellent
job
at
it.
So
that's
my
my
take
on
the
whole,
we
need
both
and
it's
not
one
or
the
other.
It's
like.
No.
We
got
to
recognize
that
there
are
both
use
cases
I'm,
seeing
the
same
place
in
the
note-taking
community
right
now,
it's
like!
Oh,
we
want
to
do
all
of
these
things.
It's
like
none
of
you
are
good
at
anything
in
particular.
A
F
C
F
F
Yeah
I
I
thought
this
was
a
good
that
the
motivation
to
create
this
thing
was
to
to
explore
the
ideas
that
I'm
learning
about
in
in
relation
to
Bayesian
statistics,
where
I'm
taking
part
in
a
study
group
with
which
Danielle
set
up
where
we're
going
through
the
wonderful
book.
Statistical
rethinking,
which
presents
Bayesian
approach
to
a
very
practical
Bayesian
approach
to
statistics
and
I
thought:
I'd
kill
two
birds
with
one
stone:
I'd
I'd
use
this
as
a.
F
F
F
F
F
F
F
F
With
each
with
each
sample,
oh
yeah,
I,
don't
know
how
to
how
far
to
go
into
explaining
base
theorem
I'm,
not
gonna,
add
I,
don't
think
that's
the
place
for
this,
but
yeah
I
I'm,
not
gonna,
try
and
explain
what
you're
it's
too
much
of
what
you're
seeing
here.
I
I.
Don't
think
you
want
an
explanation
of
a
base
yeah,
but
it's
not.
C
C
F
F
F
F
F
There
are
these
graphs
are
we're
using
Vega
the
Vega
likes
Library,
which
is
I,
think
it
takes
its
inspiration
from
ggplucks
the
the
grammar
of
Graphics
in
in
ggplot,
the
the
Vega
lights.
Here's
a
similar
grammar
Graphics
approach,
but
the
the
graphs
are
described
in
in
Json
in
a
Json
data
structure,.
C
C
F
F
And
close,
the
script
allows
us
to
do
because
it's
a
functional
programming
language
as
I
was
saying
earlier.
I
really
like
this
concept
of
separating
out
your
state
and
I.
Think
that
the
the
storage
of
the
the
memory,
I
guess
I
think
of
it,
is
the
memory
component
of
your
application.
The
the
thing,
the
the
parts
of
your
application
that
can
that
store
that
that
that.
F
F
F
F
F
C
F
And
the
the
reagent
Library
knows
that
when
this
this
part
of
the
atom
changes
that
this
HTML
part
of
this
HTML
needs
to
be
re-re-rendered,
so
I
think
what
it
does.
Is
it
it
re-renders
the
HTML
and
decides
what
parts
need
if
there's
differences
and
if
the
what
parts
need
changing
I'm,
not
completely
clear.
F
F
F
F
F
A
F
A
B
A
Yeah,
so
so
pretty,
thank
you
so
much
Jamie
we
were
seeing
these
two
ends
as
as
Theodore
mentioned
it,
and
we
will
keep
learning
I
think
about
the
Arctic
system.
There
is
hope
to
have
a
session
about
this
cuarto,
instead
clearance
programming
framework,
which
is
common
in
the
r
ecosystem,
and
maybe
Kira,
would
like
to
comment
about
it
today
or
some
other
time
and
in
general,
we'll
keep
learning
about
other
ecosystems
and
does
anybody
have
any
comments
or
question
about
the
whole
session
if,
before
we
end
the
official
part.
A
E
E
Think
there's
a
lot
to
be
thought
about
in
terms
of
like
maybe
introducing
different
layers
or
levels
of
easiness
to
using
closure
to
create,
maybe
dashboards,
maybe
web
applications
for
visualization
and
then
having
the
ability
to
remove
the
layer
and
expose
the
code
and
have
that
be
customizable.
There
is
a
lot
more
to
be
discussed
and
I
am
enjoying
the
Journey
of
learning
about
closure,
the
ecosystem
and
all
of
this
thank.