At a certain point, I got sick and tired of all the time I was wasting to start three different programs and configure kdbg just to work on code. Why do I need to switch over to the console window and type "make && make install" when I could just hit ctrl-shift-b? Why spend the extra minute or two to start kdbg and configure it - and restart and reconfigure it when the program crashed in a certain way - when I didn't even have to do anything to get that functionality in MSVC++? And let's not go into all the handwaving that seemed to be behind dealing with the code itself. Sure, I could've found the kdbg manual and understood it...but at a certain point, that just seemed rather retarded when I could just switch back to MSVC++ and get all that functionality without having to work on it.
A lot of Linux people just don't seem to get this, but sometimes programs and computers are just tools. How many hours of people's lives are being wasted because they're trying to get three separate programs to work in concert rather than just starting up one? Sure, if that's your cup of tea - if that's how you want to spend your time - then go for it. But, I, personally, don't find much value in learning about how one programmer thinks that programs should be when there's such a paucity of choices available that there's no way of judging whether or not there's any value in that method.
And regardless of learning about the program, unless I'm actually working on a compiler or a debugger, all that information is distracting and irrelevant. If I've got a certain set of features all mapped out, there's no way in hell that I want to spend my time messing with something completely different in order to let me debug it. I'll take the extra bloat, very happily, if it'll let me focus on what I'm doing and let me do it with a minimum of fuss.
So IMHO it's not just that everyone who disagrees with you sucks.