Visual Basic isn't dead. Indeed, not yet in any case. One would imagine that 26 years on, we'd be discussing VB as an inheritance dialect, similar to COBOL, in that it's still around and a few companies will twofold down on a decent pay for the individuals who can utilize it to prop up old yet at the same time valuable frameworks that run it. In any case, VB is still very helpful, and Microsoft's Visual Basic group isn't ignoring it and keeps on issuing changes and developments. It's valid!
I say that with some slight, ridiculing mockery. It's difficult to gauge how VB is seen in the developer world, with apparatuses that appear to be a better fit for the world now, not a couple of decades back. In the course of the most recent couple of years, there has been the hypothesis that xamarin certified mobile developer Microsoft wouldn't move excessively to enhance the dialect as they've finished with C#, F#, even Visual C++. (Furthermore, get this: Visual Basic has bafflingly vanished in the Developer Tools Blogs menu.)
Be that as it may, VB still keeps on limping along. Prior this year, Microsoft's Mads Torgersen expounded on the group's designs in a flawlessly titled post, The .NET Language Strategy. "We will do all things needed to keep [VB] a top of the line resident of the .NET environment," he stated, however he takes note of that there has been a critical move from the co-development technique which had VB being produced in parallel with C# similarly as an issue of enabling the dialects to progress of their own volition instead of driving highlights onto one dialect on the grounds that the other now has such help.
An intriguing side note is the matching of the details Torgersen utilizes from Stack Overflow with the technique the group is intending to complete. The numbers he refers to from Stack Overflow aren't exact, yet rather are in a scope of "C# is utilized by a large number of individuals," and "Visual Basic is utilized by a huge number of individuals."
With such pairings, his think piece offers an unmistakably characterized way for C# and F#. For C#, he composes that the group "will enhance forcefully, while being exceptionally watchful to remain inside the soul of the dialect," with the group proceeding to make execution additions and biological system development some of its higher needs. For F#, Mads recognizes a significantly littler gathering, yet in addition, refers to "incredible real and potential development" in view of out of control group activism.
Shouldn't something be said about the dialect "utilized by a huge number of individuals," VB? Mads' message appears to state that C# is the thing that developers are backing nowadays, with VB dialect changes coming just on the off chance that they bode well.
A subsequent piece to Torgerson's, from Anthony D. Green, who's the Visual Basic Language developer, explains VB's future all the more briefly, in this one passage:
Be that as it may, concerning the cloud and mobile, development past Visual Studio on Windows and for non-Windows platforms, and front-line developments we are driving with C#. This is on the grounds that the gathering of people in those spaces is requesting it. We won't modest far from Visual Basic open source commitments on the grounds that in the long haul any open source VB people group is superior to none. Be that as it may, the concentration for VB will be the place VB is as of now or liable to be effective, i.e. essentially on Microsoft developments and for Windows with an accentuation on conveying present-day abilities to existing arrangements, developers, ventures, and situations (e.g. SQL Azure).
There you have it. It's the cloud's - or perhaps more precisely, C#'s - blame (you gotta give the general population what they need). As a contradiction to those posts is this one from Visual Basic developer Klaus Löffelmann that brings VB once again into the cloud fairly (however more into the domain of UWP and cross-platform development), in which he depicts a work process fixated on VB in the following VS 2017 Update 3 Preview, as it now incorporates VB-based .NET Core and .NET Standard formats. In the post, he goes ahead to depict building an application with VB and xamarin certified mobile developer. Forms and .NET Standard utilizing the VS2017U3 Preview. The kicker is that in the undertaking creation, some C# records are made by bootloader applications, however, they're overlooked in the primary task. In any case, it can be accepted this will be a cleaner procedure as VS 2017U3 platforms up to a general discharge.
Along these lines, perhaps VB isn't just "not dead," we may see developers working with it for no less than a couple of more decades.