4 ms·
I find it quite interesting that 90% of the comments here associate VB to VB6. It's a bit like if 90% of the comments on the anniversary of python would be abou
by cm2187 10y ago
I find it quite interesting that 90% of the comments here associate VB to VB6. It's a bit like if 90% of the comments on the anniversary of python would be about python 2 and how people missed it (or not)...
- umanwizard 10y agoThat's because VB.net isn't VB; it's C# with a different lexical syntax.
- cm2187 10y agoIt has kept some of its niceties. It's one of the rare case insensitive languages (less pointless bugs as a result of typos), it is very expressive (I just don't get the love of certain programmers for special characters), and it provides a natural evolution for business people into programming, many of who even today have learned the basics of coding with VBA (like me...). And there aren't that many breaking changes between VB6 and VB.net. Enough to make a VB6 program not compile. But not enough to really stand in a way of a VB6 programmer upgrading his skills over a couple of weeks.
- wvenable 10y ago> And there aren't that many breaking changes between VB6 and VB.net. If you just count syntax, maybe. But the entire environment and API of VB6 wasn't there, making the transition pointless. It's like arguing that Windows C programmers have an easy transition to C on Linux because it's the same language. VB.Net in it's current form should never have existed. VB.Net should have been able to run VB6 applications unmodified giving a straight forward transition from VB/VBA to .Net. Instead most apps were never ported from VB6 and VBA. It was a huge missed opportunity.
- voltagex_ 10y agoOooh, I wonder how hard it would be to make a VB6 compiler with Roslyn...
- umanwizard 10y agoLike I said: lexical syntax. Case sensitivity and whether you use "End" or "}" are, to me, down somewhere around tabs vs. spaces in terms of what matters for the usability of a programming language.
- WorldMaker 10y agoAgreed. Also, given the current cultural fork, I do think there will be plenty of loud, vocal people out there commenting on how Python 2 was the last "real" Python. Programmers are weird.
- smacktoward 10y agoThis is because a huge community of VB developers built up during the VB1-VB6 era, and then Microsoft blew that community to smithereens with the language and licensing changes that accompanied the move to .NET. VB still exists in the form of VB.NET, but in terms of popularity it never recovered from the diaspora of VB6 users who abandoned the platform and never looked back. So today you have two groups with an interest in talking about VB: a huge community of VB expats who moved on to other languages when the crack-up came, and a relatively tiny community of VB.NET users who either stuck with the platform or came to it later on.
- cm2187 10y agoWhat changed in the licensing? .net is pretty permissive, and has been free for a few years now (with the express editions).
- smacktoward 10y agoThey stopped selling licenses for Visual Basic 6 through most channels when VB.NET launched in 2002. Not "warned that they were going to stop selling licenses," just... stopped. So you had all these companies who had built up enormous codebases in older versions of VB, the last of which had been released only four years earlier, who suddenly couldn't buy the software all that code depended on anymore. Many of which were huge enterprises that were used to being able to phase out old software extremely slowly; so having the plug pulled on "classic" VB so abruptly was kind of terrifying for them. Microsoft's official response to these customers was "VB.NET is much better, just use that." But you couldn't take a VB6 code base and run it under VB.NET without at least some modification to bring it in line with the new syntax. And VB.NET felt less like a version of VB than like C# with a coat of VB-colored paint on it, so the developers who would have to make those modifications faced the prospect of having to learn what was more or less a whole new language in a big hurry. Since demand for client-server software (which is what you used VB to write) was in decline by then anyway, and apps that ran on the Web were the New Hotness, lots of VB developers decided that if they were going to have to learn a new language it may as well be one that let you deploy to the Web. So they didn't bother with VB.NET and moved to platforms like C#, ASP.NET, PHP, Python, Ruby, etc. instead, all of which had a better story for developing Web applications than VB.NET did. (Disclosure: I was one of these.) Of those developers that didn't flee, most simply did the easy thing, which was to refuse to do anything; they just hung on to their existing VB6 licenses and kept on churning out VB6 code like nothing had changed. All that old VB6 code meant that you could actually make a good living for a surprisingly long time this way, just tending old legacy apps and keeping them running as well as possible.
- bluedino 10y agoI actually associate VB 'being awful' with VB4. In version 5 you could finally compile to EXE, so things ran faster and you didn't have to include the runtime DLL. It was finally a 'real' language to a lot of us on AOL at the time. I was more interested in writing Doom/Quake related stuff in Visual C++, but I played around with and got a lot done with Visual Basic 4.0 and 5.0 All the PC tech support calls from the past, all because VBRUN300.DLL or VBRUN400.DLL didn't exist, or were the wrong version...