eschurter

5 ms·

1. 1.▲
   by eschurter 4y ago

   Hi, GitLab PM for the Web IDE and Remote Development here! You're right, the Web IDE itself is running fully in the browser, but if you try to open a new Terminal panel you'll see that it can be configured to connect to a remote h
2. 2.▲
   by eschurter 4y ago

   GitLab PM for the Web IDE here. You're right! You can follow our progress in https://gitlab.com/groups/gitlab-org/-/epics/9466
3. 3.▲
   by eschurter 4y ago

   GitLab team member & PM for the Web IDE here! In our measurements the memory footprint was between 50-80% lower than the previous Web IDE. I'm not sure how it compares to other web-based instances of VS Code.
4. 4.▲
   by eschurter 4y ago

   GitLab PM and OP author here! You're right, the client-side instance of VS Code is only a piece of the full "IDE" puzzle. You can learn more about our direction for providing server-side runtime on our Remote Development dire
5. 5.▲
   by eschurter 4y ago

   GitLab team member and OP author here. I'm glad you enjoy that `.` hotkey! Don't worry, it won't go away! I'm about 90% sure multi cursor works the same way, but I'll verify and make sure we don't take a step b
6. 6.▲
   by eschurter 4y ago

   GitLab PM and OP author here. Thanks for linking that epic @john_cogs! You can also see the direction page for remote development: https://about.gitlab.com/direction/create/editor/remote_deve... We're lo
7. 7.▲
   by eschurter 4y ago

   GitLab PM and author of the OP here. It is an interesting position we find ourselves in and we had some lively discussions about it! I would like to note, though, that Monaco (which powers our current Web IDE) is ALSO a Microsoft project. S