Its not strange that the debate will eventually involve .net
MS replaced VB6 with .NET and we are trying to figure out (impossible) if VB6 is still worth using, if VB6 has any cons or pros against .NET, if .NET is a bad choice, if any other languages should be "the next" after VB6, if we decide to move on.
private use or professional use, also a distinction worth mentioning, as most of the time its about customers, maintaining, cross-platform, server etc that has very little to do with private use.
VB6 is old, very old, but still working, but not always and sometimes buggy if we are not using API and workarounds.

but if we think about it, VB6 should be stalled, nothing new should be presented for us to use, thats what an abandoned product usually is. even so, we are still getting stuff.
Olaf's rc5, different typelibs (as I also mentioned many times, Direct2D). but we could get even more. we could have directx10-11 (a site offer that, but you need to use his OCX for that)

so VB6 can evolve even more, VB6 could be a top language right now 2019. the issue is .NET, a lot of professionals moved on and we lost knowledge and expertise.
if all of those people stayed, im sure we would have all the typelibs, workarounds, replacements to enchant VB6 to be so much better than .NET. but we are not far behind, we have a couple of genius in here and that gives hope.