Visual Basic forever 29-year-old Microsoft announces it will no longer develop the language

Recently, the Microsoft NET team announced in a developer blog that while they will continue to support Visual Basic on .NET 5.0, they will no longer use VB as a stand-alone language development (Go forward, we do not plan to evolve Visual Basic as a language).

Visual Basic forever 29-year-old Microsoft announces it will no longer develop the language

.Net 5 is a large iteration that provides a unified running environment for Windows, Linux, macOS, iOS, tvOS, Android, Web, etc., across the cloud, IoT, local games, etc., announced by Microsoft Build last year and on March 17 this year The first preview version was released.

Visual Basic forever 29-year-old Microsoft announces it will no longer develop the language

First preview version

NET 5 VB will support class libraries, consoles, Windows Forms, WPF, Woker Service, and ASP.NET Core Web APIs.

“Looking ahead, we’re not going to continue to evolve the VB language, but rather focus on improving stability and maintaining compatibility with the .NET Framework version and .NET Core.” “Of course, VB will gradually show the difference on both versions due to the platform differences.

VB was brilliant.

VB was once brilliant, and it was the first language to support visual interface design.

VB’s predecessor was Quick BASIC, which was introduced by Microsoft in 1987. Quick BASIC is also the successor to BASIC if you go back. The BASIC language was born in 1971 and is designed for beginners, and the Fortran and Algol 60 languages are difficult to master by non-engineering students.

Quick BASIC was the development language under DOS, and with the introduction of Windows systems, the new version was renamed Visual Basic in April 1991 and was popular with many programmers. Vb 6.0, released in 1998, is a very widely used version.

Then came the .NET era. In 2001, VB moved to the .NET platform, named VB .NET. VB .NET has made significant improvements to the BASIC language features.

But it’s also this version that has cut the VB’s camp apart, with some developers using the .NET version and others sticking to past Vbs, such as the classic VB6. Developers say the two languages are very different, the former more like java, more object-oriented.

Microsoft, on the other hand, chose .NET. In 2005, Microsoft announced that it would no longer offer free support for non-.NET versions of VB, and 100 MVPs were unsuccessful. Then, in 2010, Microsoft added two versions to Visual Studio.

The VB .NET that wins in the infight, but does not resist the external opponent, C. The .NET development platform supports multiple languages, of which C? is the primary language, in 2000 with the .NET development platform.

Over time, professional developers have become more inclined to use C . . . and many VB users have simply abandoned more complex and powerful . NET version. Today, almost all of Microsoft’s relevant development documentation is more and more difficult to find with examples of the VB source code.

And Microsoft’s attitude towards VB doesn’t seem to have been well-documented. In 2017, Microsoft announced a co-development strategy for C?/VB, but in fact some people think it’s been a gimmick, with only C? getting all the new features, and VB focusing on the simpler, more accessible scenarios it once dominated. This statement amounts to a formal declaration of strategic bankruptcy.

“It’s considered a toy language for people who are just starting out to learn programming. In a 2018 report, tIOBE, a programming language community, wrote that not many professional developers pay much attention to the language. “Microsoft is slowly reducing its investment in VB, and sooner or later the language will decline. “Microsoft’s official figures for the year show that the number of users in C is millions, while vb. NET only has hundreds of thousands.

Visual Basic forever 29-year-old Microsoft announces it will no longer develop the language

March 2020 List

Miraculously, VB. NET has been active in the TIOBE program language list, surpassing C. in Fifth Place in December 2018. In the latest March list, C? came in fifth, VB. NET dropped to sixth place from March last year, and VB ranked 18th.

Where do developers go from here?

Microsoft blog says developers can continue to use the .NET Framework, and not necessarily migrate VB apps to .NET Core, which currently does not support WebForms, Workflow, WCF, and other things, and migration sits to some very new technologies.

“As long as you’re happy, you can continue to use the .NET Framework, whether you’re a VB or a C?user, and as long as your PC supports Windows, your own .NET Framework will always be used.” “

Microsoft also noted that Visual Studio will continue to add new features and improve performance, as will VB developers, such as the one they recently added to IntelliCode for VB.

That is, VB.NET won’t go away, it’s not going to go any further, and developers can switch to .NET Core, or directly to C.

In an external blog post, some developers said that the VB user base is too small, “death” is inevitable. Not only his friends are useless, but even friends of his friends are useless.

However, despite VB’s decline, there are many programs and Apps written in VB, such as many office applications developed for small and medium-sized businesses, which can be quickly prototyped and easy to get started.

There are many developers who have expressed nostalgia for VB and the time it used 20 years ago. These developers migrated from FoxPro to VB around the 1990s and then switched to C. So in the nostalgia, they also urged VB developers to move to C.

Mike_Brady is one of them, starting in 2002. He thinks some VB programmers are still sticking to VB because they’re too scared of curly braces, “Although C is much like C, it’s not (I’ve been in the C language for a few years at work, and I’m shuddering, I’m not going to use it anymore!” ) In fact, the c’ is closer to VB.NET, and conversion is not a very difficult thing, maybe a week or two, to be able to adapt to this stylistic difference. “