Hacker News Reader

Comment by tosh | Hacker News Reader

Ives van Hoorne (of CodeSandbox) got Visual Studio code to run in the browser

https://twitter.com/CompuIves/status/1031930891122049024

Looking at the bio it seems like the creator is just an university student. That's crazy impressive! I thought an app of this level of polish would require at least a small team of experienced devs/designers.

Very cool. We (Sourcegraph) could never get VS Code fast enough to be the right fit for code browsing and search, which is what we're targeting. So we built our own components (open-source at https://github.com/sourcegraph/codeintellify). For browsing and search, you need fast loading, low resource consumption, a native system feel for text, etc.

For editing in the browser, where you're likely to keep one tab open for a long time, it is an absolutely obvious choice. A huge undertaking for sure, and it's awesome that he was able to accomplish it!

Theia IDE folks are working on this as well. They have a very similar project/product. I'm curious how much of the work is overlapping...

The SourceGraph folks seemed to have been one of the first to get major chunks of VSCode running in browser. I've stumbled across a few others doing similar things but they seemed like toys.

GHEdit was released ~2 years ago: https://github.com/spiffcode/ghedit/blob/master/README.md

This is really impressive! Seems like it would be in Microsoft's best interest to recruit him for the Code team.

VSCode IS running inside a browser.

What everyone else has been doing is embedding Monaco (the barebones text editor component) into their shell. The shell implements things like searches, key bindings, a file explorer tree view, top menu, fake-console etc.

What the creator is saying is that he got the actual VSCode project running in the browser. This means that the vast plugin ecosystem will run inside the browser. I suppose he'd have replaced all the nodejs dependencies with browser versions; for example an "fs" module that keeps files in-memory (or maybe using indexeddb) etc.

Further down that tweet, he says that the code is very easy to get started with. That's been my experience looking at it briefly; VSCode just seems like it was written by a team with deep expertise in IDE-making and PLs.

> VSCode IS running inside a browser.

I used to be a major contributor and follower of Atom. People commonly asked why Atom couldn't run in the browser. The answer was simple, node and a browser are totally different things. Imagine a browser opening files, starting processes, running arbitrary C-code, etc.

No, VSCode does not normally run in a browser.

Ives said it was relatively easy to swap out the node bits.

He also said that the reason for that was the way the VSCode team structured the code, not because it's "running in a browser already": https://twitter.com/CompuIves/status/1031932607326371843

Reply on news.ycombinator.com