When comparing Codiad vs Gitpod, the Slant community recommends Gitpod for most people. In the question“What are the best cloud IDEs?” Gitpod is ranked 12th while Codiad is ranked 18th. The most important reason people chose Gitpod is:
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.
Ranked in these QuestionsQuestion Ranking
Pro Open source
You can run Codiad on your server to allow you and your team to edit files.
Simplest to run may be using a Docker image like linuxserver/codiad.
Pro Easy to self-host: Only requires PHP
It only requires PHP 5+ and Nginx or Apache. No database is required. This makes it really easy to install on many servers include shared hosting.
Pro Multi-line edit
Allows to edit multiple things are once by having multiple cursors like Sublime Text.
Pro Has many easily installable plugins
Many plugins exist, from Terminal, Git to Collaboration and Emmet... Plugins can be installed by using the web interface, or by manually extracting files to the right directory.
Pro Simple and easily managable GUI
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 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.
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.
Con Terminal runs as same user for everyone
No matter who is the logged in user, the Terminal plugin runs commands as the PHP user. This also affects the Git plugin in that there is a single SSH key for all users using your Codiad instance.
Con Full of small bugs
There are plenty of various issues and bug that may either be due to your setup and the UI will not report them, or due to bugs in the code; I'm including common plugins here as well (just naming a few: search files and in files may report nothing if it had an error, commands stderr not printed, marketplace not showing items, search in market place showing no results, Git escaping
\( in the commit message for no good reason...). Those are generally small but together it makes the product feel flawed.
Con Currently no search and replace in multiple files
There is a search in multiple files, and search & replace in current file, but not something to perform a search & replace in multiple files.
Con Terminal doesn't TTY
The terminal plugin for Codiad allows users to type some commands and see the outputs, but not interactive input is supported (i.e. stdin is closed). Meaning you cannot run Vim, Tmux or anything requiring user inputs.
Con Demo only lasts 30min
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 installs 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.