NetBeans vs Eclipse Che

NetBeans is a free, GPL-licensed IDE. It can run on any computer with a Java virtual machine. If a computer has a Java virtual machine (JVM), Netbeans can run on it. Netbeans can, therefore, run on a variety of operating systems such as Windows, *nix, and Mac OS. Being open source means that developers can contribute changes to the code to have the IDE better serve them.

Has built-in support for the most popular revision control systems

Supports synchronization with projects stored remotely through FTP or SFTP.

You can run Linux terminal inside the IDE.

Supports Symfony1, Symfony2,Yii2 & Zend frameworks.

There's a built-in local history that lets you compare code changes and revert to a specific revision. Helpful when source code file accidentally overwritten.

PHPUnit is a testing framework. You can create test classes, run and see the code coverage directly from IDE interface.

Git commits/local diff comparison is best

NetBeans can be extended beyond the basic tool that you get out of the box through community made custom plugins.

The most used composer commands can be done directly from IDE.

Netbeans not only debugs your code, and points out errors but also gives you hints on which sections of your code could be further optimized.

Supports Smarty Template Engine right out of the box.

NetBeans provides code completion and documentation for all Twig elements.

Supports documentation generation through ApiGen and PHPDoc.

Supports static code analysis with phpstan

ApiGen allows automatically generating documentation from specifically formatted comments. It's easy to use, supports traits, allows fuzzy searching for classes and highlighting docblocks using Markdown.

Built-in terminal with root access so you can make changes to your running machines. Being able to SSH into the workspace so you can use a desktop IDE is handy.

You can package up custom commands with your workspace and then use them (or share them) with everyone else.

You can choose from pre-configured environments for Java, Javascript, C++, PHP, C#, etc., or you can define your own by dropping in a Dockerfile - makes it easy for simple and complex projects.

Projects can be easily imported from any Git or Svn repository hosting service.

The workspace in Che includes project sources, IDE and the runtime. So if you hand your Che workspace definition to another user and they execute it they will get everything they need to build, run and debug the project.

Also the runtime is in a Docker container so it will work even if the second user is on a different OS than the original user who shared their workspace with them.

Che does a nice job to automatically map the service:port running in the Docker container (e.g. tomcat on 8080) to the Docker port it actually uses (something in the ephemeral range). You never need to figure that out - it's just made available when you run your server.