Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing SlickEdit vs Code::Blocks, the Slant community recommends Code::Blocks for most people. In the question“What are the best IDEs for C++ on UNIX-like systems?” Code::Blocks is ranked 4th while SlickEdit is ranked 19th.
Question Ranking
Pros
Pro Extensive support for programming languages
SlickEdit supports over 50 programming languages on nine platforms.
Pro Built-in beautifier
The beautifier formats code as you type to help improve readability and consistency.
Pro Compiler tools
Pro Scriptable
Write custom macro commands, functions, dialogs and tool windows.
Pro Over 13 emulations
Choose from fifteen keyboard emulations, containing the key bindings and behaviors necessary to emulate other editors (e.g., CUA, Vim, GNU Emacs, etc.)
Pro Extensive configuration options
Pro Easy access to Visual Studio workspace
SlickEdit opens Visual Studio workspace with no conversions needed.
Pro Symbol analysis support
There are powerful symbol analysis features in SlickEdit, including context tagging and references.
Pro Integrated debuggers for multiple languages
Integrated debuggers for GNU C++, Java, Python, Perl, Ruby, and PHP.
Pro Multi-Platform
Windows, Linux, Mac OS X, AIX, HP-UX, Solaris SPARC, Solaris x86
Pro Portable mode
Possibility to set up a portable installation, to run on a USB drive for example.
Pro Easy access to XCode projects
SlickEdit opens XCode projects with no conversions needed.
Pro Third party tool integration
Pro Popular version control system
Pro Lightweight
Pro Easy to use
Pro Simple Library import
Cons
Con No command line option
This is a visual only editor
Con It's kinda slow
If you have a very large project or tag database, it can hang the UI.
Con Hard to set up
Con Not very feature rich
By default it's not much more than "What if Gedit had a compiler and a terminal built in?" (or: "What if Notepad had colour coding, auto indents, file structure, a compiler and a terminal built in?")
There are far more professional IDEs out there. This one is much too basic for any efficient use.
Con Slow navigation using mouse
In most IDE's, you can "goto declaration"/"implementation" by holding CTRL and left-clicking on an identifier or include directory. This does not work in Code::Blocks no matter what settings you have. Right-clicking will bring-up a menu that includes these "goto" options, but it's not instant and you'll be slowed down immensely depending on how often you have to do it.
Con Can get quite slow and doesn't look all that good
Con Setting up dark theme requires using system's own gui toolkit
Con Lots of functionality is encountered only in plugins
You can't change keyboard shortcuts, neither share themes with vanilla codeblocks, for example.
