They did not kill anything, they brought them into VB.NET, and I can tell many VBA users are quite happy to transition into VB.NET, as I experienced in a couple of life sciences corporations.
Having used VB back in the day, the only thing missing are a couple of people still not getting that VB.NET with Forms is just the same deal, even Me is available.
Except that all the little controls and plugins DIDN'T transition to VB.NET--and they're what made VB6 useful to common people.
And the hot code reload in VB.NET is nowhere near as useful as it was in VB6--and that was how common people debugged code.
I can go on and on.
VB.NET was not a useful replacement for VB6. I still know tons of businesses running VB6 code and, when they finally have to migrate, it won't be to VB.NET.
We had a programming language that matched that description ...
Visual Basic 6 -- and Microsoft killed it because it wasn't making them enough money.