Author Topic: Code::Blocks vs. VS Code  (Read 428 times)

Offline tigerbeard

  • Multiple posting newcomer
  • *
  • Posts: 89
Code::Blocks vs. VS Code
« on: March 19, 2019, 11:26:24 am »
When you search the forum with "CodeBlocks" and "Visual Studio" you quckly find those three.

Code: [Select]

General (but related to Code::Blocks) / Code::Blocks vs Visual Studio
by kinddavid on July 28, 2015, 04:11:44 am

General (but related to Code::Blocks) / Code::Blocks vs. Visual Studio
by pghtech on August 07, 2006, 11:22:45 pm

General (but related to Code::Blocks) / Code::Blocks vs. Visual C++
by ixfd64 on March 21, 2008, 10:52:18 pm

The newest is 2015. I have not found anything about "VS Code"

A few days ago I did check out MS Code. Where for Visual Studio I have a sack full of arguments why I rather stick to Code::Blocks, for VS Code I realize that things are very different.

So to me it looks like with "MS Code" Microsoft now has
* a full open source cross-plattform IDE
* supporting almost all conceivable languages
* impressing online documentation (limited offline use)
* debugger and intellisense integration for many languages
* easy to install
* central addon repository. Automatic download & install from IDE

a bit unclear
* Suitability for larger projects? (no "project" concept, but "workspaces")
* Build management?

I am impressed to see what happens when massive manpower is directed into open source. MS built something very open and very flexible. Very unlike other MS stuff. Just looking at the wealth of 3rd party addons (called "extensions") shows that it seems already widely accepted and widely used. Looking at their own C++ extension I was instantly wondering where they plan to draw the line against their own VS Community edition over the next years.

I guess I will stay with CB which feels more suited to me for larger projects. Also I kind of love the non-fancy but very functional user interface. But I feel I am running short of real good arguments. Maybe it is mostly because its a long used tool I just comfortable to work with.
In fact, my last unsuccessful action in C:B got me the VS Code in the first place ( http://forums.codeblocks.org/index.php/topic,23035.msg156654.html#msg156654, "Plugin development/python plugin"). I was up and running Python with VS Code in a day, both for Linux and Windows. I still have my struggles with the modern GUI and with missing offline documentation but I guess even the strongest C::B supporter would give 100 points to MS Code here.

I think VS Code is a very interesting development and worth watching. Also worth a fact-based exchange of thoughts and experiences. I would be interested in
  • When you are C:B user, what is your experience with that tool?
  • What are your pros & cons? 
  • Do you plan to stick with C::B, change or use both in the future?

Offline sodev

  • Almost regular
  • **
  • Posts: 242
Re: Code::Blocks vs. VS Code
« Reply #1 on: March 19, 2019, 08:41:44 pm »
My Situation is like this:
  • I need a cross platform IDE (for me that means Windows and Linux). I don't want to learn to use two IDE's.
  • I need a cross platform meta build system that can drive automated builds and the IDE. I need to apply identical configurations to many projects, need to easily update libraries, compiler, settings, i don't want to maintain two sets of build system configurations, one for automated build, one for the IDE.

For about the last 6-8 years my setup was a heavily modified PreMake 3.x and CodeBlocks. For the last 2 years i am looking for a replacement because mainly CodeBlocks doesn't fit my needs anymore. Using a lot of Modern C++ CodeBlocks is for me reduced to a Notepad++, pretty much most of its CC functions are dead for me.

My first shot was Eclipse, but it doesn't work on Windows for me because it's not usable with the MSVC compiler there (try to use the plugin and you will quickly figure out the problems). I am using Eclipse on the Linux side though, with handwritten project files to copy enough compiler configuration to get Codan running. A maintenance nightmare but usability is really great. I was quite interested about VS Code too, tried it, and dropped it pretty fast. Main reason is focus. It is focused around "modern" web-based "fancy" script-like languages, while it might be good in that area (sorry, im not that modern enough to justify :D) it lacks in the "classic" native-code area. The project-less approach is weird and as soon as you need to configure something you end up writing "obscure" settings files. This is not very user friendly and smells like trouble for my second requirement.

From my Java work i know Gradle as a (meta-)buildsystem which fulfills my requirements for the Java side, it also gets improved support for native building but IMHO has the same problem like VS Code: its focus is Java. But now there is a very strong option for my C++ side: CMake. Yes i heard the stories about it, that was also the reason why i didn't pick it earlier, but now there is some nice improvement: native IDE support. CMake could generate projects for various IDE's previously, even some i would pick, but the results weren't that awesome. But now, since major IDE's can natively open CMake projets, the situation has changed. The results using this path looks better. Another point for CMake is that it is kind of the standard meta buildystem right now and you see increased support for it.

CodeBlocks was not bad, it was a good choice for me in the past, but i don't see a future for it for my work. It lacks some essential features and regarding the currently available manpower i doubt this will improve in the near future. For me the path is clear, get my stuff running with CMake and then use the IDE that supports this best.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11653
    • Travis build status
Re: Code::Blocks vs. VS Code
« Reply #2 on: March 19, 2019, 11:32:52 pm »
... It lacks some essential features and regarding the currently available manpower i doubt this will improve in the near future...
Hehe, I'll try to prove you wrong, hopefully even this year. Getting good CC support these days is not that hard as it was 5 years ago. :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 2300
Re: Code::Blocks vs. VS Code
« Reply #3 on: March 20, 2019, 08:01:28 pm »
You really need a killer argument against vs code? It is an electron application. Everything said ;) ... The integration in the operating system is terrible, the resource usage is terrible, everything seems to be reinvented.... (just my two cents i will not argument anymore about this)
Quote
Hehe, I'll try to prove you wrong, hopefully even this year. Getting good CC support these days is not that hard as it was 5 years ago. :)
Have you any preview ;) (probably language server?) ?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11653
    • Travis build status
Re: Code::Blocks vs. VS Code
« Reply #4 on: March 20, 2019, 08:34:37 pm »
Have you any preview ;) (probably language server?) ?
Nope, when I have something you'll see a topic. And yes it is language server based.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Krice

  • Multiple posting newcomer
  • *
  • Posts: 95
Re: Code::Blocks vs. VS Code
« Reply #5 on: March 22, 2019, 08:18:33 am »
I think C::B is the only actual IDE in open source scene, that's why it's also the best one. When comparing, more accurate vs. is Visual Studio Essential (free version) and it's just better in my opinion. But C::B has "no installer" option which I think is great, you would be surprised how many people need that.