I don't think using VB6 (either the whole suite or just the compiler) is crazy as long as you've understood the limitations and risks and as long as you own the decision. I'd apply that same criteria of craziness to the use of any language (or any tool, for that matter). It behoves us to do some research around the alternatives, then make a choice and live by it.

I think some of the frustration many people feel toward VB6 fans has nothing to do with the fact that they continue to use VB6 (franky, who cares - if it works for you then more strength to your arm) but rather that many of them don't want to accept the responsibility for making that choice. So many of the campaigns and comments we see around the topic are couched in terms of Microsoft having some moral responsibility to continue development on it. Campaigning for MS to put time and resources into a project which they've repeatedly told you they will not be pursuing and then holding them up as the villain when they continue to remain utterly consistent is really just passive aggression played out large. They've made their position perfectly clear and have been entirely consistent in doing so.

VB6 was an excellent tool for developing DeskTop tools (probably the best IMO). I personally think .Net is better but that's just my opinion. I've deliberately been pushing myself into Web development lately because I do think desk top development is going to become more and more redundant as the capabilities of web technologies increase. I've chosen MVC as the platform for that shift and I'm aware I'm behind the curve but I've always found that there's a nice sweetspot behind the curve where one can continue to be profitable without the discomfort that comes with being right out in front. I progress through technologies but I do so at a fairly slow rate.

I make choices to learn new techs and am happy to live with the consequences of them.