User forums > General (but related to Code::Blocks)
Code::Blocks vs. VS Code
Krice:
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.
pluto:
My needed opinion, because I've nothing better to do :P
I've tried VS Code in the past, and the GUI simply sucks. I think it's the new trend of making inconsistent, nonsensical and unaccessible GUIs that for some people look cool. Good examples are Windows 8, and modern browsers. Maybe it comes in part from the forced GUIs of rich websites (instead of using protocols+custom clients) and smartphones.
Outside of the GUI, I haven't tried VS Code debugging, but in the traditional VS it's one of its strongest points. Here CB has regressed to the point that lately I've been trying CodeLite to be able to debug anything.
Also, I think the CC effort was a big waste of time. Why rewrite a parser when there are already open source implementations from compiler themselves? Not only it's a step closer to having continuous compilation, but it's implicitly consistent with how an actual compiler sees the code; plus, it requires less code maintaining with new language standards (see C++).
oBFusCATed:
--- Quote from: pluto on July 16, 2019, 05:04:23 pm ---Outside of the GUI, I haven't tried VS Code debugging, but in the traditional VS it's one of its strongest points. Here CB has regressed to the point that lately I've been trying CodeLite to be able to debug anything.
--- End quote ---
What OS is this on? The debugging experience hasn't changed much in my opinion.
--- Quote from: pluto on July 16, 2019, 05:04:23 pm ---Also, I think the CC effort was a big waste of time.
--- End quote ---
What rewrite? CC hasn't changed much last 3-4 years. clangd is still not that usable for big projects.
pluto:
--- Quote from: oBFusCATed on July 16, 2019, 06:39:34 pm ---What OS is this on? The debugging experience hasn't changed much in my opinion.
--- End quote ---
Windows 32bit with GDB
I've not used much CB in the last year, so pardon me if my info is not up to date, but let me see..
- the disasm window doesn't show anything anymore
- the pretty printing went away without any announcement, and suddenly I have to learn how to use GDB's ugly python crazyness, which was (still is?) not documented anywhere
- multithreaded debugging doesn't work
- breakpoints sometimes don't work
- the watch window doesn't remember anything
- pausing or stopping the slave, doesn't work anymore and sometimes stalls CB
- ...
is the GDB interface still the deprecated one?
--- Quote from: oBFusCATed on July 16, 2019, 06:39:34 pm ---What rewrite? CC hasn't changed much last 3-4 years.
--- End quote ---
Exactly, and it still crashes the IDE.
--- Quote from: oBFusCATed on July 16, 2019, 06:39:34 pm ---clangd is still not that usable for big projects.
--- End quote ---
Maybe it would have been more proficuous to help that project to make it more usable in the IDE, instead of starting from scratch?
Before anybody thinks I'm just an ungrateful random ranting, I'm not.
I'm grateful CB exists and that some people worked and are still working on it. I'm just pointing out some problems from my point of view.
As I wrote in the past, every single user of CB is a coder, which is very useful for code contribution, and an advantage that most open source projects don't have. The problem is that most of these users don't have time to dig into the entire codebase to understand it to contribute, so it would be very useful to document it a little, especially because CB already supports plugins, so that small patches can be provided easier and faster.
oBFusCATed:
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---- the disasm window doesn't show anything anymore
--- End quote ---
This should be fixed now. Try a night build and report if it doesn't work. But you'll have to switch to 64bit gdb and your executable also should be 64bit.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---- the pretty printing went away without any announcement, and suddenly I have to learn how to use GDB's ugly python crazyness, which was (still is?) not documented anywhere
--- End quote ---
The old thing never worked well. The python stuff is documented in GDB's documentation.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---- multithreaded debugging doesn't work
--- End quote ---
Simple example which can be used to reproduce the problem? We know this is not very robust part of the debugger interface, but it works most of the times and if you're not too aggressive switching threads.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---- breakpoints sometimes don't work
--- End quote ---
Example please.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---- the watch window doesn't remember anything
--- End quote ---
Never did, so it is not a regression.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---- pausing or stopping the slave, doesn't work anymore and sometimes stalls CB
--- End quote ---
Example? Are you debugging 64bit apps?
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---
--- Quote from: oBFusCATed on July 16, 2019, 06:39:34 pm ---What rewrite? CC hasn't changed much last 3-4 years.
--- End quote ---
Exactly, and it still crashes the IDE.
--- End quote ---
Minimal example to reproduce the problem. If you've not disabled the symbol browser try to do it. It might save you some of the crashes.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---Maybe it would have been more proficuous to help that project to make it more usable in the IDE, instead of starting from scratch?
--- End quote ---
Our parser is older than clangd and possibly clang. So there is no chance we've been able to help them.
And still using clangd with gcc or vc++ is not working 100% of the time, so it is a good solution only if you use clang as your compiler. But probably in the future we'll use clangd. I have an experimental plugin and when I find the time I'll finish it.
--- Quote from: pluto on July 16, 2019, 09:03:28 pm ---... so it would be very useful to document it a little...
--- End quote ---
What do you mean here? Which parts need better documentation? The codebase isn't really that big in the first place.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version