Inadvertently, you could say I owe my entire programming career to you specifically. Yes I can expound upon VisualBasic's retarded conceptions but playing around and making "Forms" was how I got really interested in programming as a career choice. One could say DOS batch scripting had a hand before that but it wasn't until VB3 that I really pursued it in earnest. It wasn't until a CS 101 course teaching Pascal where every thing really gelled into a cohesive unit in my brain. I still can't deny the VB underpinning even if I laugh when I admit it. Had Ruby been around with my batch scripting background, things likely would've taken the same turn either way. Regardless of how you see it now, there's likely a lot more people like myself with a similar story.
Having said all that, what you describe would still be interesting today. I just don't know how feasible it would be to implement. I had a file manager/shell idea in the form of a game construct. Something like crates to open or destroy as a delete mechanism. It was never more than a fleeting concept but I find it interesting that I'm not the only one lamenting about what is now Explorer.exe.
Actually, the apology at the end of my post wasn't about Visual Basic as a whole, but the VBX interface specifically. People did use it to build a lot of nifty controls and extensions, but the interface itself wasn't the best-designed thing in the world, and Microsoft eventually replaced it with COM/OCX.
Having said all that, what you describe would still be interesting today. I just don't know how feasible it would be to implement. I had a file manager/shell idea in the form of a game construct. Something like crates to open or destroy as a delete mechanism. It was never more than a fleeting concept but I find it interesting that I'm not the only one lamenting about what is now Explorer.exe.