June 2021 Summaries

An Integrated Development Environment (IDE) is a suite of applications used by developers for writing and building applications. Traditionally, developers have run their IDEs on local machines, but there has been growing interest in moving development workspaces and IDEs to the cloud. Local IDEs are installed and run on a developer's personal machine, while Cloud-based IDEs run on servers accessed through a browser or other remote access tools. The choice between using a local or cloud IDE depends on factors such as team size, internet connectivity, hardware limitations, and individual preferences for customization.

The text discusses how Coder, a platform that orchestrates development environments on Kubernetes infrastructure, migrated its networking from a traditional reverse proxy architecture to WebRTC. This change was made due to issues with the previous architecture, such as brief interruptions during envproxy process crashes and additional round-trip latency. By using WebRTC, Coder can now leverage built-in browser APIs for better security, faster editing experience, and compatibility with diverse networking configurations. The new approach also minimizes points of entry that administrators need to secure. Future releases will explore further improvements, such as full peer-to-peer communication and an in-browser WebRTC proxy.

In Coder, software development occurs in cloud workspaces that contain dependencies, IDEs, and configuration for projects. These workspaces are reproducible and can be accessed through Web IDEs, SSH, or local file sync. Unlike traditional containers, Coder Workspaces persist the home directory to prevent loss of source code and settings. They also support running system-level apps inside containers using the Sysbox container runtime. This makes Coder a great candidate for developing cloud-native apps. Workspaces can be large or small and are resource efficient, leveraging Kubernetes and container technology. Teams can conserve compute resources by setting provisioning ratios. Workspaces can also be source-controlled using coder.yaml files in Git repositories. Coder workspaces currently run inside a Kubernetes cluster with the enterprise version, but a SaaS offering is planned for future release.

The future of cloud development is expected to prioritize editor neutrality, allowing developers to choose their preferred editors while working remotely. This approach has been shaped by the experience of Coder IDE, which failed to gain traction due to its attempt to impose a specific workflow on developers. Instead, Coder shifted focus to creating code-server, a platform that enables developers to use popular editors like VS Code in a browser, respecting their existing workflows and choices. As cloud development platforms evolve, they will need to prioritize developer choice, including operating system, software stack, editor, keybinds, and terminal options, to empower developers and provide a more neutral and flexible environment for remote work.