►
Description
Paul Slaughter, Staff FE Engineer, and Eric Schurter, Sr. Product Manager, demo a proof of concept implementation of VS Code running in the web, replacing the GitLab Web IDE.
Part 1 is focused on the overall user experience of running VS Code in the web and how it compares to the current Web IDE.
Learn more here: https://gitlab.com/gitlab-org/gitlab/-/issues/345718
A
B
A
So
paul-
and
I
are
here
to
demo
the
work
that
he's
been
doing-
to
build
a
proof
of
concept,
integration
of
vs
code
running
on
the
web
to
replace
our
web
ide.
So
before
the
recording,
we
were
talking
about
breaking
this
up
into
a
few
different
parts.
This
will
be
part
one
and
paul
I'll.
Let
you
take
it
over
and
just
kind
of
give
an
overview
of
what
that
means
and
how
it
works
and
what
kind
of
benefits
we
would
gain
from.
Moving
to
vs
code
for
our
web
ide.
B
B
And
then
click
on
the
web
id
button,
but
what
we're
demonstrating
what
we
did
architectural
spike
on
is
instead
of
loading
our
homegrown
built
view
app
of
the
web
ide
we're
gonna
load,
a
a
customized
bootstrap
of
a
web,
build
of
vs
code,
so
local
vs
code
editor
comes
in
a
browser
build
and
we
can
load
custom
extensions
on
it
which
let
us
seamlessly
integrate
with
gitlab.
Hopefully
so
this
is
it
all
bootstrapping.
B
It's
pulled
the
file
tree
from
the
project
that
I
just
loaded
and
I
can
use
here's
all
cool
hotkeys
that
come
baked
out
of
the
box.
I'm
gonna
hit
f1.
I
can
start
running
commands,
but
I'm
also
gonna.
I'm
just
gonna
look
for
the
readme
file
and
I'm
here
editing
the
readme
file
and
I
can
make
changes
nicely
as
I
would
expect,
and
I
can
view
those
changes
in
the
source
control
tab.
B
I
can
preview,
I
can
also,
I
don't
know,
start
opening
up
other
things
on
that
tab,
like
so
here's
my
preview
and
then
I'm
going
to
open
up
this
on
other
tabs,
and
I'm
I'm
not
even
familiar
with
this,
but
you
can
keep
splitting
things
like
at
vs
code
lets
you
split
things
and
definitely,
however,
you
want
there's
also
some
cool.
There
are
some
things
you
get
in
the
footer
here
of
where
usually
you
would
have
like
your
terminal?
We
don't
have
a
terminal,
but
we
do.
B
You
can't
have
problems
and
output
and
other
extensions
can
write
to
this
so
like
you
can
actually
see
a
list
of
what
maybe,
like
my
linting
problems,
are
that
will
show
up,
but
if
I've
opened
up
files,
so
let's
also
just
open
up
some
column
files.
If
I
open
up
yeah,
let's
open
up
and
let's
find
another
kotlin
file
or
whatever
so
I
open
up
these.
These
files
also
lets
me.
Do
the
search
so
I
can
start
searching
for
whatever
files
I've
opened.