Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Code::Blocks vs juCi++, 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 juCi++ is ranked 20th.
Specs
Question Ranking
Pros
Pro Lightweight
Pro Easy to use
Pro Simple Library import
Pro Lightweight
Provides fast editing with autocompletion.
Pro Licensed under MIT
Open source and free of any charges. Hosted on Github.
Cons
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.
Con Not really feature rich
Has not as much features as most other IDEs.
