Who is who in the cloud IDE market?
Since the publication of the cloud IDE overviewabout two years have passed. Did the developers have enough time to transfer the online IDE from the category of interesting toys to the category of tools and services actually used in the development? It is difficult to give a definite answer. The coup is not perfect, but the onset of the cloud IDE has become even more assertive. The development of the cloud industry incites teams of innovators to innovative moves. By the way, one of the most common misconceptions - the cloud IDE - is a regular editor in the browser, stuffed with all sorts of extras and ryushechkami. Just such projects do not have a chance to become a full-fledged replacement for offline development environments. But the idea of having all the development tools, as well as services for launching, testing and deploying applications in the cloud, is very, very attractive. And if it is also beneficial in terms of finance and time? Then maybe it's worth considering.Cloud9 and Codenvy .
Cloud9 is a prominent representative of the cloud IDE. The US-Dutch team regularly updates its service, adding new editor features, supported languages and PaaS. Cloud9 differs from Codenvy, and not only in design. However, the design of Cloud9 deserves separate epithets - made unusual. If in Codenvy the layout of the menu can be called classic, then for the first time getting into Cloud9 you need to get a little used to it. Plus or minus is up to you.
Registration and creation of projects
To register in Cloud9, just enter the desired username (this will be the name of your domain), email (a link will come to confirm registration) and select a password. Quick access to the virtual desktop is the main feature of any cloud IDE, and Cloud9 is no exception. Registration took about two minutes. If you have accounts on GitHub or Bitbucket, then registration is even easier.
By default, one demo project is available in Cloud9 with 5 simple applications in HTML, Node.js, PHP, Python and Ruby. Of course, you can create new projects, upload files from local disks, or use the help of Git or Mercurial to work with remote repositories.
Supported Languages, Platforms, and PaaSs
As already mentioned, Cloud9 supports HTML, Node.js, PHP, Python, and Ruby. But the list of PaaS is clearly lame. By registering with a free account, only Heroku, Windows Azure Cloud Services, and Windows Azure Websites were found among the supported PaaSs. The site also claims support for CloudFoundry, but this PaaS was only available from the command line. Support for OpenShift was noticed, but it turned out that this PaaS is not used as a full-fledged platform for deploying applications, but just as one of the remote repositories.
Editor
Cloud9 supports basic features such as code completion, syntax highlighting, code navigation, code folding, formatting, etc. The editor interface is also customizable (windows, tabs). There is the ability to customize hot keys.
Launching and debugging
Cloud9 applications would not be a cloud IDE if users could not launch and debug applications in the cloud. Just click on the running person icon and the application runs on the local Cloud9 server. The same goes for launching in debug mode. Thus, developers can “bring to mind” applications before deploying them to PaaS.
Version control system
Cloud9 supports Git and Mercurial. Both version control systems are available only in console mode, however, this can hardly be considered a drawback. Work with remote repositories is supported, which means that you can easily backup the code on GitHub and pull projects to Cloud9.
Invitations to projects / joint programming
Cloud9 offers the following options for inviting and “sharing” projects:
* invite via email
* share on Twitter
* share on Facebook
Of the amenities - a full mode of co-editing projects. Moreover, collaborators can chat directly in their domains. By default, guests can only work in read-only mode, but the domain owner can provide extended rights, of course, if he considers it necessary.
Cost
For $ 12 / month, Cloud9 offers 6 private workshops, full access to the console and terminal, connection to its own virtual machine, unlimited ftp and public workshops, and an unlimited number of invited users.
General impression
Cloud9 left a very good impression, and without a doubt, the project will develop. Convenient work with files, the necessary and important functions of the editor, a full-fledged collaborative editing mode ... However, for one second the feeling that Cloud9 was perfect for working with files, but not projects as a whole, did not leave. However, perhaps this is just a feeling that has nothing to do with reality)
Over the past 2 years, the team has changed not only the name (previously the project was called Exo IDE). Starting as a component of the eXo Platform product, Codenvy set sail on their own. Codenvy’s ambition is not worth talking about. The pace of product development speaks for itself - the guys intend to fight for the lion's share of the market, which, by the way, is in its infancy. As they say, who is the first - that and slippers.
By the way, collecting information about Codenvy, we managed to find the resource codenvy.ru - a simple non-profit blog of informational and educational orientation. There is not much content due to the age of the blog, but it is updated with enviable regularity. So, the interest of the Russian-speaking community is present, and, hopefully, it will only grow.
Codenvy developers have provided their IDE with the brainchild of a dozen new chips covering all aspects of development: from new PaaSs and code refactoring, to multi-user mode and project invitations. Let us dwell on the main ones:
Registration and creation of projects
If you have a Google account, then registration of a new domain will take no more than 2-3 minutes. The domain name will be taken with the Google Mail ID. In case you do not want to use a Google account, manual registration is also available with the choice of the desired domain name. No downloads, plugins, configurations. This is all on pure Linux, Windows or Mac OS, under Chrome, Firefox or Safari (IE is not supported).
Creation of projects takes place under the guidance of a special wizard. You will not have a chance to select an unsupported PaaS or enter an invalid project name. Codenvy proposes to use its own templates by default, however, nobody canceled the import of their own applications. Cloning repositories from GitHub or BitBucket via a graphical interface is intuitive and does not take much time. There is also a download of local files and archives with projects.
Supported Languages and PaaS
Codenvy currently supports Java, Java Script, PHP, Python, Ruby, HTML, and CSS. Applications written in these languages can be deployed on AWS Elastic Beanstalk, AppFog, Cloud Foundry, CloudBees, Google App Engine, Heroku, and OpenShift. Such a set of technologies and PaaSs does not mean that any application can be deployed on any PaaSs. So, for example, a PHP application can be “deployed” only on OpenShift or AppFog. Needless to say, the list of available programming languages and PaaS is constantly growing. By the way, users themselves vote for those chips that they would like to see.
The
Codenvy editor was originally sharpened for Java. But, this does not mean that other languages are deprived of editor functionality. Still, Java programmers will find a b athe smallest number of chips is code autocompletion, syntax highlighting, an error editor with hints for their elimination, code scheme and code refactoring (currently renaming classes, fields and variables is supported; watch the video ).
The toolbar and hot keys are easy to customize, therefore, in just a few minutes it is possible to configure the Codenvy domain for yourself, for example, by placing the most frequently used commands on the main panel.
Builds, launch and debug applications
Before deploying the application to the selected PaaS, users have the opportunity to build and publish the project, run it on the local Codenvy server, or run the application in debug mode. And it's all in the cloud! Maven is used as a project collector. For Java applications, a JRebel plugin is available that can update the application directly in runtime. Codenvy
Version Control
System uses Git as a version control system. Git operations are available from both the GUI and Shell. Of course, work with remote repositories is provided. Whether support for SVN or Mercurial is planned is an open question. Perhaps such support will appear in the future. However, the Native Git is a very usable option.
Project Invitations / Co-programming
Codenvy is already working on a full-fledged collaboration mode, which will somewhat resemble collaborative document editing in Google Docs. Users who are currently working on the file will be indicated by colorful cursors, and their edits will also have color differences. The beta project is already in the testing phase, and its appearance is expected in the near future.
From what is already available - an invitation to users to your virtual workplace (import of Google contacts or an address invitation), as well as an invitation to GitHub co-authors.
Cost
At the moment, you can use Codenvy absolutely free. In the near future, it is planned to switch to the GitHub model: public projects - for free, private ones - for money. Tariff packages start from $ 9 / month, but have not yet entered into force.
Summary
We will not argue and reflect on the feasibility of developing a cloud-based IDE. There are enough critics and supporters of "hang in the cloud." On the other hand, hiding your head in the sand is at least stupid - the online IDE market is developing and developing dynamically. And the fact that competition appears on the market indicates that conventional IDEs will continue to progress. According to experts, by 2015, the cloud industry will bring companies revenues of $ 1.1 trillion and create 14 million jobs worldwide. Surely, some part of this market will be occupied by cloud IDE projects. Well, to everything else, now more and more applications are being created in the world, while the number of people involved in software development is not keeping pace with the growing number of applications and web services. It means, that programmers just need to become more productive. This is exactly what the online IDE projects are aimed at. The goal of any cloud-based IDE project is to make life easier for the developer or development team.
As a result, I will give a summary table comparing Cloud9 and Codenvy. Register, try and express yourself!
Cloud9
Cloud9 is a prominent representative of the cloud IDE. The US-Dutch team regularly updates its service, adding new editor features, supported languages and PaaS. Cloud9 differs from Codenvy, and not only in design. However, the design of Cloud9 deserves separate epithets - made unusual. If in Codenvy the layout of the menu can be called classic, then for the first time getting into Cloud9 you need to get a little used to it. Plus or minus is up to you.
Registration and creation of projects
To register in Cloud9, just enter the desired username (this will be the name of your domain), email (a link will come to confirm registration) and select a password. Quick access to the virtual desktop is the main feature of any cloud IDE, and Cloud9 is no exception. Registration took about two minutes. If you have accounts on GitHub or Bitbucket, then registration is even easier.
By default, one demo project is available in Cloud9 with 5 simple applications in HTML, Node.js, PHP, Python and Ruby. Of course, you can create new projects, upload files from local disks, or use the help of Git or Mercurial to work with remote repositories.
Supported Languages, Platforms, and PaaSs
As already mentioned, Cloud9 supports HTML, Node.js, PHP, Python, and Ruby. But the list of PaaS is clearly lame. By registering with a free account, only Heroku, Windows Azure Cloud Services, and Windows Azure Websites were found among the supported PaaSs. The site also claims support for CloudFoundry, but this PaaS was only available from the command line. Support for OpenShift was noticed, but it turned out that this PaaS is not used as a full-fledged platform for deploying applications, but just as one of the remote repositories.
Editor
Cloud9 supports basic features such as code completion, syntax highlighting, code navigation, code folding, formatting, etc. The editor interface is also customizable (windows, tabs). There is the ability to customize hot keys.
Launching and debugging
Cloud9 applications would not be a cloud IDE if users could not launch and debug applications in the cloud. Just click on the running person icon and the application runs on the local Cloud9 server. The same goes for launching in debug mode. Thus, developers can “bring to mind” applications before deploying them to PaaS.
Version control system
Cloud9 supports Git and Mercurial. Both version control systems are available only in console mode, however, this can hardly be considered a drawback. Work with remote repositories is supported, which means that you can easily backup the code on GitHub and pull projects to Cloud9.
Invitations to projects / joint programming
Cloud9 offers the following options for inviting and “sharing” projects:
* invite via email
* share on Twitter
* share on Facebook
Of the amenities - a full mode of co-editing projects. Moreover, collaborators can chat directly in their domains. By default, guests can only work in read-only mode, but the domain owner can provide extended rights, of course, if he considers it necessary.
Cost
For $ 12 / month, Cloud9 offers 6 private workshops, full access to the console and terminal, connection to its own virtual machine, unlimited ftp and public workshops, and an unlimited number of invited users.
General impression
Cloud9 left a very good impression, and without a doubt, the project will develop. Convenient work with files, the necessary and important functions of the editor, a full-fledged collaborative editing mode ... However, for one second the feeling that Cloud9 was perfect for working with files, but not projects as a whole, did not leave. However, perhaps this is just a feeling that has nothing to do with reality)
Codenvy
Over the past 2 years, the team has changed not only the name (previously the project was called Exo IDE). Starting as a component of the eXo Platform product, Codenvy set sail on their own. Codenvy’s ambition is not worth talking about. The pace of product development speaks for itself - the guys intend to fight for the lion's share of the market, which, by the way, is in its infancy. As they say, who is the first - that and slippers.
By the way, collecting information about Codenvy, we managed to find the resource codenvy.ru - a simple non-profit blog of informational and educational orientation. There is not much content due to the age of the blog, but it is updated with enviable regularity. So, the interest of the Russian-speaking community is present, and, hopefully, it will only grow.
Codenvy developers have provided their IDE with the brainchild of a dozen new chips covering all aspects of development: from new PaaSs and code refactoring, to multi-user mode and project invitations. Let us dwell on the main ones:
Registration and creation of projects
If you have a Google account, then registration of a new domain will take no more than 2-3 minutes. The domain name will be taken with the Google Mail ID. In case you do not want to use a Google account, manual registration is also available with the choice of the desired domain name. No downloads, plugins, configurations. This is all on pure Linux, Windows or Mac OS, under Chrome, Firefox or Safari (IE is not supported).
Creation of projects takes place under the guidance of a special wizard. You will not have a chance to select an unsupported PaaS or enter an invalid project name. Codenvy proposes to use its own templates by default, however, nobody canceled the import of their own applications. Cloning repositories from GitHub or BitBucket via a graphical interface is intuitive and does not take much time. There is also a download of local files and archives with projects.
Supported Languages and PaaS
Codenvy currently supports Java, Java Script, PHP, Python, Ruby, HTML, and CSS. Applications written in these languages can be deployed on AWS Elastic Beanstalk, AppFog, Cloud Foundry, CloudBees, Google App Engine, Heroku, and OpenShift. Such a set of technologies and PaaSs does not mean that any application can be deployed on any PaaSs. So, for example, a PHP application can be “deployed” only on OpenShift or AppFog. Needless to say, the list of available programming languages and PaaS is constantly growing. By the way, users themselves vote for those chips that they would like to see.
The
Codenvy editor was originally sharpened for Java. But, this does not mean that other languages are deprived of editor functionality. Still, Java programmers will find a b athe smallest number of chips is code autocompletion, syntax highlighting, an error editor with hints for their elimination, code scheme and code refactoring (currently renaming classes, fields and variables is supported; watch the video ).
The toolbar and hot keys are easy to customize, therefore, in just a few minutes it is possible to configure the Codenvy domain for yourself, for example, by placing the most frequently used commands on the main panel.
Builds, launch and debug applications
Before deploying the application to the selected PaaS, users have the opportunity to build and publish the project, run it on the local Codenvy server, or run the application in debug mode. And it's all in the cloud! Maven is used as a project collector. For Java applications, a JRebel plugin is available that can update the application directly in runtime. Codenvy
Version Control
System uses Git as a version control system. Git operations are available from both the GUI and Shell. Of course, work with remote repositories is provided. Whether support for SVN or Mercurial is planned is an open question. Perhaps such support will appear in the future. However, the Native Git is a very usable option.
Project Invitations / Co-programming
Codenvy is already working on a full-fledged collaboration mode, which will somewhat resemble collaborative document editing in Google Docs. Users who are currently working on the file will be indicated by colorful cursors, and their edits will also have color differences. The beta project is already in the testing phase, and its appearance is expected in the near future.
From what is already available - an invitation to users to your virtual workplace (import of Google contacts or an address invitation), as well as an invitation to GitHub co-authors.
Cost
At the moment, you can use Codenvy absolutely free. In the near future, it is planned to switch to the GitHub model: public projects - for free, private ones - for money. Tariff packages start from $ 9 / month, but have not yet entered into force.
Summary
We will not argue and reflect on the feasibility of developing a cloud-based IDE. There are enough critics and supporters of "hang in the cloud." On the other hand, hiding your head in the sand is at least stupid - the online IDE market is developing and developing dynamically. And the fact that competition appears on the market indicates that conventional IDEs will continue to progress. According to experts, by 2015, the cloud industry will bring companies revenues of $ 1.1 trillion and create 14 million jobs worldwide. Surely, some part of this market will be occupied by cloud IDE projects. Well, to everything else, now more and more applications are being created in the world, while the number of people involved in software development is not keeping pace with the growing number of applications and web services. It means, that programmers just need to become more productive. This is exactly what the online IDE projects are aimed at. The goal of any cloud-based IDE project is to make life easier for the developer or development team.
As a result, I will give a summary table comparing Cloud9 and Codenvy. Register, try and express yourself!
Only registered users can participate in the survey. Please come in.
Cloud IDE
- 10.9% will die because nobody needs them 147
- 41% will develop, but will not compete offline with development environments 550
- 21.2% will supplant the offline IDE, if not in the near future, then in 5-7 years exactly 285
- 51.6% will coexist with the offline IDE, occupying their own niche 692
- 5.8% I already program in the cloud 79