When comparing IntelliJ IDEA vs Gitpod, the Slant community recommends IntelliJ IDEA for most people. In the question“What are the best IDEs for Node.js?” IntelliJ IDEA is ranked 9th while Gitpod is ranked 13th.
Ranked in these QuestionsQuestion Ranking
Pro Great Java Support
Pro A good editor for test-driven development
Pro Markdown support with preview
Pro Great TypeScript support
Really good support for importing classes, libraries, etc. into a typescript class. Making it easy to do TDD.
Pro Angular CLI support
Pro Supports PHP quite well
Pro Good BASH script support
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.
Consumes more resources than VSCode etc. But depending on your use-case, it can still be worth it for the benefits you get with this editor.
Con Autocomplete does not work while IntelliJ is indexing
But this, in general, is not much of an issue. Usually after npm install, etc.
Con Is not free
But it does have a free version (Community Edition).
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.