Happy 20th Birthday Visual Basic!

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
It’s hard to believe that it has already been 20 years since the creation of Visual Basic. VB is still going as strong as ever with no signs of slowing. The secret of its success is diligent updating and re-invention, keeping it current with the changing times. Happy Birthday VB!

Visual Basic has always had a personality for humanizing programming and with Async methods in vNext it continues that tradition.
 
That is crazy. As you mentioned, they are still doing great! Happy birthday VB!
 
The secret of its success is diligent updating and re-invention, keeping it current with the changing times.
So many people are still stuck on the idea that VB is still classic VB, which was dead as a standalone programming language with VB6 (shipped in 1998, last SP was released in 2004).

It has evolved into a pretty decent and modern language, but there's very little reason for anyone to choose it over C# for .NET development. It's far less popular for new projects than VB classic was in its day. VB in any form is dying.
 
So many people are still stuck on the idea that VB is still classic VB, which was dead as a standalone programming language with VB6 (shipped in 1998, last SP was released in 2004).

It has evolved into a pretty decent and modern language, but there's very little reason for anyone to choose it over C# for .NET development. It's far less popular for new projects than VB classic was in its day. VB in any form is dying.

I still have a lot of memories with VB6, I will remember it well.
 
So many people are still stuck on the idea that VB is still classic VB, which was dead as a standalone programming language with VB6 (shipped in 1998, last SP was released in 2004).

It has evolved into a pretty decent and modern language, but there's very little reason for anyone to choose it over C# for .NET development. It's far less popular for new projects than VB classic was in its day. VB in any form is dying.

The problem is that no matter how much they try to fix its origins, it is still BASIC (although you whippersnappers have no idea what a limited language is unless you tried to work in 8bit BASIC). When VB came out (I started with 2.0), it blew my mind. Drag and drop a GUI together, click and add code, they got everything *exactly* right. Since MS has all the code, once they allowed any other language (C# for example) to use the GUI toolkit VB as doomed.

I just wish I had a GUI development kit like VB for python.
 
C# is so much nicer unless you really love writing hideously verbose and nasty code for whatever reason
 
Started using it from day one. VB development has made me a LOT of money. But most everything I do these days is in C#, definitely a cleaner language. VB is the type of thing that is what Microsoft is best at, making VERY complex things like programming Windows something that anyone could pick up.

The reason that I like Microsoft is that it not only inspired people to consume, but to PRODUCE AND MAKE MONEY for nearly a generation now, long before Linux, App Stores and iPads.
 
The problem is that no matter how much they try to fix its origins, it is still BASIC.
That's exactly the point I was making. :p Different versions of "BASIC" have undergone several major overhauls since it was created in the 1960s. There is not a standardized version of it like there are for certain other languages. VB5 and VB6 had very large limitations in the language, which is what most people mean when they trash VB. Classic VB deserved that reputation, as those were object-based with very limited OOP support.

The language used in VB 1.0 looked as different from early 1980s versions of BASIC as BASIC does to Pascal. The language and feature support of VB.NET is very different from classic VB, especially in 2005 (.NET 2.0) and later versions.

The VB.NET 2008/2010 language is so far away from BASIC now that it's hard to even call it "BASIC", and learning it is no easier than learning C#. Maybe you could shed some light on what you feel from "BASIC" is holding back the VB.NET language. Other than different keywords, you can do virtually everything in VB.NET that you can do in C#. That hasn't always been true (VB.NET 2002/2003 [1.0/1.1] versions did not have anywhere near feature parity with C#).

I'm not really trying to defend VB. Classic VB was a mess. I wouldn't recommend anyone use VB.NET over C#, but there's nothing really wrong with later versions of VB.NET from the last several years.
 
I'm not really trying to defend VB. Classic VB was a mess. I wouldn't recommend anyone use VB.NET over C#, but there's nothing really wrong with later versions of VB.NET from the last several years.

Classic VB wasn't so much as mess as much as it was a victim of its own success, it was simply not meant to do many of the things people used it for. However it wasn't a modern OO language even for it's time and that was it's major fault. VB.NET on the other hand is an extremely modern language and Microsoft's development tools are light years ahead of 20 years ago, they are arguably the best in the business now.

But C# is better suited for .NET development and it the language that most professional developers use by a huge margin these days. But with the exception of syntax VB.NET are C# are very similar and skills learned in VB.NET translate across .NET, so it's not a dead end tool to learn and people do use it in the field still.
 
Visual Basic .Net has become so complex, why bother with it any more? C or C# aren't that much more difficult these days.
 
Visual Basic .Net has become so complex, why bother with it any more? C or C# aren't that much more difficult these days.
It's not really more or less complex than C#. :p That is unless you want to waste time trying to use classic VB namespaces, which you can also do in C# or other CLI compatible languages.

The updates made to both languages for .NET 4 are pretty impressive because the languages are evolving at a relatively rapid pace. But I'm a nerd and get impressed by stuff like that. ;)
 
VB is still VB, and it's crap. Yes, VB.Net can do the things that real programming languages can do now, but its syntax is still awful.

Die in a fire, VB.
 
VB is still VB
No, it isn't. You should see how utterly confused classic VB programmers are with VB.NET. I have. (To be fair, many programmers worth anything would have moved on to a real language. Those left behind are unmotivated or incapable of learning anything new.) :p

and it's crap.
No, it isn't.

Die in a fire, VB.
It is dying, but not in a fire. VB is legacy, as I described above (last release is from 1998, last SP for that version in 2004). VB.NET is a different animal, but still dying. Anyone learning .NET programming is better off with C# than VB.NET.

I've never seen so much hysteria directed towards programming keywords before. :p
 
Wow, quote only part of what I say and then pick it apart. Good work, there. VB syntax is still incredibly awful.
 
VB syntax is still incredibly awful.
VB and VB.NET are not C derived languages. There is nothing wrong with the syntax, other than it not being derived from C. :p

I didn't quote the other part because it showed incredible ignorance. VB.NET could "do the things that real programming languages can do" back in 2002/2003. It's not the same as classic VB. :rolleyes: Horse. Water. Give up.
 
VB syntax is still incredibly awful.

The syntax of BASIC was designed in the 60's (it's older than C) to make it easier for beginning programmers to write code. When looked at that from that perspective the syntax is almost magnificent. BASIC has been a phenomenal tool for teaching hobbyists and helping them learn other languages. It was the first computer language that old farts like me learned because good old Microsoft BASIC was embedded in all of the first home computers.

BASIC was the tool that taught my generation about computers and it's lead to me making a decent living. BASIC isn't about syntactic elegance, that wasn't its design goal. It's about learning and in the regard the nearly 50 year old language has served with the greatest of distinction.
 
I have to say when I was getting into computers when I was 14? and trying to use my 486 to program on, C was a major pain in my butt, but when we got the awesome Pentium and I got to dig my teeth into VB a little bit (never moved on more then a hobbiest) I was really hooked. VB essentially got me dug into the tech world, sometimes I wish it was still has mysterious and thrilling now as it was then. It seems too easy these days.
 
Quick trivia. Visual Basic for DOS was QBasic compatible, but was not compatible to the Windows version.
 
Bingo and I couldn't agree more, writing C for Windows 3 is some of the most complex coding I've ever dealt with, VB was like magic. BASIC overall and VB in particular have been game changing tools for getting people into computers programming. Belittling them over syntax totally misses the point as to their importance.
 
Quick trivia. Visual Basic for DOS was QBasic compatible, but was not compatible to the Windows version.

Yes, I remember this. The first real job I had was a QBasic developer and I migrated some programs over to VB DOS and was really bummed when I learned this.
 
My next class is nothing by VB. I hope it goes well, I'm afraid of programming.
 
I. Hate. BASIC. And all languages derived thereof. There's a really damn good reason that C is the industry standard, Java is so popular, and C# is the dominant language for the .NET CLR.

Computers work with numbers, not full sentences. Programs should be written like mathematical formulas, not an English essay.
 
Beginner's
All-Purpose
Symbolic
Instruction
Code

Why are people so intent on dismissing this nearly half-century old language that predates C, C++, Java, and C# that got millions of people into computers? BASIC by DESIGN was meant to be verbose as it is a BEGINNERS language, not a thing of mathematical beauty. Ignoring the design goals of a language and then saying that its not something it wasn't designed to do makes no sense.
 
Kind of funny, when i moved to 98 and started to learn c++ i lost a lot of interest, it went from being a hobby to a part time job. I guess it was time to move on, i had no interest in taking it further from small projects.
 
Back
Top