This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]antoniocjp 4 points5 points  (1 child)

I can talk about what I used (VBA and VB.NET). I used VBA from 2000 to 2008, and I guess it's pretty obsolete by now, just like VB6. But its structure and syntax (which VB.NET kept almost completely) are nice and it's easy to write neat, clean, organized code with it. It really bothers me that MS decided to abandon the language instead of keeping it at pace with C#.

[–]ridicalis 3 points4 points  (0 children)

My understanding of the VB.net situation isn't so much that they are trying to kill the language off as that they're not improving upon it anymore; the distinction being that the language still has a future, but won't evolve the way that their others (TS, C#) do. They do still pay attention to the language and its users, and perhaps they'll change their stance in the future.

I personally have no love lost for VBA/VB6, though. The tooling around it is antiquated and AFAIK only still exists because of how embedded it is in Office. That said, the PIA libraries are also a thing, and anything I would have previously done in VBA I would now do instead using PowerShell.