Rename Visual Basic to B# and Support B# With Absolute Parity
Dotnet 2015 made it clear: VB.NET developers need to switch to C# or be left behind. Very sad.
VB syntax is friendlier, easier to read and code and maintain. Yet Microsoft is killing off this superior language bowing to pressure from myopic C# developers and Mono.
That's because Microsoft abandoned Visual Basic and tried to replace it with the poor VB.Net. No surprise it isn't popular.
VB6 programming was always far more popular, and probably still is.
Good news that Microsoft have extended support of VB6 to Windows Server 2016. VB6 programming is supported until at least November 2027 on Windows Server 2016, and until at least 2025 on Windows 10. Both are likely to be extended.
Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008, Windows 7, Windows 8 and Windows 8.1, Windows Server 2012, Windows 10, and Windows Server 2016
VB6 programming is supported on Windows 10, Windows Server 2016 and earlier versions of Windows.
VBA programming is supported on Office 2016 and earlier versions of Office.
VBScript programming is still part of Windows.
.Net is failing commented
The 2017 Stack Overflow survey is very interesting...
C# has fallen in popularity from 45% to 34% in just 5 years.
It is amazing to see how far C# has fallen in the last few years.
C# was intended to compete with Java but was never successful in that.
It is unlikely that C# will still be a mainstream language in 5 years time.
And Xamarin is one of the most dreaded technologies in the Stack Overflow survey.
Never successful as an independent business, Xamarin is now failing in Microsoft's ownership.
>>Too bad you didn't even understand why the C# name has a # in it. Very sad.
Do tell us. I certainly have no idea. Obviously nothing to do with speed either of development or performance.
Is it C-hash because Microsoft made a hash of it ?
It is more D-flat than C-sharp.
ARM brings back VB6 programming commented
Good to see that VB6 programming will run on ARM processors under full Windows 10.
You'll even be able to run the VB6 IDE on an ARM tablet.
dotNet will be too slow on ARM processors, so a great future for VB6.
Visual Basic is classic VB, dotNet should not use the Visual Basic name.
VB6 Programmimg Guide
>>Sue Gee of i-programmer magazine has suggested VB6 be open-sourced to celebrate Visual Basic's 25th birthday.
>>Please support this request.
Where has this request gone ?
Ray Koopa commented
Too bad you didn't even understand why the C# name has a # in it. Very sad.
Rashid Ali commented
Just because of the name. There is a common perception that C# is more powerful than VB. Which is totally wrong. No more Visual Basic B# B# B# B# B# B# B# only.
Mike Stone commented
Sue Gee of i-programmer magazine has suggested VB6 be open-sourced to celebrate Visual Basic's 25th birthday.
Please support this request.
Zagor Tenay commented
Microsoft have already announced VB.Net will no longer have parity with C#.
Microsoft is killing off VB.Net.
Where did this "VB.Net is being abandoned" even coming from anyway? Was there an announcement I missed?
This is a post from the MS program manager for the VB team, Anthony Green, from January 2016:
Re: VB has a long future ahead of it no matter how you look at it. We're working on the next version – the 25<sup>th</sup> Anniversary version – VB15. Visual Basic is an open source language (check us out on github) so it can't really be killed even in the event of Mount St. Helens erupting and burying Microsoft campus in magma.
Bring Back VB.Net commented
Now that VB.Net has been downgraded to a second-rate language and won't be updated very often there is little chance of this request being met.
VB.Net is being abandoned.
Microsoft need to tell us the route forward. If they have one.
The adoption of the VB.Net language was a mistake, now we need to migrate our VB.Net code. And we still have VB6 code, it simply wasn't viable to migrate this to .Net. Migrating to C# is a dead end, now that .Net doesn't have a long term future.
What is really needed is migration to an updated VB6 programming language, for both our VB6 source code and our .Net code. This would be compatible with VBA programming and would carry our VB6 programming skills forward.
It is time for MS to abandon VBdotNet and bring out an updated VB6 programming language.
The language name doesn't matter and friendlier is subjective but I agree 100% that there needs to be parity. I switch between languages easily enough depending on whichever language my clients prefer but to not have the same tools available in each language is a huge productivity killer.
For example, you brought back "Create Unit Test" in C# but skipped VB, EVEN THOUGH THIS FEATURE USED TO BE IN VB!!! Releasing this to one language but not the other is simply lazy if not evil.
Anyone in Microsoft that still thinks one of these 2 languages is superior to the other is a fool. The overwhelming bulk of the work real .Net programmers do revolves around the common core classes and .Net Framework with C# or VB syntax being the glue used to connect those pieces, far less than 1% of the work. It shouldn't matter which language we use. Stop giving parity lip service when it comes to Visual Studio tooling!
Jon McRae commented
I'd like to try the Community Edition of .Net but many of us cannot place an app server anywhere near the Internet without the security folk gett'n all riled.
Please vote for this to give us an option to register it offline or put out a true Open Source version with no reg. Thanks.
Mean time gonna keep us'n VB6...
"Private mIntList as New List(Of Integer)? What kind of nonsense is that?
List<int> for the win."
You could at least compare 1:1...
var mIntList = New List<Integer>
Dim mIntList = New List(Of Integer)
I don't see how one is better than the other...