There are more or less 2 major modes of managing a product relative to the current technological zeitgeist:
- expand to consume every new use case and buzzword that comes along. Survive in some form indefinitely, while the product becomes less concrete and meaningful over time. The product continues to succeed not because it is technically best in class any more, but sheer momentum of the large base of existing users it serves adequately
- remain focused to the original mission, delivering iterative improvements over time. Watch waves of loyal users get eaten away one after another by the tide of the current technological buzz
VB was mostly the second case, although it did have many cousins in the form of VBA and ASP. The original tool - VB itself, was only ever relevant to desktop computing. By the time it got merged into Visual Studio, I believe the RAD aspect of the tool had already mostly disappeared (although VS even today still offers some variety of the original experience!)
VB in its prime was a beautiful thing, and the experience AFAIK remains unmatched to this very day. I've pined for a "client/server VB" on many occasions.