User forums > General (but related to Code::Blocks)
Code::Blocks vs. Visual Studio
sethjackson:
--- Quote from: pghtech on August 08, 2006, 12:13:37 am ---Only because I am familar with it, and was planning on doing so until I started looking into Code::Blocks.
--- End quote ---
Oh well then download a nightly build, and see how you like Code::Blocks. :)
kidmosey:
A few things you might miss (for a little while) when you switch over to C::B from VS:
1. VS style document switching - using ctrl+tab to switch to the last document is a pretty nice feature.
2. Incremental builds - it seemed like VS was faster for compiling. This is more an issue with gcc, maybe.
3. Code completion - For now, C::B has a ways to go to fix this.
4. Low maintainence - Personally, I rarely had to work around a compiler/linker problem and experienced very few crashes. I am sure once RC3 is out, C::B will be the same, though.
5. Easy installation - If you are new, installing mingw, C::B, and wxWidgets can be a pain... but well worth it.
I can't think of anything else, atm. Honestly, it is worth using C::B over VS, even considering the above "problems". It is smaller, faster (the interface), cross-platform, extensible, non-bloated, FREE, and a number of other adjectives. After 5 years of using Visual Studio, C::B is a breath of fresh air.
L_O_J:
--- Quote ---A few things you might miss (for a little while) when you switch over to C::B from VS:
1. VS style document switching - using ctrl+tab to switch to the last document is a pretty nice feature.
2. Incremental builds - it seemed like VS was faster for compiling. This is more an issue with gcc, maybe.
3. Code completion - For now, C::B has a ways to go to fix this.
4. Low maintainence - Personally, I rarely had to work around a compiler/linker problem and experienced very few crashes. I am sure once RC3 is out, C::B will be the same, though.
5. Easy installation - If you are new, installing mingw, C::B, and wxWidgets can be a pain... but well worth it.
--- End quote ---
I agree with the above quote, but if you ask me, what I will really miss VisualAssistX, I mean if I have to choose between VS only and C::B I will choose C::B, BUT if VisualAssistX is added, then (sorry) I will choose VS + VisualAssistX. oh on thing that the above should also mention is debugging. IMHO C::B is still not as comfortable as VS in debugging.
Phatency:
With the latest work on the debugger, I would never go back to Visual Studio (IDE). And the compile speed issue is more of an issue of MinGW, not gcc. To my experience, there isn't any noticeable difference between using Microsoft Visual C++ compiler on Visual Studio or Code::Blocks.
Zingam:
There are quite a lot of things that VS does better and one is the way it handles projects/solutions. I really prefer it over what C::B has but CB is nice and I like it. Something that C::B really sucks at is the Find/Replace dialog. I really wonder why the devs don't want to improve it.
BTW how can one add other compilers to C::B?
On Linux C::B keeps on crashing since the very beginning. I've tried it on different Ubuntu versions \and installations - of course\ on my laptop and it has always crashed. It is actually unusable on Linux on my computer.
:shock:Why?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version