I'll ignore all the tiresome ad hominam stuff, as usual...

but of course you can decide whether a development tool is for you without having to become a guru in it. Heck, you did it yourself- you were loudly broadcasting your decisions about dotNET long before you could claim to be proficient with it. And how many times have we been told about big-business managers who insist on dotNET? Did they all become C# gurus before they decided? Your "argument" falls apart by your own evidence.

You're also wrong when you insist that nobody can be productive in dotNET inside 3 months. I've seen it more than once when smart developers join large teams and rely on peer assistance and the "it's easy to know an awful lot about very little" principle, limiting themselves to tightly constrained core competencies. As development continues its march to commodity, that's the way of the future. Much development is now a set of tightly controlled tasks- a production line, with all the QA features of production applied to it. Uber-experts who can range across entire projects are already going the same way as the physicians who used to be able to perform every surgical procedure for every condition. Their abilities were impressive, but you're better off getting your cataracts fixed by somebody who does nothing else.

If you still want the joy of ranging across entire projects, IMHO you need to lift your nose out of the detail and get into project management and scoping- . As outsourcing (and its huge teams with multiple tightly constrained competencies exactly as described above) continues to automate development, the best opportunities for some VFP people may not be to learn a new language that has more online job offers, but to leapfrog into planning or other areas that can't be outsourced and where you can display special value. For some people, that might mean staying with VFP, serving small local business. You can claim to be amused and scoff unpleasantly as much as you like, but that's not a bad lifestyle and there is $$$ in it.