Skip to content
This repository was archived by the owner on Apr 19, 2021. It is now read-only.

Commit b569646

Browse files
committed
[blog] Update around GH CS
update chris' github user name Fixes gitpod-io/website#885
1 parent f6ed7ef commit b569646

File tree

6 files changed

+69
-10
lines changed

6 files changed

+69
-10
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
date: Tue Dec 08 2020 11:49:24 GMT+0000 (UTC)
3+
author: svenefftinge, JohannesLandgraf, csweichel
4+
title: Gitpod & GitHub Codespaces
5+
subtitle: Speed and Openness Matter
6+
image: /octocat-gitpod-hat.jpg
7+
teaserImage: /octocat-gitpod-hat.jpg
8+
---
9+
10+
GitHub has announced the public availability of GitHub Codespaces today at their Universe conference. Their investment into GitHub Codespaces pushes what Gitpod has been pioneering into the mainstream.
11+
12+
In this post we would like to share some context and information around the rapidly spreading idea of automated dev environments within the developer community. Also, we’d like to point out some differences between Gitpod and GitHub Codespaces.
13+
14+
Since [we've started building Gitpod in July-2017](/blog/gitpod-online-ide/), we firmly believe that fully-automated development environments will be the standard for professional developers in 5-10 years. With a big player like Microsoft entering the market this whole space will gain additional velocity.
15+
16+
We certainly welcome the additional push Codespaces will bring, but it is important to communicate how and why [Gitpod is better than Codespaces](/gitpod-vs-github-codespaces/).
17+
18+
### Gitpod is Open-Source, Multi-Cloud, and Works With GitLab and Bitbucket
19+
20+
Gitpod is an open-source platform which means you get full transparency over how Gitpod works and can even contribute to it. The vibrant open-source community of Gitpod welcomes everyone, and empowers them to develop additional features without restrictions.
21+
22+
Furthermore, you can run Gitpod on your own infrastructure and any cloud provider. Unlike Microsoft/GitHub, Gitpod’s business objective is not driving cloud revenues on Azure. As a true independent alternative Gitpod seamlessly works with GitHub, GitLab and Bitbucket. Gitpod can be deployed to public, private or hybrid clouds, neatly integrating into your infrastructure, giving you full control of your system and your source code.
23+
24+
### Gitpod is More Powerful
25+
26+
As a highly-optimized Kubernetes application Gitpod is built on next-gen container technology instead of VMs, which GitHub Codespaces relies on. This allows Gitpod to offer its SaaS service for less than half the price of GitHub Codespaces.
27+
28+
Compared to virtual machines, isolating workspace containers from each other is harder. At Gitpod we’ve integrated the latest container isolation mechanisms that securely allow users to benefit from the resource efficiency of containers while still having root privileges. Here’s a [great technical presentation](https://youtu.be/l4I2TVAnBuw?t=174) explaining how we make this happen.
29+
30+
The result is that Gitpod offers a far better cloud density compared to VMs, resulting in more powerful dev environments with a much smaller ecological footprint. Furthermore, we run Gitpod.io on a 100% carbon-neutral cloud service ❤️🌍
31+
32+
### Gitpod is Faster
33+
34+
Gitpod is not only faster than Codespaces because of the higher efficiency, but also because of our prebuilds. Let’s take a closer look.
35+
36+
The metric that matters here is time it takes until a dev environment is ready-to-code. Ready-to-code means that developers can actually start creating and don’t have to wait for builds, dependencies to download or code generators to run.
37+
38+
With Codespaces whenever you start a new dev environment, you are left with a raw copy of the code. So before you start coding, you’ll need to run a bunch of processes and wait until they are finished.
39+
40+
Gitpod can pre-build dev environments when a new commit is pushed to the remote repository. The following diagram illustrates the idea:
41+
42+
![Prebuilds Diagram](https://user-images.githubusercontent.com/372735/101493570-870aa000-3966-11eb-9fe1-e32eb80449f0.png)
43+
44+
Besides Gitpod loading faster (it’s quicker to start containers than it is to start VMs), the advantages of having your dev environments prebuilt can not be overstated. For the [vscode repository](https://github.com/gitpod-io/vscode) we measured a 15x difference.
45+
46+
We believe prebuilding dev environments the way Gitpod does it, is key towards “dev environments as code”. Without prebuilds, developers have to manually maintain and reuse their dev environments, because of the manual labour put into them. Those stateful environments drift apart over time and teams are once again working in very different setups, wasting time and energy with the resulting problems and surprises.
47+
48+
### The Road Ahead
49+
50+
The real competition is the habit of maintaining stateful environments on overpowered local machines. We welcome GitHub and Microsoft to join forces in convincing developers around the world about the workflow and productivity benefits of automated, cloud-based dev environments.
51+
52+
We are excited about the things we announced yesterday around [Root, Docker and VS Code](https://www.gitpod.io/blog/root-docker-and-vscode/) and are already working on big plans we have for next year.
53+
54+
Ephemeral dev environments are going to democratize software development. Allowing anyone to get into a productive coding state on any of their projects and branches with the click of a button is a massive productivity boost. In addition we keep the entire devops pipeline in a centralized, managed system, which provides more security and observability to today’s developer teams.
55+
56+
We will continue to focus on automating the provisioning of dev environments that blend in with your existing workflow, integrate into your existing infrastructure and run on any cloud or your own clusters. [We do all of this in the open](https://github.com/gitpod-io/gitpod) and invite everyone to join us in building an open platform for secure, collaborative and always-ready-to-code development environments for all developers.
57+
58+
If you want to learn more you can start with our [Introduction to Gitpod](http://gitpod.io/docs/).
59+

src/blog/local-services-in-gitpod.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Using local services in Gitpod
33
date: Thu Nov 13 2019 09:00:00 GMT+0000 (UTC)
44
image: /local-services.jpg
55
teaserImage: /local-services.jpg
6-
author: 32leaves
6+
author: csweichel
77
---
88

99
Some things just aren't exposed to the internet. Either because we do not want them out in the open, think some on-prem database, or because they cannot easily be made available like the Docker daemon on your laptop.
@@ -54,9 +54,9 @@ Usually that daemon would run somewhere in the cloud, too, e.g. in your dev-clus
5454
5555
Using inlets you can make the Docker enging running on your local machine (or in your local network) available in your Gitpod workspace.
5656

57-
I've gone ahead and prepared a prepared an [example repository](https://github.com/32leaves/gitpod-goes-local/tree/docker) that demonstrates this idea:
57+
I've gone ahead and prepared a prepared an [example repository](https://github.com/csweichel/gitpod-goes-local/tree/docker) that demonstrates this idea:
5858

59-
[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/32leaves/gitpod-goes-local/tree/docker)
59+
[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/csweichel/gitpod-goes-local/tree/docker)
6060

6161
Once the workspace is up and running, follow the instructions in the upper-left terminal to complete the setup.
6262

src/blog/native-ui-with-vnc.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
url: https://medium.com/gitpod/developing-native-ui-applications-in-gitpod-15af2967c24e
33
date: Thu Oct 04 2018 12:47:53 GMT+0000 (UTC)
4-
author: 32leaves
4+
author: csweichel
55
subtitle: Cloud IDEs aren't limited to web apps
66
title: Developing native UI applications in Gitpod
77
image: /virtual-x-sever-running-on-a-remote-desktop-client.png
@@ -15,7 +15,7 @@ A few days ago [Gero introduced Docker builds to Gitpod](/blog/docker-in-gitpod)
1515

1616
## Hello World
1717

18-
Let’s use Gitpod to write [a simple desktop-native application in Go](https://github.com/32leaves/gitpod-hello-ui-demo) using [libui](https://github.com/andlabs/libui). First, we create a GitHub repo and a [little bit of configuration](https://github.com/32leaves/gitpod-hello-ui-demo/commit/fea580735c09fa704531a810e8ec7ca6a5c03a88): we need a Dockerfile to install libui’s dependencies (see below), and we need to tell Gitpod to use that Dockerfile.
18+
Let’s use Gitpod to write [a simple desktop-native application in Go](https://github.com/csweichel/gitpod-hello-ui-demo) using [libui](https://github.com/andlabs/libui). First, we create a GitHub repo and a [little bit of configuration](https://github.com/csweichel/gitpod-hello-ui-demo/commit/fea580735c09fa704531a810e8ec7ca6a5c03a88): we need a Dockerfile to install libui’s dependencies (see below), and we need to tell Gitpod to use that Dockerfile.
1919

2020
FROM gitpod/workspace-full-vnc
2121
RUN sudo apt-get update && \
@@ -50,4 +50,4 @@ I added this setup to [definitely-gp](https://github.com/gitpod-io/definitely-gp
5050

5151
By plugging together a handful of tools we can develop native UI applications in Gitpod, and stay in the browser altogether. Naturally, this comes with a few limitations, e.g. at the moment this is Linux only, so testing on different platforms is not feasible. Also, noVNC disconnects from the VNC server every now and then; reloading noVNC brings it back.
5252

53-
Surprisingly, frame-rate is not one of those limitations: you could [open a browser inside a Gitpod](https://gitpod.io/#https://github.com/32leaves/gitpod-browser-demo) and watch YouTube videos; it’s best you pick one without sound, though. :)
53+
Surprisingly, frame-rate is not one of those limitations: you could [open a browser inside a Gitpod](https://gitpod.io/#https://github.com/csweichel/gitpod-browser-demo) and watch YouTube videos; it’s best you pick one without sound, though. :)

src/blog/prebuilds.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
url: https://medium.com/@csweichel/a1c6b25fd601
3-
author: 32leaves
3+
author: csweichel
44
subtitle: Prebuild your workspaces
55
title: Waiting for code to build is like watching paint dry
66
date: Mon Mar 18 2019 16:16:17 GMT+0000 (UTC)

src/blog/status-page.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
url: https://medium.com/gitpod/status-update-gitpod-%EF%B8%8F-statusfy-ed8266d63a20
33
date: Tue Jan 29 2019 10:32:22 GMT+0000 (UTC)
4-
author: 32leaves
4+
author: csweichel
55
subtitle: Status Update
66
title: Gitpod ❤️ Statusfy
77
image: /teaser-status-page.png

src/contents/authors.ts

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,10 +46,10 @@ export const allAuthors: { [idx: string]: Author } = {
4646
},
4747
description: "Gero is a passionate software developer with a strong interest in programming languages. He likes to learn new stuff but somehow always turns out to work on the backend side of things. His current pet peeve is Kubernetes and everything around it."
4848
},
49-
'32leaves': {
49+
'csweichel': {
5050
name: "Christian Weichel",
5151
socialProfiles: {
52-
github: '32leaves',
52+
github: 'csweichel',
5353
twitter: 'csweichel',
5454
linkedin: 'christian-weichel-740b4224'
5555
},

0 commit comments

Comments
 (0)