coder VS vscode-remote-oss

I'm Quartz's primary author, and I hadn't seen this proposal until today.

They are similar in the sense of using a faked clock to make things deterministic. Other than not having to inject the Clock interface, tests using Quartz will probably look fairly similar to this proposal in many cases.

The proposal has a simpler API than Quartz, being able to just run some goroutines and wait until everything is blocked.

However, this brings some limitations on what can be tested, such as time elapsing while computation is occurring (not just elapsing while things are waiting for something else). IMO this is an important limitation, as many interesting time-of-check, time-of-use bugs and edge cases occur because time does elapse during computation in real systems.

An example of this from coder/coder that motivated the design of Quartz's API: https://github.com/coder/coder/blob/a5e4bf38fec66c5e7ecc96b0...

Founder of coder (https://github.com/coder/coder) here. We choose Terraform as our provisioning layer so that users can provision full blown VMs as their development environment.

We have many teams using GPUs with Coder for ML workloads but doing GUI/Game remote development where interactivity is essential remains elusive.

If you're looking for a collaboration tool, try Coder.

You're right, Tailscale is not 100% open source but the clients and DERP system being open source is enough for you to create what is requested here. A perfect example is https://github.com/coder/coder

Coder is using SQLc. You are responsible for handling transactions, see this example:

The company i work for is planning on implementing Coder ( GitHub - coder/coder: A tool that provisions remote development environments via Terraform) with VS Code.

Next, you'll need a workspace template to be able to create a workspace. Again, the Coder's docs explain how to do this well and there is an example k8s template you can start from.

Coder https://github.com/coder/coder

That’s the extension which launches the server. The server itself, which is what runs on the remote machine, is part of the vscode repo itself. You can see this open source extension for an example of what the extension does as well as an explanation of what it does https://github.com/xaberus/vscode-remote-oss

Mainly just sets up the UI/connect commands in vscode UI and launched REH (the vscode server) on the remote machine. The actual server is just a different binary you build from the same repo. Non-Microsoft OSS builds of vscode work with SSH fine.

I guess that's https://github.com/xaberus/vscode-remote-oss

There's also remote-oss [1], which is fairly low-level (you have to install it on), but doesn't require you to pass your traffic through the GitHub proxy that Microsoft's service requires (I believe) and is also truly open source (which means, for example, that it can also be used with Codium [2], not just the Microsoft's VS Code distribution).

[1]: https://github.com/xaberus/vscode-remote-oss