When comparing Neovim vs CodeBlocks, the Slant community recommends CodeBlocks for most people. In the question“What are the best IDEs for C++ on Linux?” CodeBlocks is ranked 6th while Neovim is ranked 9th.
Ranked in these QuestionsQuestion Ranking
Pro Still Vim but with upgraded features and some issues fixed
NeoVim was a complete rewrite of Vim, with new features added and underlying issues resolved thanks to the Vim code base. The keybindings and configuration are the same as Vim, so the switch can be pretty simple.
Pro Better integration with external tools
The core text editor is "headless", meaning it's detached from the user-interface so other programs can hook into it. This enables better integration with IDEs and browsers, where "Vim mode" has typically been a poor substitute because it was a partial rewrite or a partial port at best. One of the advantages of Vim has always been ubiquity and Neovim makes it even more ubiquitous.
Pro Modern code base
As a refactor over Vim, Neovim has greatly improved its code base. For example, some functionality is handled by libuv, the same code base that powers Node.js.
Pro Powerful plugin model
Vim plugins have always been useful, but tied to specific languages. Neovim's architecture provides better separation between plugins and the core product, so that plugins are completely flexible and can be written in any language.
Pro Built-in terminal emulator
This avoids the user having to make any installations.
Pro UI Agnostic
The core functionality is handled apart from the UI, meaning that Neovim can be embedded into any other GUI system, such as Atom.
Pro Async plugin execution
Pro Active development community
Pro Comes with some good configurations out of the box
Some typical configurations most of VIM users make are default in Neovim.
Pro Opens a 3Gig Text File in a few seconds
Not many editors can open such a large text file so quickly.
Pro Fast and light on memory usage
New neovim editor instance starts instantly and you can have multiple editors open at the same time, because id does not require a lot of memory to run.
Pro Work in TUI (Tex User Interface)
Neovim can work on terminal, on a remote server over ssh.
Pro Terminal mode is very convenient for testing code in a split window
Pro Easy to use
Pro Simple Library import
Con No stable release yet
As of yet, Neovim is in an unstable point in it's development. There is no stable release and using it for the moment should be done with caution as many features may change in the future.
Con No graphical editor yet
At the time of writing this, no equivalents to gVim exist.
Con Limited cross platform support
Neovim is not available for many legacy platforms.
The Windows version is currently considered experimental.
Con Ambiguity in extensive documentation
Con Lots of functionality is encountered only in plugins
You can't change keyboard shortcuts, neither share themes with vanilla codeblocks, for example.
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 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.