Mike, I mainly agree on that.
That's also why I considered what I considered. Not only to enable yourself to extend your VFP world. Both C++ and SQL dialects are in demand aside from Java, which is in even higher demand. I don't disapprove learning Java or javascript (and don't confuse them with each other) for that reason, but it has no direct additional benefit for your own VFP usage, also if you do that as a hobby. I'd say SQL has a better benefit in its separate usage from VFP and in its usage in conjunction with VFP. Including the kind of NoSQL dialects necessary to handle new database types. You already can qualify when a backend developer is needed as employee or freelancer. Javascript comes into play, if you find one of few VFP projects making use of VFP as a server-side language of a web application, but do you even know ProLib's AFP or Claude Fox's ActiveVFP? Or have developed with Rick Strahls Web Connection? In that case you likely also already have HTML and javascript knowledge. Or if you do web development on a totally separate development stack, of course.
As a freelancer, you rarely find a demand for an application built from scratch with anything you like, but demands to maintain and extend existing applications that demand the knowledge of the language it's already written in, that's no discussion point. And today that's only VFP in very few cases, of which I think 50% are POS systems. I once almost got involved in software for cemetery management and all other kind of software you can't think of, but that's how I'd describe the market - 50% POS systems and 50% individual software that exists as internal company software and is very unique and doesn't fit into usual categories.
If you develop targetting end users and have ideas not yet covered in the market of shareware/freeware, congratulations, but the usual price people are willing to pay is close to 0.00 only. So get lucky that you get many hundred thousands if not millions of customers to cover more than your development costs. It's true though, that end users will mostly not care what something is written with. Unless you target developers as end users. But then programming something for the community of VFP developers is having a falling number of potential clients, which also are used to getting free add-ons on GitHub VFPX by now. So in that case your motivation should be the support of the community, not making your living.
I get it there are a lot of people old enough to foreseeable make it until they don't need to program anything at all. The endangered VFP developer species is over 50 years old and not able to learn anything else as deep as needed to qualify as XYZ-developer. Of course you still have much time to learn and apply something. But even if you say 1 year of intensive learning is sufficient, you can't learn enough as a side project while developing VFP to feed you and your family. Don't underestimate what concepts unknown to VFP you would need to understand if you would want to take on maintenance or extension of something written in XYZ. And a project failing when you have to admit you weren't fit for the job is getting you a hit in repuatation, too.
Chriss