Quote Originally Posted by Niya View Post
This makes me realize that the people that complain about MS switching over to VB.Net instead of developing VB6 further are complaining simply to be a pain in the ass. They have no legitimate claim to reason. If they did, they'd simply stay in VB6 and if they yearned for new features and stuff they'd move to VB.Net.
Funny, I'd say comments like that one come from the real troublemakers.

In any case I don't expect Microsoft or anyone else to pick up VB6 and develop it further. Those days are long past.

Of course .Net is now in maintenance mode as well as noted by quite a few people in the know. If your question is what to develop in for Windows you can pick a horse and ride it: VB6, .Net languages, Delphi, Java, whatever. They're all going by the boards since Windows is moving to the closed-ecosystem RT model.

As Microsoft folks have been saying for a while, and more strongly recently, they want "One Windows" and that will likely be something like Windows 8.x but with the desktop locked down as in Windows RT.