When comparing Codenvy vs WebStorm, the Slant community recommends WebStorm for most people. In the question“What are the best JavaScript IDEs or editors?” WebStorm is ranked 2nd while Codenvy is ranked 18th. The most important reason people chose WebStorm is:
WebStorm integrates with Node.js to allow for running, debugging, and unit testing of Node.js apps.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Easy setup
Once an account is set up and the user has logged in, all that's needed to start is to pick a language, a framework and a PaaS. Codenvy also allows anonymous logins albeit with some important limitations.
Pro Powerful editor
Codenvy has a fast, secure browser-based editor that supports syntax highlighting, code completion, refactoring and more. It can be used to edit, build, run and debug projects. It even has multi-cursor support.
The layout will be familiar to most developer, especially those experienced with Eclipse, with a file explorer on the left, code on the right and tabs for builders, runners, terminal and events at the bottom.
Pro Beginner-friendly
It allows going to any box and pick up a project and work on it.
Pro Git support
Codenvy supports all Git commands through UI and Codenvy CLI.
Codenvy also integrates well with all major Git hosting providers including GitHub, BitBucket, GitLab. Sign up, sign in, repo cloning, uploading SSH keys are supported. Tutorials for integrating various providers can be found here.
Pro Partly open source
Codenvy is a full multi-user, multi-account, multi-tenant implementation of [Eclipse Che](https://github.com/eclipse/che/_ which is open source but only single-user/account/tenant. Codenvy open source projects can be viewed on GitHub.
Pro Self-hostable (priced)
Codenvy has an on-premises solution that allows running it on own hardware and behind a firewall. The service costs $300/user/year.
Pro Nice interface
Look and usability of Codenvy IDE are nice and pleasant.
Pro Easy projects sharing
Projects are share by sharing the link (public projects), adding access rights (private and public projects) and factory.
Factory allows to share projects along with build/run settings. To try run/review project recipient just need an URL. Factory also works with external git repositories so it allows share github/bitbucket/other git hosting projects. Recipient doesn't have to be registered. It also allows giving out a share button that activates the factory and counts how many times it is used.
Pro Portable workspaces
You can send someone a short JSON file and your whole workspace (projects, config and runtime) can be replicated for them in a separate container. Great for coordinating among team members.
Pro On-demand, instant-access, real-time collaborative IDEs
Codenvy "Factory" feature enables developers to create temporary IDE workspaces with full code, build, test, deploy, and collaboration functionality that can be shared with a URL. Multiple people can work in the same workspace making code reviews and teaching simpler and faster. And there's no limit to collaborators.
Factories also work with external git repositories and can be shared with not registered users of Codenvy. It also allows counting how much a factory is used.
Pro Has a fully functional free tier
Codenvy provides a fully functional free tier with 3 GB of RAM and unlimited workspaces, free and public projects and developers. Premium subscription start at $1/month and offers machines with up to 200GB of RAM. Codenvy also offers an on-premises solution that costs $300/user/year.
Pro Fantastic Java support
All Java builders, syntax highlighting, class navigator, jump to package and declaration, and JavaDoc are present in Codenvy.
Pro Can provide a custom runtime environment
Codenvy can provide a runtime environment to test and debug code. This can also be used to share work progress with a client.
Codenvy uses Docker as the runtime application and gives access to Dockerfiles allowing any environment that runs on Linux to be built. This allows using any database, reverse proxy or builder, etc. Codenvy even provides SSH access to running container in every image.
There's also a selection of pre-built environments to speed up the development.
Pro Install anywhere Docker runs
You can install Codenvy on any OS that has Docker running on it. The simple install syntax can work through proxies and even offline.
You can use this for proxy install:
https://codenvy.com/docs/admin-guide/installation/index.html#proxy-installation
You can use this for offline install:
https://codenvy.com/docs/admin-guide/installation/index.html#offline-installation
Pro Provides a terminal with root access
Codenvy offers a terminal with full root access into the machine. Since machines can be defined with Dockerfiles this gives the ability to create any custom environment for building, running or debuging and all the access that's needed to use it as a local machine.
Pro Complete build lifecycle
The IDE allows validating, compiling, testing, packaging and deploying.
Pro Integrates with a wide variety of tools
Codenvy offers first class support for code management, continuous integration, PaaS, and project management tools.
Pro Automation of contribution to GitHub projects
Codenvy provides contribution button that can be placed in Readme.md file on GitHub. It automates contribution to the Github's projects. User clicks this button and it opens a ready to run/edit version of the project in Codenvy. If a user makes changes, Codenvy takes care of everything needed for the contribution on GitHub.
- fork of the origin project on github
- add ssh keys to push to github
- commit
- push
- create pull request in the origin project
- create factory url for review of this pull
- post this factory in pull request.
Then project's owner can use posted link to code review/run project with changes.
Pro Badge to start developing in one click
You can create a .codenvy.json
containing the Factory configuration which includes what binaries to install and how to set up the IDE, may be even start the development server. Then create a badge and put it on your GitHub repository and people can start coding and may be compile and run your server with one click.
Pro Lots of built-in templates
Pro Can be used for Android development
Can be used for android development by adding Eclipse plugin.
Pro Custom build system support
Codenvy allows setting up any build system via Dockerfile. Instructions on how to do it can be found here.
Pro Has Eclipse plugin
Codenvy can be plugged into Eclipse offering choice between online and offline builds. Plugin can be found here.
Pro Developer workspace replicas
Codenvy can create a recipe for a developer workspace that includes the build and run environment configuration plus all the IDE plug-ins, syntax rules, policies and other items. Then version and store that with the code in a repository. Makes it impossible to get a code change that doesn't build and run.
Pro Quick support from staff
Pro One-click automation
Pro SSH Access
Can connect to the workspace via SSH for use with desktop editors.
Pro Provides Java debugger
Pro Includes Subversion support
Codenvy includes full subversion version control support.
Pro Node.js integration
WebStorm integrates with Node.js to allow for running, debugging, and unit testing of Node.js apps.
Pro Code refactoring support
To make sure your code can be easily maintained, you must first be sure to make it clean and tidy. This is the part where WebStorm really helps you. It automatically refactors your code by performing functions on it, such as extraction of variables, moving files, inline variable extraction, etc.
Pro Integrated code quality tools
WebStorm comes bundled with JSHint and JSLint. JSCS, ESLint, and Closure Linter can be installed via npm. They register as inspections and are customizable through IDE settings. They run automatically and will highlight potential issues. Pressing alt+enter on an issue will allow the user to view suggested fixes.
Pro Intelligent code completion
WebStorm has two types of autocompletion: structural completion and word expansion.
Structural autocompletion makes predictions based on its understanding of JavaScript objects, while the latter tries to predict the word currently being typed based on previously typed words. Word expansion also works in comments and docstrings and it's similar to vim's omnicompletion.
Both types of autocompletion work extremely well, have little to no problems and are quite fast even when loading suggestions on the go.
Pro Supports a wide range of plug-ins
Pro Maintains a local history
The local history feature in Webstorm tracks all your local changes in the source code that you are making. You can use it to view changes that you've made to your code and roll back whenever necessary.
Pro Typescript support
WebStorm offers typescript support for building typed JavaScript applications which improves refactoring and code completion, as well as helping to find bugs.
Pro Supports many JavaScript frameworks
WebStorm includes support for Meteor, Angular, and React.
Pro Reduces the amount of repetitive code that has to be written with code snippets
WebStorm includes a feature called Live Templates. Live Templates are predefined code snippets that can include variables. They're intended to increase productivity by reducing the amount of repetitive code that has to be written.
Pro Ability to base hot keys on previously used IDEs
When you install WebStorm, it allows you to choose from other IDE's for it to base it's hot keys on. So if you are switching from another IDE, it makes it a very easy transition and productivity is not adversely affected by having to learn new hot keys.
Pro Powerful git and GitHub integration
WebStorm has a powerful visual git tool, allowing for easy commits, visual diffing, merging, push/pull, rebasing, and inspecting the VCS history of a project. GitHub is supported natively - you can check out a project directly from GitHub.
Pro Built-in support for JavaScript task runners
WebStorm has support for Grunt and Gulp task runners.
Pro Built-in terminal/run tools
WebStorm (and really all of the IntelliJ IDEs) support the plugins throughout their plugin ecosystem which leaves you with 100s of tools to handle your automation tasks. There is a wide range of build-related plugins that help you by having pre-defined commands to execute with the click of a button. Out of any other IDE, WebStorm has by far the most coverage when it comes to tools for your development workflow.
Pro Theme support / tweaking
The theme is very easy to customize to your liking. You can change font-size, colors, highlighting colors, and more.
Pro Support for all major VCS systems
Webstorm supports not just Git and Mercurial, but Subversion, CVS, and Perforce as well.
Pro Multi-line select and editing
Pro Really good configurable code formatting
This integrates with other community tools like ESLint and editorconfig.
Pro Powerful Code Templates
Code Templates are powered by Apache VTL (Velocity Template Language) and allow for includes, custom variables, conditional blocks, iterators, and live templates.
Pro Special icons for most filetypes in project list
Webstorm comes with icons for many filetypes which makes it easier to find what you're looking for in the project list.
Pro Built-in web server
WebStorm has a built-in webserver that allows you to run projects from http://localhost:63342/ProjectName
.
Pro Has a built-in terminal
The IDE comes with a built-in terminal, a feature lacking in some lighter editors.
Pro Compilers for compile-to-JavaScript languages
WebStorm has built-in support for CoffeeScript and Dart.
Pro Support for Karma test runner
Karma allows you to execute unit tests and monitor code coverage. You can read more about using Karma with WebStorm here.
Pro CSS pre-processor support
WebStorm has built-in support for Sass which is one of the most stable and powerful CSS extension languages.
Pro Server and client-side debugger
WebStorm has a powerful debugger, with support for conditional breakpoints.
Pro Auto sync settings across team / machines / platforms
With the settings repository, you can easily enforce your development standards.
Pro Free for open-source development, students, and teacher
Non-commercial open source projects, and students and teachers (including classroom licenses) may qualify for a free license. There is a 50% off license for startups (under 3 years old). You can read more about it here.
Pro Different configurations for different projects
It is able to specify for example node versions, which will be used to run task for current project.
Pro Webpack support
Assists with configuration and understands module resolution.
Pro Cordova support
Cordova allows for building native mobile applications via HTML, CSS, and JavaScript.
Pro Dart language support
Autocompletion, syntax-highlighting, refactoring, and pub integration for Dart are supported in WebStorm.
Pro Coffeescript support
Autocompletion, syntax-highlighting.
Pro Low memory use
It may seem like a complex IDE and it does have a lot of functionality, yet it uses way less RAM than barebones-looking, Electron-based IDEs.
Pro Gulp support
Pro Interactive theme (color scheme) editor
Makes adjusting an existing or creating new themes a breeze. Especially due to things like inheritance, as well as easily exporting/distributing/importing the color settings which really only store where on deviates from the defaults (thus the resulting files are very small and relatively human-readable).
Pro Efficient and effective
Cons
Con No custom keyboard shortcuts
No possibility to create custom keyboard shortcuts.
Con No SSH, FTP mode
For example, "Code everywhere" allows using SSH, FTP as base of project. In Codenvy it's possible only through VM.
Con No Collaborative editing
At the moment, Codenvy does not have real-time collaborative-editing. But this is on roadmap, and would be implemented soon.
Con Lacks two-factor authentication
Con Slow installation by default
Trying to install with "npm install" and the server restarts before the installation. However, you can circumvent this by using npm install --no-bin-links
.
Con Non-optimistic UI, typing results in letters being sent to server and back and then they show
Con Occasional slow performance
WebStorm can sometimes choke all cores of the CPU. There are numerous reports of high CPU usage.
Con Not free for commercial use
A paid license is required to use WebStorm for commercial use. The license terms changed in November 2015 and currently require a subscription (per year: $59 personal, $129 for companies). Students can obtain a free non-commercial, educational license good for one year. There is also an option to pay on a monthly basis in addition to perks, such as a fallback commercial license that can be used for free.
Con Not open source
This application is proprietary, and thus cannot be modified, freely distributed, or trusted for security.
Con You may have to fiddle with the JVM memory settings in configuration files
To get it to run properly, you have to edit the JVM memory settings when you use Node.js. Node.js makes the small JS project you have into a "large" project that requires more memory.
Con Plug-in ecosystem isn't robust
Every framework or extension with any popularity whatsoever will have a plugin for VS Code. Sometimes they'll still support Atom. Only one in twenty will have native support for WebStorm.
If you want support for the latest libraries, you won't get it in WebStorm.
Con Non-native filesystem causes issues
The Java wrapper around the filesystem doesn't actively watch for file changes (by, for example, using the fsevents api on OS X), and as a result can become easily desynchronised from the actual filesystem.
If you have an external tool acting on your project (such as a gulp task or a third-party Git client), what you see in the file browser or in open tabs becomes out-of-date. There's a feature in the context-menu for manually synchronising directories with their real filesystem equivalent, but this shouldn't be necessary and is annoying to do. You usually remember to do that anyway after you've been trying to track down a bug on a line of JavaScript that Webstorm says doesn't exist for the last two hours.
It should be noted though that this is easily remedied by going to File/Settings/System Settings and checking the "Synchronize Files on frame or editor tab activation" option. It's also recommended to more explicitly represent your workflow within WebStorm itself. Most external tools/tasks can be handled with WebStorm. And if it's not in a plug-in, then you can handle it with the File Watchers.
Con Proprietary file dialogs
Webstorm doesn't use the native Windows and OSX file dialogs, which makes it more of a hassle to open projects.
For instance, you don't have access to your favorite folders on the left-hand side in their custom file dialogs.
Con Can't open multiple projects in a single instance
The only way to open multiple projects is to run a new instance of WebStorm which is not ideal. WebStorm can use up to 1-1.5 GB of memory.
Con Poor usability on option and menu navigation
You need to press a combination of keys or navigate through different menu levels to carry out the two most common things a developer does. For example, to run your code, the default is Shift+F10. To go to definition, you need to click on "Navigation" first. There is no sense to this: being forced to press a combination of keys hundreds of times or navigating through different menus can be a waste of time.
Con Bad default options compared to the competition
Examples are an unreasonably low number of undo steps and automatic saving (which causes webpack dev server to bundle VERY frequently).
Con Constantly trailing behind on support for its main features
The Jetbrains team do an admirable job attempting to keep up with support for the features they wrap, but they are running an un-winnable race. For example, WebStorm 11.0.2 hangs when trying to debug NodeJS 5.0+ projects (30+ seconds before hitting breakpoint). By the time they fix it, 5.1 will be out and something else will break.
Con Newer versions are increasingly unstable
This only happens when it's not a major version.