GItHub Codespaces is a hosted remote coding environment by GitHub based on Visual Studio Codespaces integrated directly for GitHub.
Ranked in these QuestionsQuestion Ranking
Pro Preferences are synced
Your Visual Studio local preferences and extensions are saved within GitHub, allowing you to use your configurations on the go.
Pro One-click experience
Designed to make contributing to a repository easier, all it takes to start the cloud IDE is its dedicated button within the repository page.
Pro Visual Studio Codespaces extensions works as-is
If you are a customer for Visual Studio Codespaces, your extension to control GitHub Codespaces will also work and you will be able to use your Visual Studio Code to interact to the Codespace instead of using the Web IDE if need be.
Pro Extensible and configurable
Borrowing from its bigger sister, Visual Studio Codespaces, which is also based on Visual Studio Code, any VS Code extensions work outside the box, no gotchas.
Pro Customizable environments
Environments can be customized in the user-level or the repository using a container declaration file, allowing the environments to be tailored according to the user and the target project
Con Limited to GitHub
As this is a GitHub Product, do not expect it to work with the likes of GitLab or BitBucket. If you want to use third party VCS providers, you might want to use Visual Studio Codespaces instead.
Con Limited to 5 Codespaces instances
GitHub Codespaces currently limits you to 5 concurrent working codespaces. You have to delete another to start another codespace.
Con Early-Access Software
Currently invite-only, expect GitHub Codespaces to have some bugs until its GA release.