►
From YouTube: hyper TSC meeting 4-20-2021
Description
In this meeting we discuss
* the hyper roadmap
* review the progress of the new site
* discuss strategies for the hyper/client
A
And
make
sure
I've
got
it
recording
and
get
started
thanks
for
joining
still
working
on
the
roadmap
that
I
kind
of
put
together
just
a
quick
update
on
that.
A
Basically,
and
and
thanks
for
everyone
that
that
did
give
feedback
on
the
the
new
site
that
that
I'm
working
on,
is
there
any
comments,
or
did
anyone
not
get
a
chance
to
check
it
out.
A
Okay,
let's
see,
I
think
I
can
pop
it
in
the
chat.
A
I
think
it's
and
and
and
most
of
the
screens
are
just
mobile
at
this
point
and
it
was
really
interesting.
Let's
see
on
render.com,
I
think
that's
it.
A
A
So
still
working
on
the
responsive,
kinks
a
little
bit,
but
but
for
the
most
part
I've
got
the
main
page,
pretty
good,
so
that's
svg,
and
that
this
svg
was
probably
the
biggest
pain
point
with
it.
A
So
it
kind
of
draws
down-
and
it
comes
to
this
little
graphic
here
and
you
can
switch
in
between
the
ports
and
this
this
svg
is
supposed
to
like
draw
all
the
way
down
to
each
one
of
these
boxes,
so
different
screen
sizes.
A
A
You've
got
your
menu
up
here
that
pops
in
it's
kind
of
nice
and
then
I'm.
A
Learning
tailwind
and
svelte
kit.
At
the
same
time,
I
learned
that
I
probably
should
have
approached
this
differently.
I
probably
should
have
done
all
the
mobile
first
and
then
did
the
desktop,
but
here's
the
mobile
and
you
can
switch
between
the
ports,
which
is
pretty
cool
and
then
you've
got
the
faq
section
testimonials
and
a
footer.
A
A
A
B
A
Yeah,
there's
yeah,
you
can
just
pop
it
in
the
channel.
I
think
that's
that's
fun.
A
There's
a
website
there's
a
website
channel
got
it
got
it
got
it.
B
Yeah
also
when
you
are
getting
getting
a
little
further
along
and
want,
or
whenever
you
want,
an
accessibility
pass,
I've
done
a
hell,
a
lot
of
that
in
the
past
year
and
some
training.
So
I
got
you.
A
No,
that
would
be
awesome,
so
my
current
kind
of
plan
is
is
to
to
get
the
the
pixel
design
down
on
the
first
phase
of
I
feel
like
I'm
in
a
good
spot,
and
then
this
week
desktop
and
and
try
to
knock
out
the
responsive,
desktop
and
then
hit
the
the
copy
and
a
little
bit
more
of
the
functionality.
A
A
You
know
like
the
faq
questions
and
some
of
the
developer
setup
stuff,
basically,
content
that
might
change
to
to
tweak
in
in
instead
of
instead
of
messing
with
a
full
cms
or
instead
of
messing
with
like
markdown
and
json,
because
it's
kind
of
structured
data,
it
doesn't
really
make
a
lot
of
sense
to
be
marked
down
most
of
it.
But
I
don't
know.
A
Yeah,
I'm
kind
of
open
to
both
approaches
and
looking
at
at
both
to
try
to
you
know
and
I'm
trying
to
think
about
like
when
things
are
changing.
Is
it
is
it
just
this?
You
know
simple
to
redeploy
re-push
or
you
know
just
to
grab
grab
from
the
database.
Since
you
know
it's
it,
it's
not
going
to
get
billions
of
hits.
So
I'm
not
you
know,
I'm
not
worried
about
yeah,
I'm
really
not
worried
about
performance
from
coming
from
a
cms
and-
and
I
can
cache
it.
So
I
don't.
B
Yeah,
I'm
thinking
about
like
search
engine
and
stuff
because
I
know
like
google
and
them
say
that
they
deal
with
you
know
asynchronous
stuff,
but
I'm
trying
to
think
of
it
like
if
the
faq
and
other
things
have
like
marketing
knee
stuff
in
them,
yeah
yeah.
So
that's.
A
So,
what's
what's
really
cool
about
sveltkit
is
that
ssr
is
like
built
in
so
every
single
remote
query:
it'll
always
pull
the
full
html
down.
So
so
from
an
seo
perspective.
There's
really
no
differences.
It's
really
more
of
a
preference
from
you
know.
Do
I
want
to
go
and
update
it
and
then
submit
a
a
push
to
deploy,
or
do
I
want
to
just
you
know,
write
a
record
in
a
database
and
then
then
it's
live
right.
So
really
it's
just
a.
A
Sorry
is
is
probably
that
that
review
and
you
know,
hit.
A
You
know
there's
so
many
like
android
devices
hit
like
the
web
page
test
and
generate
like
all
the
screens
and
and
start
tweaking
that,
but
so
some
of
the
stuff
is,
you
know
it's
just
like
that.
Svg
image
flow
in
the
background
and
trying
to
do
that
that
I
I
I
I
don't
know,
I
don't
know
how
that's
gonna
get
perfect
on
every
single
one,
if
you
guys
have
any
any
answers
to
that,
if
you've
dealt
with
svg's
and
and
as
they
spring
width-wise,
they
kind
of
grow
wise.
A
So
they
kind
of
extend.
That's
that's
where
I'm
struggling.
It's
like.
I
can
make
that
image.
That's
like
a
thousand
twenty
four
if
it
shrinks
width,
it
shrinks
height
and
that's
what
happens,
and
I
I
dug
into
each
of
the
svg
nodes
and
tried
to
play
with
some
of
the
numbers
there.
But
there
wasn't
a
lot
of
success
there.
Yeah.
D
That's
the
hard
one
yeah.
Are
you
saying
you
want?
So
if
you
have
so
you
say
you
had
a
square
and
the
screen
got
smaller.
Are
you
saying
you
want
it
to
stay
proportionally
the
same
or
you
want
it
to
only
shrink
with
twice.
A
Yeah,
so
I
think
the
trick
is
is
that
I
wanted
the
width
to
shrink,
but
the
height
to
stay
the
same
so
that
that
that
curve,
with
the
line
down
all
the
the
buttons
that
line
kind
of
stays
constant
I'll
see.
Let
me
share
my
screen
again.
A
See
this
line
here
so
at
this
size
really
about
right
here,
see
how
that
line
starts
to
crawl
up.
C
C
A
There
yeah
and
that
that's
you
know
maybe
make
this
whole
section
all
one
section
and
make
it
relative
and
then
position
this
that
that's
that's
something
to
try.
This
is
kind
of
its
own
component,
but
but
I
could
probably
wrap
it
around
this
whole
section
and
try
to
make
this
relative
to
that
section.
C
D
Yes,
it's
not
svg
directly,
but
I
know
that
I've
definitely
trying
to
get
svg
layouts
inside
of
css
layouts
can
be
a
little
weird,
but
that
viewbox
attribute
lets
you
set
a
height,
although
that
one
is
that's
the
one
that
it
just
scales
it
to
the
exact
same
proportions
regardless.
Is
that
what
the
issue
is.
A
Yeah
but
but
again
you
want
to
take
a
look
at
it.
B
So
I'm
not
you
know,
I'm
not
sarah
sweden,
but
I've
done
a
lot
with
svg.
I
I
know
that
this
is
going
to
be
a
huge
time
suck
yeah
there.
If
you're
looking
for
a
multi-colored
line,
there
are
ways
to
do
that,
like
with
a
like
a
before
attribute
placeholder.
B
Where
you
can
you
can
you
can
make
a
rainbow
if,
like,
if
you're
going
for
a
rainbow,
and
so
you
could
have
the
svg
and
then
have
something
that
is
like
css
connecting
with
that,
but
there's
lots
of
tricks
that
the
hard
thing
with
svg
is
getting
that
to
like
be
positioned.
I
can't
quite
find
where
this
line
is.
I
haven't
dug
in
long
enough,
but
get
you
know
making
something
that
might
be
like
absolutely
positioned,
sync
up
with
stuff
and
respond
to
stuff.
B
That
is
not
absolutely
positioned
is
difficult,
especially
with
an
svg
element.
A
C
A
Yeah
well,
it
was
like
you
know.
It
was
like
one
of
those
you
go
and
do
something
else,
and
then
you
think
of
something
you
come
back
to
it.
Then
you
go
and
do
something
else,
and
then,
finally,
I
got
it
to
enough
to
where
it's
like.
Okay,
that's
that's
good
enough
right
now,
so
yeah
working
through
that,
I
feel,
like
I'm
doing
a
pretty
good
job.
A
It's
tell
when,
like
I
said,
if,
if
you
start
mobile
first,
I
think
it
just
is
much
easier
to
deal
with
and
then
svelte
kit
is
is
really
easy
to
work
with
the
only
you
know,
problems
that
I'm
having
with
swell
swell
kit
are
challenges.
Is
that
tailwind
purges
css?
A
So
as
as
you
go
through,
it
uses
post
css
to
purge
it,
and
if
you
don't
have,
if
you
have
your
css
like
dynamically
specified,
then
it
will
kill
it
because
it
doesn't
know
it's
there,
so
that
that
was
fun.
So,
basically,
on
my
style
guide,
I've
got
like
a
hidden
batch
of
all
the
class
colors
that
I'm
using,
because
I'm
basically
using
those
dynamically,
but
that
was
that
was
interesting.
A
Anything
that
you
use
with
the
post,
css
setup
tailwind
will
purge
that
css
if
it
can't
find
it
in
any
of
your
markup
class
thing.
So
that's
good
to
know,
and
then
the
other
thing
is
is
the
tell
when
build
process
is,
is
incredibly
slow.
So
so
it
it
just
really.
You
know
getting
that
fast
feedback
and
having
to
build
tailwind
on
the
fly.
A
Every
time
there's
a
change
was
was
annoying,
and
so
one
of
the
things
that
I
did
on
another
project
was
just
pull
in
the
tailwind
css
in
development
mode
and
not
run
post
css
on
it
and
that
felt
really
good.
That
was
a
nice
feel
from
from
just
getting
getting
stuff
from
code
to
presentation
you
you
just
were,
I
was
able
to
move
so
much
faster,
so
I
know
they're
working
on
the
the
compiling
of
tailwind,
but
but
that
was
just
something
that
I
thought
was
that
could
be
improved.
C
I
know
tailwind
just
released
their
like
just
in
time
mode
as
part
of
2.1,
which
is
supposed
to
cut
down,
at
least
during
development
like
those
like
all
of
that
processing
that
has
to
be
done
to
the
css,
especially
if
you're
doing
some
like
some
things
in
the
theme
that
bloat
your
css
during
development.
A
Yeah
and-
and
I
don't
know
if
you
know
I
know
I'm
running
2.1,
but
I
don't
know
if
swelt
kit
turned
on
just
in
time
mode
or
not
so
I'll
have
to
check
check
on
that,
but
anyway,
that
that's
sort
of
where
I'm
at
with
that
and
then
in
terms
of
the
rest
of
the
road
map.
A
One
of
the
things
that
one
to
talk
about
is
the
api,
and
thanks
robert
for
looking
at
one
of
my
iterations
on
the
api
and
still
kind
of
iterating
on
that
and
where,
where
I
am,
I
feel
like,
I
just
keep
going
back
and
forth.
A
I
feel
good
about
the
the
quick
dev
environment,
where
you
get
this
one
connection
string
to
connect,
but
I'm
I'm
struggling
on
building
too
opinionated
of
an
api
and
and
kind
of
two
things
painting
painting
ourselves
in
a
corner
where
people
use
this
a
specific
way.
But
more,
I
think
more.
So
is
the
fact
that.
A
I
see
it
creating
kind
of
this
thing
once
it's
released,
that
it
has
to
stay
up
to
date,
and-
and
it
could
be
one
of
these
things
that
may
not
be
the
best
solution,
but
could
be
you
know
it
could
be
technical
debt.
A
I
guess
that's,
and
so
you
know
I've
kind
of
went
back
to
the
thought
of
you
know
creating
a
small
kind
of
configuration
module
for
like
lack
of
a
better
term
and
then
try
to
show
show
a
picture
of
that
here,
really
quick,
but
basically
just
make
it
easy
to
connect
to
hyper
and
and
then
maybe
a
more
basic
rest
approach
like
here's.
A
The
post
command
put
command,
delete
command
kind
of
thing
in
in
the
the
reasoning
behind
that
is
more
of
just
trying
to
build
stuff
with
hyper
and
and
kind
of.
You
know
each
kind
of
little
app
that
I
build
kind
of
takes
a
different
approach
and
doesn't
necessarily
have
this
one-size-fits-all
api.
A
So
here's
some
some
code
kind
of
showing
kind
of
this
config
module
where,
where
basically
it
would
export
this
url
and
this
token
method
and
the
the
url
well,
it
would
take
a
hyper
connection
string
and
that
hyperconnection
string
is
kind
of
a
url
looks
like
a
url.
A
It's
got
like
hyperio
colon
username
password
at
you
know,
server,
slash
account,
name
right
and
it
kind
of
divides
that
up
and
then
gives
you
this
url
function
where
you
can
just
give
it
an
id
and
it
fills
out
all
the
stuff
and
could
take
this
data
and
say
it's
data
or
cache
or
storage,
etc,
but
kind
of
a
url
builder
and
then
a
token
builder.
So
then,
however,
you
want
to
call
this
is
really
up
to
you.
Just
got
this
nice
url
builder
and
token
builder.
A
I'm
basically,
you
know
calling
the
fetch
and
just
calling
url
and
giving
it
some
data
to
build
my
url
and
then
I'm
just
calling
token
to
build
the
token.
So
it
eliminates
that
pain.
Point
of
having
to
remember
you
know,
where's,
my
url,
that
I'm
connecting
to
get
data
and
I
need
a
a
jot.
I
need
a
jwt,
so
it
eliminates
that
and
then
it
should
work,
whether
you
use
fetch
or
whether
you
use
axios
or
or
whatever.
A
So
that's
what
I'm
experimenting
with
now.
Instead
of
building
like
a
a
fully
expressive
api,
just
because
I
think
there's
going
to
take
a
lot
of
iterations
to
get
that
right,
what
what
are
your
thoughts?
Are
there
questions
that
I
explain
that
well
enough
are.
Can
I
answer
questions
about
that
kind
of
approach.
B
It's
pretty
clear
to
me
yeah
and
like
what
you
what
the
last
the
last
thing
you
just
showed
with
the
other
start
with
the
headers.
So
when
you're
doing
a
like
in
that
example,
you
don't
put
like
that's
what
someone
end
user
would
be.
A
You
know
maybe
an
example
like
like,
maybe
that's
in
an
example.
So
it's
you
know
an
end
user
can
just
kind
of
copy.
That
example
like
like
here's
an
example
crud
so
that
you
know
that
they've
got
the
help,
but
it's
not
like
use
hyper,
io,
client
right.
It's
like
just
just
use
the
hyper.
You
know
connection
string
in
this
little
config
module.
A
You
know
that
kind
of
builds
your
url
and
builds
your
token.
And
then,
if
you
have
a
strong
opinion
again,
you
know
using
axios,
then
here's
an
example
of
how
you
use
it
with
axios.
You
have
an
opinion
of
fetch.
Here's
how
you
use
it
with
fetch,
right
and
and
anything
else,
and
I
think
what
that'll
allow
me
to
do
is
also
go
to
other
languages.
Like
here's,
you
know,
here's
your
connection,
string,
here's
your
little
config
module
for
ruby
and
then
here's
an
example
of
how
you
make
a
rest
call
in
ruby.
A
Here's
an
example:
how
you
make
a
rest
call
and
python
and-
and
I
think
that'll
you
know
again-
be
much
more
flexible
but
but
get
give
users
a
really
simple,
onboarding
process
right.
It's!
It's
not
it's
not
so
intimidating
that
they're,
like
I'm,
not
going
to
use
this.
C
463
provides,
then,
this
sort
of,
I
think,
leaves
the
door
open
to
that.
If
I'm
understanding
how
this
is
how
this
is
structured.
So
it's
not
it's
not
so
opinionated
that
it's
backing
us
into
a
corner,
but
it's
also
most
developers
that
they
could
just
kind
of
take
it
and
use
it
directly.
A
Exactly
so,
it's
not
that
I
I
don't
want
to
do
a
client,
it's
it's
more
of
like
figuring
out
when
the
timing's
right
to
to
launch
the
client
right.
So
if
I
put
something
together
that
you
know
doesn't
have
a
lot
of
eyeballs
on
it
and
people
actually
start
using
it
in
production
code,
then
all
of
a
sudden
we're
married
to
it,
and-
and
I
don't
think
it's-
you
know
the
way
that
I
the
way
that
I'm
trying
to
gauge
it
is.
A
If
I
put
a
client
together,
I
should
be
able
to
build
five
applications
using
that
client
in
one
week
right,
five
little
crud
applications
and
what
I'm
finding
is.
Every
time
I
build
a
little
crud
application.
A
I
want
to
do
something
different
right,
so
so
that
kind
of
tells
me
that
maybe
it's
a
little
too
premature
for
an
opinionated
client
or
maybe
I'm
the
wrong
person
to
take
a
stab
at
it
right.
So
it's
one
of
those
two
things.
C
And
I
sort
of
I
sort
of
mentioned
it
on
a
previous
meeting,
but
perhaps
it
approaches
like
not
building
out
a
fully
featured
client
but
building
out
little
pieces
and
then
and
then
composing
those
little
pieces
together
to
create
a
client
that
has
just
what
you
want
and
then,
as
long
as
the
little
pieces
implement
some
sort
of
api
and
then
you
can
compose
them
together,
using
like
a
hyper
utility
and
then
that
way.
C
A
Yeah,
no,
I
I
I'm
totally
on
board
with
that
and
just
just
to
share
my
screen
real
quick
to
show
one
thing
that
that
I'm
really
happy
with
with
that
little
config
utility
is
kind
of
you
know
if
you
sign
up
with
dev.hyper63.com
with
your
github.
A
It
just
gives
you
this
connection
stream
and
you
can
hit
hit
copy.
So
I'm
really
happy
about
that.
Taking
that
connection
string,
copying
that
into
an
environment
variable
and
then
then
I
can
parse
that
with
the
url
and
and
build
that
url
builder
and
also
parse
it
and
build
a
token
which
totally
eliminates
the
user
from
the
developer
from
having
to
build
the
url
to
connect
and
to
build
the
token
all
they
have
to
do
is
just
get
that
string
in
an
environment
variable
and
and
that
that
reads
easy
in
a
tutorial
right.
E
Yeah
tom
late
to
the
party
I
apologize,
but
my
thoughts
were
the
the
url
builder
parser
and
the
token
generator
could
each
be
little
npm
modules
yeah.
Where
am
I
off
base
there.
A
No,
no,
that's
that's
exactly
right!
That's
what
what
what
and
and
I
think
I'm
listening
to
all
you
guys.
It's
like
you
know.
C
I
mean,
I
think
I
think
the
url
approach
is
is
fine
and
I
also
think
it
sort
of
adheres
to
just
sort
of
and
referencing
like
clean
architecture.
C
C
Cool
and
the
url
connection
string
seems
like
a
a
a
pretty
good
solution
to
me
that
doesn't
back
us
into
any
corners
to
support
something
that
a
team
could
like
take
to
production.
A
Exactly
so
so
that
way,
if
I
you
know,
if
I
write
like
two
tutorials
in
the
next
few
weeks,
I
don't
have
to
worry
about
those
tutorials
being
dead
in
two
months.
Right,
they'll
still
be
usable.
A
Cool
thanks
for
thinking
through
that
with
me,
because
it's
one
of
those
things
it's
like,
I
see
what
some
other
folks
are
doing,
doing
some
really
nice
apis
and
and
it's
very
enticing.
But
but
then
you
know
you,
you
narrow
yourself
down
to
very
specific
use
cases,
and-
and
you
know
not
not,
everybody
is
building
a
blog
or
not
everyone's
building.
You
know
y
combinator
hacker
news.
A
A
D
Whenever
I
see
something
like
that,
I'm
if
it
ends
up
being
clean
and
useful
long
term,
I'm
all
about
it,
but
I'm
always
my
first
direction
that
I
always
go
is
more
in
the
I
want
more
control
myself,
give
me
more
control
over
I'm
giving
someone
else
control
now.
D
It
obviously
depends
on
the
specific
scenario,
both
in
terms
of
like
the
knowledge
that
you
have
about
the
tool
that
you're
using
and
how
well
the
tool
that
you're
using
is
set
up,
but
I
generally
tend
to
like
more
control
over
something
myself.
D
A
Yeah
yeah,
you
absolutely
could,
and
I
definitely
can
provide
instructions
on
how
to
do
that
in
in
a
way
that
people
feel
empowered
to
do
that.
It
really.
My
thinking
is,
is
that
you
know
you
know.
A
A
B
What
if
I
just
drop
some
kind
of
like
tangential
thoughts,
real
quick
yeah,
because
I'm
kind
of
feeding
off
what
casey
was
saying
about
control
and
this
kind
of
goes
for,
like
I
guess
any
decision
making
you're
doing
when
it
comes
to
like?
I
guess
it
kind
of
boils
down
to
like
a
like
convention
and
versus
the
configuration
argument
that
you'd
see
in
rails
and
then
and
other
things.
B
And
you
know
as
someone
who's
been
a
beginner
in
a
lot
of
things
like
you
know,
moving
into
the
haskell
world
moving
into
the
rust
world,
like
moving
into
the
elixir
world,
moving
back
back
into
the
ruby
world
and
being
on
different
teams
or
like
just
collaborating
with
different
groups
of
people
that
were
at
a
similar
level
to
me
it
the
places
where
it's
like
you
know,
any
you
know
do
whatever
you
want,
always
ended
up
being
harder
experiences
unless
there
was
either
a
something
built
into
the
built
into
the
tool
that
gave
you
that
convention
so
think,
rails
and
phoenix
or
like
ihp
with
haskell,
which
is
a
new
thing.
B
B
You
don't
know
where
anything
is
you'll,
never
find
it,
and
it's
really
hard
to
work
with
and
because,
like
a
lot
of
different
people
over
time
had
like
their
own
ideas
about
how
to
do
something,
and
so
I
think,
maybe
that
sweet
spot
for
you
and
in
going
forward
with
with
making
things
and
figuring
out
the
client
and
stuff
is
like,
if
you're,
not
sure
exactly
what
the
conventions
should
be
for
all
the
use
cases
for
like
this
is
my
big
old
demographic
of
of
user
types,
if
you're
not
sure
about
that,
maybe
like
like
you're
doing
already
the
you
know
here,
I'm
not
going
to
constrict
you,
but
here's
the
recommended
way
to
do
it.
B
Yeah
feels
like
that's
the
sweet
spot.
I
think
you've
hit
that.
So
I'm
really
not
really
saying
much
other
than
like,
as
we
go
forward
in
the
future
too
think
about
how
you
know
think
about
if
a
code
school,
if
you've
got
a
deal
with
a
code
school
where
it's
like,
hey
code,
school
people,
get
this
much
this
many
you
know
hyper
apps
or
hours
or,
however,
you
do
pricing
stuff
in
the
future.
B
A
I
think
the
approach
that
I'm
attempting
to
take
is
if,
if
from
now
until
july,
if
I
can
get,
you
know
three
or
four
different
kind
of
use
case,
apps,
all
using
hyper
and
and
then
then
refactor
them.
A
B
Oh
yeah,
oh
yeah,
I'm
just
kind
of
like
philosophical
musing
right
now,
but
yeah.
I
know
that
makes
total
sense
like
kick
it
down
the
road
because,
like
like
you
said
you
don't
want
to
be
making
guides
and
then
all
of
a
sudden
be
like.
Oh
huge,
breaking
change.
You
know,
angular
one
to
two
level
change
and
and
lose
a
bunch
of
people
have
to
go
back
and
do
extra
work
to
update
the
old
guides.
B
Yeah
that
also
I
just
got
another
little
quick
thing.
If
you
don't,
I
don't
know
if
you're
doing
this,
but
if
you
just
when
you
do
more
guides
and
stuff
like
videos
and
blog
posts.
Whatever
are
you
tagging
any
kind
of
like,
like
hyperversion
kind
of
stuff,
to
make
it
easier
like
when
you
do
a
breaking
change
in
the
future?
You
can
know
like
you
know,
which
ones
to
go
back
and
put
a
note
on
like
this
is
for
version
best.
E
A
So
I've
got
my
learn,
spelt
one
and-
and
I
think
I've
got
to
go
back
and
you
know
kind
of
change
that
to
svelt
kit
and
that's
that's
not
hyper,
but
it's
kind
of
the
same
principle.
If,
if
you've
got
a
bunch
of
these
guides-
and
you
know
in
the
requirements
section,
it
takes
this
version
of
hyper
right
and
then
tag
that
so
that
you
can
easily
find
them.
E
You
know
yeah,
you
bind
them
together
in
the
kit
version
numbers
like
you
know
here:
here's
your
helper
code
and
tutorials
and
videos
for
hyperkit
one
and
hyperkit.
One
deals
with
this
versions
of
hyper,
and
this
was
on
this
date.
You
probably
want
hyperkit
the
latest
hyper
kit
with
a
link
to
the
latest.
You
know,
and
that
way
someone
can
get
on
to
the
the
right
point
in
time:
yeah,
it's
a
with
with
the
web
and
a
developer
ecosystem.
E
There's
it's
like
a
facet
of
a
diamond
with
many
different
faces
right,
like
a
diamonds
cup,
many
different
faces
and
you
can
look
into
the
diamond
from
any
one
of
those
facets
or
angles,
and
it's
still
the
same
diamond.
But
it's
a
different
perspective.
So,
whether
you're
coming
at
the
the
truth
of
what
thing
is
from
the
frequently
asked
questions
guide
or
the
getting
started
guide
or
the
errors
or
the
the
swagger
technical
reference
or
the
source
code,
it's
all
a
window
into
the
same
thing.
E
So
yeah
you
got
to
make
sure
they're
not
looking
into
an
old
window
into
an
old
thing
or
if
they
do
how
to
get
back
on
the
old,
the
new,
the
new
thing,
if
that
makes
sense
that
way,
that
gives
you
freedom
too
to
iterate
and
say
well
screw
hyper
kit
too.
It
sucks
we're
gonna
move
the
hyperkit
three
buy
hyperkit,
two,
so
yep.
A
A
Anything
else
is
there
anything
that
you
guys
have
for
questions,
I'm
hoping
to
make
an
announcement
a
big
announcement
any
day
this
week
and
you
know
moving
to
hyper.io
in
in
the
next
month
and
then
hopefully
be
ready
to
to
at
least
get
some
developers
on
the
system,
probably
by
the
end
of
may
that's
that's
kind
of
the
target
now.
B
Cool
I'm
gonna
give
you
I
think
tonight
I
got
a
little
time,
so
I'm
gonna
give
you
a
a
review
on
that
dev
website
dot
on
render
and
get
that
to
you
and
I'll.
Just
I'll
include
some
ally
stuff,
just
so
be
okay,
so
you're
aware,
but
not
like
hardcore.
D
A
Getting
the
website
and
and
getting
getting
the
copy
and
getting
some
guides
together
so
yeah.
A
No,
no,
it's
it's!
Just
like
the
the
the
ten
percent.
You
know
the
ninety
percent
done
and
then
the
ten
percent
that
takes
forever.
B
But
that's
the
stuff,
that's
the
stuff!
That's
like
a
make
or
break
you
know,
because
if
it's,
if
it's
real
like
bootleg
feeling
it's
going
to
be
the
most
like
the
people
who
are
willing
to
go
to
the
edge
and
like
dig
the
deepest
and
then
but
then
you
like
get
classed
as
like
a
niche
thing
instead
of
something
that's
for
the
mainstream
right
so
like
with
the
website
like
this
stuff
looks
fabulous,
and
so,
if
you,
if
your
docs
go,
you
know
go
along
with
that
and
really
like
that.
B
A
No,
I
I
hear
you
yeah
and
it's
it's
just
it's
getting
getting
the
copyright
and
getting
focus
on
making
sure
things
are
clear
and
and
easy
to
understand,
cool
all
right.
Well,
thanks!
Everyone
is
there
any
other
thoughts
before
we
hang
up.
I
know
we're
right
at
time,
so.