>Just as one can create pieces of crap with VFP, using the VS doesn't mean the product will be good.

That's the central point, probably the most sensible in this whole thread.

As I write in message ID 1639037, releasing high-class software has nothing to do with tools, it's just another hen and egg story.

The best example is what happened in the JavaScript world:

Until 2005, JavaScript was considered as a second-class dev language, merely for dumb web designers: no tool whatsoever, just a text editor and a lot of patience; object oriented without inheritance; no way to pass parameters by reference; weird 'closure' concept that can make debugging a nightmare, etc.

Then developers started to put together frameworks on top of each others, sharing them under some FOSS licenses, then came the tools like smart text editors, browser dev tools like Firebug, then tools over tools like GitHub (a majority of projects on GitHub are JS), the server side S/W (nodeJS), etc.

JavaScript developers became more and more professional, maybe the most rigorous I've seen around.

While all this happened, JavaScript was still the same contemptible, dumb language for amateurs.

So, if you are a virtuoso using a tool and this tool works fine, just keep it, you'll always be better than trying to use someone else's tool.
And if you share with others, you'll always move up and forward.

As of the old saying: there are more bad workers than bad tools.