"...But then somebody tells you the construction plan used to build the machine is written in Latin! Is that a problem?..."
Don, your comparison with the coffee machine actually proves the problems with VB. Latin does not contain the words to describe the construction of the machine; plastic, electric, heating element (element would have a very different meaning in Latin) even coffee! Hence the instructions would be very long winded (attempting to describe, in Latin, words that did not exist), ambiguous, difficult to understand, and hence prone to errors. I can't even imagine how to describe what plastic is in Latin (I studied Latin at school) and calling it "plastic" would not be a solution since the word would mean nothing to a Latin reader. Would you would know what I meant if I asked you to buy me some fadge! (not Latin, but a common Irish word).
VB has the same problems. When it was written many of the instructions required for a modern system weren't in existence, and you have to find a round-about way of executing them. Long winded, time consuming, prone to error (by the processor, not necessarily you) and generally not efficient. You have done an excellent job, it amazes me that XY even works! Why it will not run on my 4 & 5 Ghz systems you may find out one day - when you update to a faster machine.
These round-about ways of creating instructions are probably the reasons bugs "disappear" without anybody doing anything. Remember, computers don't make mistakes. The mistakes are due to either the user or the programmer. If a computer fails, it fails terminally, and doesn't mysteriously recover and work again. Yes, I know freezing hard disks can allow recovery of data (I've done it), but it's short term.
There, that's my rant for to-day. Have a good day.
Those people who think they know everything are a great annoyance to those of us who do.