Surprisingly, it just accesses their `/v1/messages` endpoint - nothing hidden at all.
288 karma · joined November 8, 2018
Surprisingly, it just accesses their `/v1/messages` endpoint - nothing hidden at all.
[1]: https://web.archive.org/web/20201108093051/https://github.co...
We’ve tried to align our pricing with the value of the product. In small teams the productivity gains seem to be much lower, so we target Enterprise!
We found that the biggest inhibitor to remote development was the lack of environmental flexibility. For example, Codespaces confines you to an ephemeral Linux container running on Azure, and our old product confined users to semi-stateful Kubernetes pods.
With coder/coder, you can use any operating system on any kind of compute on any cloud and change every single configuration knob. You can also mix and match cloud resources. An early user has hundreds of cloud resources in each workspace, including IAM roles, secrets, and network rules.
Early users are running stateful VMs running on GCP, Docker containers on big servers, Kubernetes Pods, and Windows VMs on Azure. We’re stoked to watch people adopt remote development in their own ways.
We’re disappointed that Microsoft chose to release under the `code-server` command-line name. Our community has produced countless blog posts, videos, StackOverflow questions, etc. that will become difficult for our users to find. This naming decision suggests that Microsoft aims to replace our code-server instead of coexisting.
We will continue developing our code-server until Microsoft’s has parity. As for Coder, we’re focusing more on the platform side (https://github.com/coder/coder) and less on making IDEs work remotely.