When comparing Koding vs Gitpod, the Slant community recommends Koding for most people. In the question“What are the best cloud IDEs?” Koding is ranked 3rd while Gitpod is ranked 11th. The most important reason people chose Koding is:
All languages, databases, and command-line tools are supported. Most machines are already set up with web project basics like Apache, PHP, MySQL, Ruby, Node.js, Perl, and Python and anything else can be installed via the SSH root access.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Everything is supported
All languages, databases, and command-line tools are supported. Most machines are already set up with web project basics like Apache, PHP, MySQL, Ruby, Node.js, Perl, and Python and anything else can be installed via the SSH root access.
Pro Ability to signup with Github
And link account to oDesk and Facebook.
Pro Great community
Koding has a community feature that makes it easy to collaborate and share ideas with like minded developers all over the world. And the community itself is very active and helpful community.
Pro Real-time collaboration
Real-time code and terminal collaboration with integrated chat abilities.
Pro Built-in terminal
With 256-color support.
Pro Various file upload options
Koding supports drag & drop, Dropbox, clone from Github, FTP and the ability to access them using SSH.
Pro Built-in package manager
The Koding Package Manager (a successor to Apps) is command line tool for installing packages like nginx, Redis, VNC, Wordpress and many others. It consists of officially supported and user-built packages.
Pro Communities
Ability to create different sized communities that can be public or private.
Pro Social Stream
There's a built-in social network with developers from all over the world.
Pro Unlimited domains and subdomains
Unlimited user-defined domains and subdomains for private or shared VMs can be set up.
Pro Capable editor
Koding uses the Ace editor that's developed by Cloud9. Besides the basics, it covers most important advanced code editor features such as code folding, converting cases, auto-completion, code analysis and refactoring, regex search and offers easy access to relevant documentation.
It also gives access to the CLI, has support for Vim and Emacs keybindings, includes multiple cursors and zen coding mode that removes all distractions and allows focusing on code.
Pro Customizable Workspaces
Gitpod workspaces are very customizable. You can define a workspace with .gitpod.yml
and define your own Dockerfile if you need tools that needs preinstalled automatically.
Pro Open Source to the core
Gitpod is a Web IDE product by TypeFox, which created Theia, a open source IDE framework. They rely on Kubernetes, Docker, Theia, and Let's Encrypt to provide this service - providing a 100% OSS-based SaaS.
Pro Workspaces are created from GitHub URLs
Any GitHub repository can be prepended with https://gitpod.io#
to define a Gitpod workspace. Here's an example of it.
Pro VNC Support
Gitpod has VNC support out of the box, which allows you to test Desktop apps within the cloud.
Pro Pre-authorized Git Client
This is the only GitHub-based Web IDE that pre-authorizes the git client, saving you time to do setup.
Pro GitHub Pull Request Issues Comments are viewable on the IDE
No need to jump tabs when making needed changes for your GitHub Pull Request. Gitpod supports viewing the comments and resolving those through the IDE - so you can resolve comments without ever needing to mark it resolved manually on GitHub.
Pro Automatic Configuration
If your GitHub repositories does not have a manifest to make a stack, Gitpod will attempt to make a stack based on what it understood about your codebase. However, for popular projects, a central repository on GitHub exists to configure a workspace automatically for them without the manifest file to be present.
Pro Language Server Protocol support
LSP is a standard made by Microsoft to create a single common core that can be consumed by a development tool. Theia is based on Visual Studio Code and supports LSP natively.
Cons
Con Not a cloud IDE
Have to provide your own IDE, so not a cloud IDE.
Con No real individual user support
While they do have plans available for 1-10 users, they are not focused on individual developers, so much as teams.
Con Does not create forks automatically for you
If you make a Gitpod workspace based on a GitHub repository you do not own, git push
will fail and you need to query the Git client to make the fork for you.
Con Can be slow on 3G Networks
The crux of this is because of the large bundle.js
that is needed to be transferred, this is a problem within Theia.
Con Packages can't be installed through the CLI
Gitpod doesn't support apt install
s yet due to the container mounting through an NFS. To alleviate this, you need to define a custom stack for your project if you need it.
