The main reason I'm still using IDE is mostly because of code debugging and code browsing. If I could debug code on vim or ST and do code browsing I would switch in no time.
The main reason I'm still using IDE is mostly because of code debugging and code browsing. If I could debug code on vim or ST and do code browsing I would switch in no time.
Honestly, though, probably 80-90% of the time I do prefer printfs for debugging. A debugger is great if you can easily get to the problem area. If you're just trying to figure out what is going wrong with complex code, dumping a lot of information in a format you can easily look over with a text editor is generally a superior approach.
It can be faster, but output (printf or more complicated state outputs) seems to always be more reliable.
I don't compile my code inside vim, so why should I expect to be able to debug it there?
Learning that the tools don't have to be integrated with each other to be useful was a major eye-opener for me, after using MSVC for many years.