When comparing Eclipse vs CodeLite, the Slant community recommends CodeLite for most people. In the question“What are the best open-source IDEs?” CodeLite is ranked 1st while Eclipse is ranked 2nd. The most important reason people chose CodeLite is:
CodeLite is licensed under GPL with source code available on [GitHub](https://github.com/eranif/codelite).
Ranked in these QuestionsQuestion Ranking
Pro Large selection of plugins
Eclipse has a large and active community, which has resulted in a wide variety of plugins.
Pro Fast compiler
Eclipse uses a custom compiler (which can also be used outside of Eclipse), which is often faster than the normal Java Compiler, especially for incremental compilation.
Pro Free and open source
Eclipse is an open source project and free to use.
Pro Highly customizable
Thanks to the large variety of plugins and various configuration options, Eclipse is very customizable.
Pro Multiple languages - one IDE
Pro Good font rendering
Because Eclipse is based on SWT, it uses the native font rendering and thus looks better than other IDEs on some Linux systems, where the Java font rendering is not optimal.
Pro Good refactoring tools
Pro Great debugger
Shows threads, concurrency locks, and conditional breakpoints.
Pro Gives good perspectives on your project
The concept of perspectives is outstanding. It puts right tools at your fingertips, keeping the tools you currently don't need out from the workbench. For example, in VCS perspective it's all about versions and branches. In debug perspective it's all about state.
In java ee project it can show http endpoints in a very accessible manner.
Pro Open source and free
CodeLite is licensed under GPL with source code available on GitHub.
Pro Cross platform
Works on Windows, OS-X and Linux.
Pro Modest memory footprint
CodeLite takes up about 50MB when loaded into memory with a workspace opened.
Pro Easy to find installed compilers
The search for the installed compilers is quick, and it usually yields useful results on the very first atempt.
Pro A lot of useful plugins
CppCheck, DiffTool, Git, MemCheck (Valgrind support, Linux-only), SVN, and many other plugins extend the IDE functionality greatly!
Pro File Explorer-like workspace view
The workspace view, unlike other IDEs, is a reflection of the actual directory structure on the file system (with user filters applied).
Con Plugins can be unstable
Though there are plenty of plugins to choose from, they aren't always reliable. Some aren't maintained, bug fixes can be slow, and you may need to download plugins from multiple sources.
Con UI can be confusing
There's an overly abundant presence of menus, this forces you to constantly click around the different menu structures; foreign ideas, like Views and Perspectives; strange menu choices, like configure settings located in Windows menu->Preferences.
Con Lack of plugins with good user interfaces
Many Eclipse plugins are extremely confusing, with UIs that are even less consistent than Eclipse itself.
Con Poor language support via plugins
Eclipse supports other languages with a huge amount of plugins. Many languages have their own distribution, but multi-language is hard to exist in one project. Like Scala, there is no official support from Eclipse for this language. If Eclipse gets an update, languages such as these will not.
Con Tends to be slow and lags a lot
Con Some old bugs don't get fixed
E.g. change a parameter name to the same as a field - the field will not be prefixed with "this." like in IDEA.
Con Newer versions are getting less stable
Eclipse 4 Neon randomly hangs. For example, during installing new software.
Con Bland UI
The UI is fairly boring and has limited customization options.
There is a dark theme available, however it only applies to the editor. The surrounding windows and borders remain light.
You can see a collection of screenshots here.