Skip to main content

VSCode in the Browser: Coder vs Gitpod vs Codespaces

Coder

SaaS doesn't seem to be for individuals → "Request Demo".

But they have a Setup Guide if you want to give it a try. I didn't as I just want SaaS.

TL;DR: Some extensions might be missing.

Gitpod

Go to https://gitpod.io/#/https://github.com/<your_repository> and login with your GitHub account.
Done!
Also works with GitLab.

Same as Coder. Some extensions might be missing.

Free tier gives you enough to give it a try:
  • 50 hours / months
  • Public Repos
  • Private Repos (30-Day Trial)

Codespaces (Preview)

Slower setup compared with Gitpod:
  1. Register to Microsoft Azure
  2. Create a Billing Plan. Timed out the first time
  3. Create Codespace
  4. Done!
Full-fledged Visual Studio Code in the Browser!


Conclusion

I'll try both Gitpod and Codespaces in the upcoming weeks.

EDIT June 18, 2020.
So far both Gitpod and Codespaces are impressive. Don't waste time setting up your environment, just start coding.
For Web development (JavaScript and TypeScript only), CodeSandbox is a great alternative.

Comments

Popular posts from this blog

IntelliJ IDEA not starting: Initial heap size set to a larger value than the maximum heap size

IntelliJ IDEA didn't want to start this morning. Got the following error when trying to start it from a shell: Error occurred during initialization of VM Initial heap size set to a larger value than the maximum heap size What happened is that IntelliJ IDEA loaded the JVM Options from the new custom vmoptions file in the config directory. On Windows: %APPDATA%\Roaming\JetBrains\IntelliJIdea2020.1\idea64.exe.vmoptions On macOs: ~/Library/Application Support/JetBrains/IntelliJIdea2020.1/idea.vmoptions This file was not updated properly when I updated IntellIJ IDEA. It contained: -Xms4g -Xmx2048m Fixed the issue by editing this file: -Xms4g -Xmx4g Source: https://intellij-support.jetbrains.com/hc/en-us/community/posts/360004701620-idea-vmoptions-not-used-by-default  

How to mavenify a Play 2 application

This article is for developers who want to develop web-apps with Play 2 Framework but are required to integrate these new web-apps in an existing build process based on Maven . Lucky you, someone already started a project to do this: play2-maven-plugin . Unfortunately, this Maven plugin does not support hot reloading yet, which makes the development process painful. To make it short, you still need SBT to enjoy Play 2 hot reloading feature... but you do not want to have to maintain both Maven and SBT configurations. The trick is to configure SBT from Maven pom files with sbt-pom-reader . This is how you need to configure your play2-maven project: <my-maven-project>/ pom.xml <- Your maven build build.sbt <- the sbt Play 2 configuration project/ build.properties <- the sbt version specification build.scala <- the sbt build definition plugins.sbt <- the sbt plugin configuration ...