Continue on and
master Visual Basic 5/6 (not .NET), then move on to plain C, get to know it well, then master C++. VB will further strengthen your OOP skills, then once you feel confident enough, get to know C fairly well then let it all out on C++.
VB6 is still a great language to program in. All WinXP systems already have its runtime installed, and Win2K includes runtime for VB5. Both include support for VC Runtime 6 (I believe also Win2K, but maybe VCRT 5). Not true with .NET. I have found GUI-making and string manipulation to be a nightmare in C/C++. But for everything else (not much), I'd use C, or maybe C++.
I'm just not a fan of Java or .NET. I like making native applications. VB got ruined. :| It was a great RAD language. All they had to do was add some multithreading support, 64-bit support, some extra controls, maybe a more optimized compiler (SSE2/3, etc.) and it would be heaven. I hope MS resurrects the classic VB. /rant
Java's OK, but everything I made in it seemed to be very sluggish. Maybe it's improved since then. I think .NET is just too complicated, but maybe it's just what we're used to. That said I've made some big apps in VB.NET fast. Some functions really come in handy.
It's hard to strike a balance of performance and ease of use. Fortunately, with all of those languages (except maybe Java), you can execute inline assembly via a Windows API function by sending the bytecode (and just insert inline asm instructions in C/C++ with __asm {} ). Now, if only I had mastered x86 assembly...
