This is gonna be like Python 3. There is an innumerable amount of “production” VB.
CIL doesn't have that problem, you can keep writing in VB.Net without being forced off a supported compiler.
I was in a fork in the road and had the choice between Python or .Net to move forward with my career a few years back, there were a few factors on why I went .Net. Being one of very few pleasing to use and (extremely) widespread languages with static typing, along with MS's early embrace of WebAssembly were both major influences. Yet the biggest was the Python core devs refusal to address Python2/3 in a better way. There's no good reason why you couldn't use the same Python 3 interpreter for Python 2 code. I get the maintenance argument, but this raises questions about the future, and it makes their platform look rinky dink today. I came to the conclusion I'd never build anything important on it, which is essentially everything you write, as projects tend to grow.