►
From YouTube: Container powered IDE discussion
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
So
I
think
that's
James
and
I
were
just
talking
about
like
the
usefulness
of
cloud-based
IDs
and
some
of
the
drawbacks
with
them
and
I.
Think
like
what
octet
Oh
gives
you
is.
You
don't
have
to
worry
about,
like
I
spin
up
time
on
your
IDE,
like
you
just
edit
your
code,
then,
whenever
IDE
that
you
want
and
then
via
the
command
line
like
you
spin
up,
like
you
start
octet,
oh
and
then
yeah,
it's
a
little
bit
of
time
to
like
get
the
service
to
synchronize
and
your
files
a
synchronized.
B
Yeah
I
guess
it
I
think
the
thing
we
were
not
also
talking
about
it
was
like
the
distinction
between
like
the
web
ID
today
and
the
use
case
that
everyone
loves
it
for
is
you
click
it
and
it's
just
like
instantly
there
you
make
your
edit
and
you
close
like
it's
it's
a
very
it's
a
very
different
task.
Like
is
it's
a
lot
of
the
things
I
use.
B
The
idea
for
like
I
have
no
real
integrations
with
like
I'm,
using
it
for
editing
a
markdown
doc
fixing
a
typo
here
or
there
and
writing
a
release
post,
and
although
sometimes
it
would
be
nice
to
have
like
more
validation
or
more
tools,
they
I
don't
need
a
full
development
environment.
The
thing
I
like
it
for
is
that
it's
like
way
faster,
then
doing
things
locally,
like
I,
have
all
the
projects
that
I'm
editing
locally
99%
at
the
time,
and
so
really
what
I'm
comparing
it
to?
B
B
B
A
B
And
I
think
that's
really
interesting
like
having
the
server-side
development
environment
to
local
and
maybe
in
the
future,
to
a
web
interface,
because
I've
tried
a
Camille
wrote
that
kubernetes
or
cloud
GDK
thing
because,
like
even
with
my
powerful
MacBook
like
running
the
GDK
locally,
sets
it
on
fire.
It
like
I'd,
rather
have
a
giant
box
in
the
cloud,
that's
catching
on
fire.
That's
someone
else's
problem,
rather
than
it
being
on
my
lap
or
killing.
B
My
zoom
call,
because
I've
run
out
of
resources
or
I
can't
actually
run
two
instances,
because
I'm
running
like
some
more
complicated
feature
of
gitlab.
That
really
actually
needs
all
these
CI
runners
or
kubernetes
features
turned
on.
In
addition
to
the
application
being
able
to
have
that
development
environment
in
the
cloud,
so
I've
got
more
computer
resources
than
my
laptop
provides
or
my
desktop
provides,
is
really
useful.
C
Think
only
that
the
only
thing
we
really
can't
do
and
get
laughs
is
the
last
thing
where
we
just
need
to
make
an
official
Fiasco
plugin
to
make
it
a
great
experience
and
there's
a
couple
of
plugins
but
I
suggest
to
discuss
like
hey,
let's
put
one
engineer
on
having
an
official
via
scope
plug-in
so
we're
gonna.
Assuming
we
have
that
now
we
have
the
web
IDE.
We
have
a
great
view:
scope
plugin
in
the
IDE.
How
do
you
do
that?
How
do
you
do
that?
C
Is
that
make
sense,
and
then
the
only
thing
we
don't
support
it's
other
editors,
but
it's
kind
of
a
done
deal
right
now,
like
everyone
is
migrating
to
vs
code,
even
like
long
time
build
users
and
stuff
like
that,
so
I
think
we're
kind
of
we
can
just
optimize
your
vs
code
and
let
the
rest
not.
For
the
rest,
we
should
go
for
the
majority
yeah.
B
I
think
that
there
are,
there
are
some
like
pretty
big
changes
that
would
be
needed,
because
what
we're
running
today
is
the
web.
Ide
isn't
really
vs
code,
it's
just
Monica
and
Monaco's,
like
the
tiniest
part
of
es
code
like
Monaco,
is
literally
just
the
text
buffer
area
like
it
doesn't
even
include
the
tabs
or
pain
management
or
any
of
that
stuff.
June.
A
A
A
C
C
Yeah
and
it's
almost
like
right
now-
the
majority
of
developers
do
want
their
editor
locally.
So
maybe
we
should
just
start
with
making
be
srvs
code.
Plugin
connect
to
get
lab
and
connect
to
the
stuff
on
the
cluster,
so
more
of
a
porchetto
experience
and
then,
if
that
takes
off,
we
can
always
kind
of
bring
it
back
to
an
online
version.
But
then
that
way
we
kind
of
have.
B
Yeah
I
think
it
also
provides
a
really
good
pathway
for
internal
dogfooding
and
I.
Know
that
there's
a
lot
of
people
that
struggle
to
run
the
JDK
locally
like
if
we
could
have
a
cluster
solution,
make
it
really
easy
to
develop,
get
lab
in
the
gear
lab
cluster.
Everyone
would
like
adopt
that
really
quickly.
I
can't
imagine
how
many
thousands
of
hours
have
been
lost,
even
in
an
organization
with
a
skill
of
agat
lab
just
making
get
lab
work
in
the
GDK.
A
C
Be
great,
let's
call
it
the
Monaco
IDE,
so
we
got
mono
Monica
IDE
plane.
We
got
Monaco
IDE
with
code
sandbox.
Then
we
got
vs
code
I
vs
IDE
to
the
cluster.
Then
you
got
a
local
vs
code
to
the
cluster.
Then
you
got
a
local
other
editor
to
the
cluster
and
then
you
got
the
ESCO
locally
kind
of
with
a
local
development
environment,
but
still
like
with
all
the
good
luck
goodies-
and
my
suggestion
is
stop
talking
about
forget
about
the
other
editors
and
if
we're
going
to
do
something,
let's
first
focus
on.
C
A
C
B
B
A
D
C
Well,
that
depends
a
bit,
but
on
the
octet
Oh
license
and
stuff
like
that,
you
can
just
reuse.
It
I'm
fine
with
that,
but
like
all
this
stuff
about
Oh
we'll
just
run
something
as
a
good
lab,
managed
step
no
one's
installed
and
get
appendage
steps.
So
I
think
it
should
be
on
by
default
as
much
as
we
can.
A
A
B
There's
a
few
players
in
the
space.
What
evaluating
the
tilt
guys
I
spoke
with
them
a
while
back,
I
was
just
saying
to
Eric
I,
think
Sid.
You
actually
set
up
the
the
meeting
I
had
with
them
and
victors
now
there
so
I'd
be
interesting
to
see
what
they're
doing
where
they've
come
in
the
last
year
and
whether
they're
things
fully
open
source
and
how
well
it
works
as
well
as
investigating
other
vendors
and
seeing
seeing
how
they
work
out.
D
C
C
B
C
B
Yeah,
there's
I
think
a
pretty
big
amount
of
thinking
to
work
out
how
we
offer
clusters
in
a
sort
of
safe,
secure
way
and
how
we
wrap
that
into
our
existing
billing
model
and
I.
Think
from
from
the
user
perspective,
you're
right
but
I
think
there's
a
lot
of
questions
about
how
he
would
actually
implement
that
because
I
don't
think
we
have.
C
You're
right
so
in
this
case,
like
the
managed
apps,
are
not
taking
off,
because
people
aren't
adding
their
kubernetes
cluster,
but
we
can't
offer
this.
What
are
you
adding
your
kubernetes
cluster?
So
we're
building
a
catch-22
here,
so
here
it's
it's
valid
that
it
doesn't
matter
that
much
of
its
a
manage
that
so
I
have
a
hard
time.
I
give
it
to
manage
that
and
the
interface
is
going
to
be
outside
of
get
lab
and
that's
what
we
promise
a
single
application.
So.
A
Incentive
to
set
up
a
cluster
to
run
some
of
these
managed
apps
like
people
just
don't
want
the
utility
that
these
apps
are
providing
versus.
If
we
provide
the
experience,
that's
integrated
and
the
clusters
are
something
that,
like
kind
of
runs
behind
the
scene,
similar
to
what
we
do
with
birth
runners,
I
mean
I.
Think
that's
I,
think
that's
how
you
do
this
right.
It's
not
it's
not
a
managed
aplex
perience,
it's
just
yeah!
A
C
Yeah
I
do
think
that
we
can
lay
that
problem.
We're
pretty
sure
it
has
to
work
in
the
cluster
because,
like
kubernetes,
is
the
new
crowd
interface.
So
that's,
but
we
know
we
can
already
attached
clusters.
Let's
make
that
work
which
something
that
is
like
India
part
of
yeah,
okay
way,
20s
to
code
and
then
vs
code
locally
is
probably
easier.
So,
let's
make
it
as
easy
as
possible
for
ourselves
and
we'll
know
more
after
we
ship
that
we'll
learn
more
yeah.
B
And
we
have
prior
art
for
shipping
a
get
live,
app
inside
of
a
managed
app
and
then
making
it
native
inside
of
gitlab,
which
would
be
the
CI
run.
It's
like
you
install
CI
Runner
in
your
manage
cluster,
and
then
you
manage
it
from
the
git
lab
application.
So
potentially
like
get
pods
or
some
other
thing
could
be.
A
C
So
this
is
like
the
death
valley
before
startups.
There's
speed
in
so
many
startups
that
didn't
make
it,
including
super
cool
ones
like
nitrous
and
coding,
or
gives
me
pause
that
this
time
is
different.
Kubernetes
is
very
different.
Kubernetes
and
Dockers
make
this
different
and
I
read
on
a
hacker
news:
article
or
a
couple
of
people
that
were
using
cloud
9
and
we're
pretty
excited
about
anti
jesting
about
it.
C
They
use
it
every
day,
so
I
most
of
the
time
when
there's
a
lot
of
startups
that
didn't
make
it
it's
off
because
they
were
wrong
just
because
they
were
early
and
extraction,
but
this
is
gonna.
It's
gonna
take
a
while,
but
I
think
I.
Think
it's
interesting.
I
also
think
it's
very
going
to
be
very
interesting,
because
github
will
have
that.
Well,
we
bring
something
for
you,
but
it's
a
single
thing:
it's
not
really
kubernetes!
C
It's
not
similar
to
your
production
environment,
you
and
we
run
it
for
you
doing
Azure
and
that's
it
and
we'll
all
has
something
that
you
can
run
on
any
cluster.
So
we
can
partner
with
all
the
cloud
providers,
including
an
azure
but
also
a
VMware
and
Red
Hat
and
everyone
else.
You
can
just
use
what
you
use
in
production,
so
I
think
there's
there's
a
great
value
at
Ross
there,
but
anytime,
you
say
flexible,
it's
10
times
more
complex
for
the
end
users.
So
then
driving
usage
is
always
there's
a
hard
part
cool.