Good explaining. Every language has its own set of features and nuances. When we learn (and teach) a language, it is esseential to know how the language came about. As many agree, VB came as a quick tool to enable windows programming. Way back in 1995, just when Win95 was being pushed in to the work station area, I had a question, how do I implement my shell scripts in Windows. Some one from Microsoft answered, try VB. That was how I got interested in VB. In fact, Microsoft it self learnt many things about inter process communication after the success of VBX(OCX). Remember, Microsoft talked so much about embedded documents earlier. VBX proved a new way of looking at data exchange. I worked on C for almost 10 years and then shifted to VB. I have been with it for the last 11 years! Recently I started learning C# and find it a good tool to overcome some of the problems I face in VB. I have font servers written in VB, IPC protocol implementations in VB, printer driver like things in VB. But I see fresh air in C# (my company is named C-Quad, named way before C# was conceived). The network centric orientation of C# is unparalleled in any other language, with its roots deep in XDR specs from SUN! I dont know if Microsoft talks about it. I see a connection. I have moved from Fortran IV to Pascal to C to VB but skimmed over Java and VC++. Display Postscript, Motif and may other things inclusive. I still have a heart to learn C# for what it is worth. Of course most of my work will be done in VB.
UVW
