4 ms·
It wasn't deliberately killed. The problem was that VB6 had weird semantics and behavior by the standards of other languages, but .NET was designed primarily ar
by mike_hearn 4y ago
It wasn't deliberately killed. The problem was that VB6 had weird semantics and behavior by the standards of other languages, but .NET was designed primarily around Java's semantics. Rather than pollute their nice next-gen platform (that they wanted to standardize through ECMA even!) with lots of VB6 compatibility goop, Microsoft chose to change VB with a new version that was closer to a normal .NET language. For example, in VB6 parameters are always passed by reference, but in C#, Java and VB.net they're passed by value.
They also didn't seem to care much about being fully compatible, for example VB6 had some fairly basic features that WinForms didn't have.
- narag 4y agoOK, you bet for the latter. But: They also didn't seem to care much about being fully compatible... That sounds deliberate. Edit, to clarify: I doubt they didn't anticipate the frustration and the hit on the mindshare. From Ballmer's show, shouting "developers", to spit in the face... I didn't use VB6, but I do remember the complaints.