3 ms·
"Chronic suffering" seems a wee bit hyperbolic, especially in the current apocalyptic climate. Perspective, please. OT I remember when VB.Net first came out an
by mellosouls 7y ago
"Chronic suffering" seems a wee bit hyperbolic, especially in the current apocalyptic climate. Perspective, please.
OT I remember when VB.Net first came out and some VB6 devs were rather sniffily referring to it as "Visual Fred" due to the lack of resemblance wth VB beyond keywords.
It was obvious from the get go VB was now a second class citizen, and c# was the future...
- wvenable 7y agoVB.NET's only purpose should have been 99% compatibility with VB6. Instead, it was too much like C# to be compatible and too much like VB6 to be consistent. I had lot of experience with VB6 back in the day but I moved straight to C#.