Skip to content

Commit a47cd81

Browse files
committed
Update FAQ: code-server is not using a direct fork
Also the wrapper process is another major difference along with the update notifications.
1 parent c9fbcff commit a47cd81

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

docs/FAQ.md

+5-3
Original file line numberDiff line numberDiff line change
@@ -390,9 +390,9 @@ Theia doesn't allow you to reuse your existing VS Code config.
390390
## What's the difference between code-server and OpenVSCode-Server?
391391

392392
code-server and OpenVSCode-Server both allow you to access VS Code via a
393-
browser. The two projects also use their own [forks of VS
394-
Code](https://github.com/coder/vscode) to leverage modern VS Code APIs and stay
395-
up to date with the upsteam version.
393+
browser. OpenVSCode-Server is a direct fork of VS Code with changes comitted
394+
directly while code-server pulls VS Code in via a submodule and makes changes
395+
via patch files.
396396

397397
However, OpenVSCode-Server is scoped at only making VS Code available as-is in
398398
the web browser. code-server contains additional changes to make the self-hosted
@@ -415,6 +415,8 @@ Specific changes include:
415415
- The ability to use your own marketplace and collect your own telemetry
416416
- Built-in proxy for accessing ports on the remote machine integrated into
417417
VS Code's ports panel
418+
- Wrapper process that spawns VS Code on-demand and has a separate CLI
419+
- Notification when updates are available
418420
- [Some other things](https://github.com/coder/code-server/tree/main/patches)
419421

420422
Some of these changes appear very unlikely to ever be adopted by Microsoft.

0 commit comments

Comments
 (0)