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.
Labels:

Comments

Post a Comment

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  
Post a Comment
Read more

Pair Programming good practices from my experience

Get the best hardware you can .  Saving on hardware is stupid . One big screen is better than two . It is easier to look at the same thing .  Always talk out loud what you think . Your pair cannot read your mind . Switch roles frequently . At least every 25 minutes . It helps the pair stay focused. Take breaks . A day of pair programming can be exhausting! Use Test Driven Development . It helps you keep track of what your doing. It can improve the quality of your code. But do not forget the goal which is code that works, not test coverage . Recommended readings: http://www.extremeprogramming.org/rules/pair.html http://guide.agilealliance.org/guide/pairing.html http://www.wikihow.com/Pair-Program http://blog.xebia.com/2010/05/09/practical-styles-of-pair-programming
Post a Comment
Read more